BOINC software development

BOINC is free software, distributed under the ​Lesser General Public License (LGPL). 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 process
• Help wanted - programming
• boinc_dev, an email list for BOINC developers
• Coding style
• Using SVN
• Debugging the client on Windows

Get and build BOINC software

• Get source code?
• Software prerequisites
• Building on Unix
  • Installing python-mysqldb
• Building applications
• Building the client
  • Linux VM for building 'compatible' client

Design docs for current development

• Python-based simplified app development
• Python master/worker system
• Low latency computing
• Credit system proposal
• Organizational Grid Management

Implementation notes

Client

• File structure
• FSM structure
• Data structures?
• Main loop logic
• Client scheduling policies
• Host measurements
• Host identification
• Core client/application interaction (basic)?
• Automatic attach?
• Automatic update
• Memory management
• Screensaver logic
• Sandbox implementation
• BOINC Manager
• Windows installer (V5)
• Client package layout for Unix

Server programs

• The BOINC database
• Backend state transitions
• The logic of backend programs
• Debugging server components
• Notes on BOINC server security
• Export statistics for 3rd-party sites
• Single-job submission
• Adaptive replication
• Scheduler job matchmaking

Packaging

• [ClientSetupWinSix Version 6 Windows installer, design
• Version 6 Windows installer, implementation
• Unix client packaging
• Spec info for RPMs
• Unix project packaging

PHP code (web pages and RPCs)

• PHP database abstraction layer
• Style Sheets

Protocols

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

Simulation

• Client simulator
• Web interface to client simulator

Sourcecode documentation (in progress)

• API
• Client
• Manager
• Server components
• PHP code

Miscellaneous

• Cross-project identification?
• Simulator of a project using locality scheduling
• Preferences
• Trickle messages
• How to see what has changed between two versions of an executable
• XML formats
• Diagnostics API

Historical

Design docs for old versions, or for ideas that never happened.

• Python testing framework
• Version 4 runtime system
• Mac/Intel plan
• Old Mac project plan
• Design of version 5 setup
• Mac Menubar
• Usability discussion
• Disk management