Team discussion

Web feature requests

• Ownership change: interface to transfer ownership to another member (requires their password).
• Membership change tracking: a mechanism for finding changes in team membership (join/leave) over time. Ability to see what team departed users have joined. One approach: add new DB table (also: record user credit at that point). Or maybe automated email to team founder on join/leave.
• Membership management: include email addresses in sortable team list, instead of having a separate page
• ability to send "mass PM" to team members.
• ability to send mass email to team members. Problem: what about bounces? Could this be exploited by spammers?
• When join a team, get a "Join this team on all projects?" option
• phpBB-like formatting features?
• sortable member list (join date, total credit, RAC, country)
• team page: show more than 20 at a time?
• let team founder tag members as "team assistant" (displayed next to user name). Special privileges: can view email list, can edit team settings.

Client feature requests

• Ability to show an RSS feed (e.g. for messages from team). Not clear where this should go.
• Ability for teams to make their own installers. The installer, and the resulting client, will show team graphics. The client will automatically enroll the user in the given team when they join a project.
• Show cross-project user and team credit totals in the BOINC manager.

Team challenges

• One team can challenge another to see who can increase total credit the most over a given time period. Note: this is a little tricky because of the delay in credit granting. You'd have to do some of your computing a little before the time period.
• Natural rivalries: Army vs. Navy; Michigan vs. Ohio State; France vs. Germany, etc.
• Maybe a BOINC Olympiad, based on computation per capita.
• Some notion of "weight classes" (like wrestling), with a "virtual championship belt" for each class. Winners/losers move up/down in class.

Consistency of team names between projects

It would be nice if teams were actually BOINC-wide. How do we deal with the situation where the same team name exists on different projects with different owners?

• Should teams be BOINC-wide rather than project specific?
• If so, how to resolve current inconsistencies?
• Should people be able to belong to different teams on different projects?

Proposal:

• Create a web site for registering BOINC-wide teams. In case of dispute over a name, the oldest instance of the team on an existing project wins.
• Export this team list (in XML) as part of the BOINC distribution. Newly-created projects will be prepopulated with these users/teams.
• Resolve current inconsistencies manually; I will encourage project admins to help.