Skip to content

Contributing code to BOINC

David Anderson edited this page Apr 8, 2025 · 4 revisions

If you're interested in contributing code to BOINC, please read the following.

License and copyright

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.

Issues and tasks

BOINC uses Github to manage software development.

If you're looking for something to work on, scan the BOINC issue list for unresolved bugs or feature requests.

If you want to work on for which there's not an issue, create one.

Decide on a plan and a design

If you want to work on an issue, post a comment to the issue saying

  • that you want to work on it, and in what time frame
  • how you propose to address it (technical details).

The main BOINC developers (David Anderson and Vitalii Koshura) will see and review this. They may propose a different design. They have the final say. We suggest that you not write much code until they have agreed on a design.

Make a PR

Once a design has been agreed on, implement it (in a separate branch) and test it.

Your code must use the BOINC coding style.

When your code is finished, submit a pull request (PR) for your branch. The main developers may request changes in your code. When this is finished, they will merge it.

Clone this wiki locally