Changes between Version 12 and Version 13 of TeamDiscussion


Ignore:
Timestamp:
Aug 1, 2007, 3:15:44 PM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TeamDiscussion

    v12 v13  
    1111 * Should people be able to belong to different teams on different projects?
    1212
    13 Proposal:
    14  * Create a web site for registering BOINC-wide teams.  (Can use the "dev" project for this).
     13Conclusion (implemented as of 25 July 2007):
     14 * Create a web site http:://boinc.berkeley.edu/teams/ for registering BOINC-wide teams.
    1515 * In case of dispute over a name, the oldest instance of the team on an existing project wins.
    1616 * Write an "export" script to export the list of teams and founders as XML.  Include "previous founder" field.
    1717 * Write an "update" script that downloads these files.  For each team: if it doesn't exist, create it, and create user account.  If  founder in DB is previous founder in XML, change founder.  Update other team fields (URL etc.).
    18  * Encourage newly-created projects to use the update script (e.g. put in config.xml).
     18 * Newly-created projects to use the update script (e.g. put in config.xml).
    1919 * Resolve current inconsistencies manually; I will encourage project admins to help.
    2020 
     
    2222== Web feature requests ==
    2323
    24  * Ownership change: interface to transfer ownership to another member (requires their password).
     24Implemented:
    2525 * Membership change tracking: a mechanism for finding changes in team membership
    2626  (join/leave) over time.
    2727  Ability to see what team departed users have joined.
    28   One approach: add new DB table (also: record user credit at that point).
    29   Or maybe automated email to team founder on join/leave.
     28
     29To do:
     30 * Ownership change: interface to transfer ownership to another member (requires their password).
    3031 * Membership management: include email addresses in sortable team list,
    3132  instead of having a separate page
    32  * ability to send "mass PM" to team members.
    33  * ability to send mass email to team members.
    34    Problem: what about bounces?
    35    Could this be exploited by spammers?
    36  * When join a team, get a "Join this team on all projects?" option
    37  * phpBB-like formatting features?
    3833 * sortable member list (join date, total credit, RAC, country)
    3934 * team page: show more than 20 at a time?
     35 * ability to send "mass PM" to team members.
     36
     37Under consideration:
     38
    4039 * let team founder tag members as "team assistant" (displayed next to user name).  Special privileges: can view email list, can edit team settings.
     40 * When join a team, get a "Join this team on all projects?" option
     41 * phpBB-like formatting features (for team_name_html?)
     42
     43Not doing:
     44 * ability to send mass email to team members.
     45   (problems w/ bounces, etc.)
    4146
    4247== Client feature requests ==
    4348
    44  * Ability to show an RSS feed (e.g. for messages from team).  Not clear where this should go.
     49To do:
    4550 * Ability for teams to make their own installers.
    4651   The installer, and the resulting client,
     
    4853   The client will automatically enroll the user
    4954   in the given team when they join a project.
     55
     56Under consideration:
     57 * Ability to show an RSS feed (e.g. for messages from team).  Not clear where this should go.
    5058 * Show cross-project user and team credit totals in the BOINC manager.
    5159
    5260== Team challenges ==
     61
     62Note: these should probably be implemented by a stats site, like BOINCStat.
     63
    5364 * One team can challenge another to see who can
    5465   increase total credit the most over a given time period.