• Project personnel and structure
• BOINC Development information flow.
• The BOINCzilla bug database.
• boinc_dev, an email list for BOINC developers.
• Get and compile BOINC software
• BOINC coding style

Getting involved

BOINC is free software, distributed under the Lesser GNU Public License (LGPL). We are in constant need of 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. In any case, you are welcome to browse the source code and give us feedback. You should understand how BOINC works (for both participants and projects) before getting into the source code.

To get started, look at the BOINC bug database, fix a bug or two, and send your patches to the appropriate area owner. The following medium-to-large development projects are available:

• BOINC Manager: Change the Statistics tab to use a single graph with lines of different colors or styles for different projects.
• BOINC Manager: Show progress bars for file transfers and in-progress results.
• BOINC Manager: Use pie charts for disk usage
• Show when new versions of the core client and/or BOINC Manager are available. Could show in status line of Manager, as a balloon, or in Messages.
• BOINC Manager: sortable columns in Work tab.
• Support local editing of preferences (could be done in the Manager or a separate app).
• Core client: write a log file of result start/ends. (for use by 3rd-party software like BoincView).
• Disk space management: prevent disk space usage from exceeding user preferences, and enforce resource shares, with file deletion according to project policy.
• Use database IDs instead of names to identify results and WUs in the core client (to increase efficiency in the server, since indices on integers are apparently more efficient than indices on text fields). This involves minor but pervasive changes.

Client

• File structure
• FSM structure
• Data structures
• Main loop logic
• Client scheduling policies (new)
• Client scheduling policies (old)
• Debugging
• Host measurements
• Host identification
• Core client/application interaction (basic)
• Core client/application interaction (graphics)
• Client configuration files

Server programs

• The BOINC database
• Work distribution policy
• Backend state transitions
• The logic of backend programs
• Debugging server components

Protocols

• Protocol overview
• The scheduling server protocol
• Scheduling server timing and retry policies
• Data server protocol
• Persistent file transfers

Client extensions

• GUI RPCs
  Lets you control or show the status of BOINC clients, local or remote.

Web-based extensions (statistics and account management)

• Downloading statistics data
• Cross-project identification
• Web RPCs (possibly useful for statistics sites)
• Account management systems

Miscellaneous

• Python framework
• Preferences
• Trickle messages
• How to see what has changed between two versions of an executable.
• Spec info for RPMs