Source code

• Download a tarball or .zip file (generated nightly).
• Browse the CVS repository via a web-based interface.
• Access the CVS repository directly, e.g. with a command like

  cvs -d :pserver:anonymous@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc
  

Source code for a typical BOINC application, SETI@home, is here.

If you are an experienced C++ system programmer 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 exactly how BOINC is supposed to work (for both participants and developers) before getting into the source code.

Bug database

View database of bugs and feature requests

Core client

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

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

Miscellaneous

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