| Version 1 (modified by , 16 years ago) (diff) |
|---|
Development projects
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.
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.
To get started, read about the BOINC software development process. 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 area owner, sketching what you want to do and how. Work with the the area owner to carry out and check in the work.
The following development projects are available
Web features
(Requires advanced knowledge of PHP and MySQL.)
No results
Expand descriptions | Assigned tickets (0)
Applications
Expand descriptions | Assigned tickets (0)
Core client
(Requires advanced C++ system programming experience)
- #39
- Add a project backup function
- #40
- upload optional if error
- #41
- differentiate between number of CPUs to use in idle and busy mode
- #203
- Seperate cpu options for active/idle
- #333
- Confidence limits on times
- #439
- supply normal output with abnormal termination
- #545
- Seperate processor options for 'While computer is in use' and 'not in use'
- #561
- Support IPv6 on GUI RPCs
- #579
- Multiple CPIDs in Hosts
- #1165
- Native systemd service file for boinc-client
Expand descriptions | Assigned tickets (0)
Installer
- #393
- Make BOINC service start Automatic (delayed start).
- #581
- Make BOINC more efficient to deploy to mulitple hosts
- #582
- Make BOINC more efficient for corporate networks -
- #627
- Core client config file locations
- #698
- Use Windows (un)installer to fully uninstall WCG/BOINC
- #730
- Add summary of install choices to installer
- #736
- BOINC folder names
- #881
- BOINC Manager starting from the registry.
- #955
- Add Windows Explorer link to Data directory to Programs->BOINC
Expand descriptions | Assigned tickets (2)
BOINC Manager
(Requires experience with WxWidgets GUI toolkit)
No results
Expand descriptions | Assigned tickets (0)
Server/Back? End
(Requires advanced C++/Unix system programming experience)
Expand descriptions | Assigned tickets (0)
Please check with area owner or David Anderson before undertaking any of these.
