| Version 19 (modified by , 7 years ago) (diff) |
|---|
The BOINC development process
BOINC is free software, distributed under the Lesser General Public License (LGPL), version 3 or later. The University of California holds the copyright on all BOINC source code. By submitting contributions to the BOINC code, you irrevocably assign all right, title, and interest, including copyright and all copyright rights, in such contributions to The Regents of the University of California, who may then use the code for any purpose that it desires.
- Development Workflow
- Quality Assurance Workflow (under discussion)
- boinc_dev, an email list for BOINC developers
- Coding style
- Debugging the client on Windows
Development is divided into several areas. Each area is managed by an 'owner'.
| Area | Owner | Key contributors |
| API | David Anderson | |
| BOINC Manager | Charlie Fenton | |
| Client | David Anderson | |
| Mac OS X | Charlie Fenton | |
| Testing and release management | ||
| Server | David Anderson | Kevin Reed |
| Translations of GUI and web text | ||
| Unix build system | Eric Korpela | |
| Web features | David Anderson | Rytis Slatkevicius, Janus Kristensen |
| Windows installer and screensaver |
The BOINC development process involves interaction between various groups:
Participants
- Report bugs on the BOINC message boards.
- These are reported by message board moderators to the relevant area owner.
- Participants may also file bug reports in Github.
Area owners
- Fix bugs or delegate to contributors.
Alpha testers
- Test development releases and report problems via a Web-based system.
Release manager
- Monitor the Alpha-test results and notify area owners of issues.
- Decide when to create test releases; communicate with alpha testers via email list.
- Decide when to make public releases.
