| | 2 | |
| | 3 | We need volunteers to help with software testing and development. If you have one or more of the relevant technical skills (C++ system programming, PHP/MySQL web development, Wxwidgets programming, autoconf/automake expertise, etc.) you may be able to help us maintain and enhance BOINC. |
| | 4 | |
| | 5 | 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. |
| | 6 | |
| | 7 | To get started, find a small bug fix or enhancement to do (look at the BOINC bug database, the email lists, or message boards for ideas). Look at the source code and think about how you would implement it. Then communicate with the [http://boinc.berkeley.edu/contact.php area owner], sketching what you want to do and how. Work the the area owner to carry out and check in the work. |
