Maintain your BOINC project

If you operate a BOINC project, you can do various things to keep it healthy and growing:

Participate in the BOINC community

• Subscribe to the boinc_projects email list. If you have any problems or questions, post there (or create a Github issue).
• Attend the BOINC Projects Zoom call; these happen every few months and are announced on the email list.
• Attend the yearly BOINC workshop if you can.

Upgrade server software

Enhancements, bug fixes, and features are continuously being added to the BOINC server software. When there's a new release, we recommend that you upgrade.

To facilitate this, avoid modifying BOINC code. There are lots of override mechanisms that let you make customizations without modifying the code. If you need something additional, let us know (create an issue).

Check log files

Periodically check the server log files. Look for [CRITICAL].

Periodically check your Apache error log (usually /var/log/apache2/error.log). PHP warnings and errors appear here.

Develop new app versions

• If possible, develop versions for Windows, Mac, and Linux.
• Develop GPU versions. Vendor-specific toolkits (CUDA, Metal) are faster. OpenCL is slower but works on most GPU types (NVIDIA, AMD, Intel, Apple).

Interact with your users

• Post news items regularly.
• Monitor and participate in your forums. Appoint moderators if needed.
• Develop web content.
• Check for spam (user accounts, profiles, message boards). Use anti-spam mechanisms as needed.

Promote your project

Get to know your institution's PR person. Tell them about your project. Encourage them to seek coverage (mainstream media, social media) when you have something to announce.

Make sure your project is covered on your institution's web site, alumni magazine, etc.