| 5 | | It would be nice if teams were actually BOINC-wide. |
| 6 | | How do we deal with the situation where the same team name exists |
| 7 | | on different projects with different owners? |
| 8 | | |
| 9 | | * Should teams be BOINC-wide rather than project specific? |
| 10 | | * If so, how to resolve current inconsistencies? |
| 11 | | * Should people be able to belong to different teams on different projects? |
| 12 | | |
| 13 | | Conclusion (implemented as of 25 July 2007): |
| 14 | | * Create a [http://boinc.berkeley.edu/teams/ web site for registering BOINC-wide teams]. |
| 15 | | * In case of dispute over a name, the oldest instance of the team on an existing project wins. |
| 16 | | * Write an "export" script to export the list of teams and founders as XML. Include "previous founder" field. |
| 17 | | * 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 | | * Newly-created projects to use the update script (e.g. put in config.xml). |
| 19 | | * Resolve current inconsistencies manually; I will encourage project admins to help. |
| | 5 | This issue was resolved by creating a mechanism for |
| | 6 | [http://boinc.berkeley.edu/teams/ BOINC-wide teams]. |
