| | 1 | = The BOINC development process = |
| | 2 | |
| | 3 | BOINC development is done by BOINC staff, by the staff of various BOINC-based projects, and by volunteer programmers. Development is divided into several areas. Each area is managed by an 'owner'. |
| | 4 | |
| | 5 | || '''Area''' || '''Owner''' || '''Key contributors''' || |
| | 6 | || API || Bruce Allen || Bernd Machenschalk || |
| | 7 | || BOINC Manager || Rom Walton || |
| | 8 | || Core client || David Anderson || John !McLeod, Carl Christensen || |
| | 9 | || Mac OS X || Charlie Fenton || |
| | 10 | || Testing and release management || Rom Walton || Jens Seidler || |
| | 11 | || Server || Bruce Allen || David Anderson || |
| | 12 | || Translations of GUI and web text || Jens Seidler || |
| | 13 | || Unix build system || Reinhard Prix || Eric Korpela || |
| | 14 | || Web features || Rytis Slatkevicius || |
| | 15 | || Windows installer and screensaver || Rom Walton || |
| | 16 | |
| | 17 | |
| | 18 | The BOINC development, testing and release process is shown below. Ovals represent people, rectangles represent information channels. A, B, C, D and E represent the different BOINC development areas. 'Owner A' represents the person who owns area A, as shown above. |
| | 19 | |
| | 20 | [[Image(http://boinc.berkeley.edu/dev_flow.png)]] |
| | 21 | |
| | 22 | Participants |
| | 23 | |
| | 24 | * Report bugs (or learn of workarounds) on the BOINC message boards. |
| | 25 | * Learn of new releases on the BOINC web site. |
| | 26 | * Note: we need ways of 'pushing' info to participants, e.g. via the Manager. |
| | 27 | |
| | 28 | Area owners |
| | 29 | |
| | 30 | * Reads the relevant BOINC message board on a regular basis. Decides if new bugs are present. Adds entries to the BOINC/Trac bug database. |
| | 31 | * Monitors the relevant categories of the BOINC/Trac bug database. Manages entries (delete, merge, prioritize, assign). |
| | 32 | |
| | 33 | Developers |
| | 34 | |
| | 35 | * Are assigned tasks via BOINC/Trac. |
| | 36 | |
| | 37 | Alpha testers |
| | 38 | |
| | 39 | * The boinc_alpha email list is used to give instructions, and for discussion of tests and procedures. |
| | 40 | * If find bugs, log them in BOINC/Trac. |
| | 41 | * Use web-based interface for submitting test summaries. |
| | 42 | |
| | 43 | Release manager |
| | 44 | |
| | 45 | * Decide when to create test releases; communicate with alpha testers via email list. |
| | 46 | * Decide when to make public releases, based on web-based reports and on contents of BOINC/Trac. |
