boinc/CONTRIBUTING.md

Contributing to BOINC

👍 First off, thank you for taking the time to contribute! It's people like you that make BOINC such a great tool. 👍

How Can I Contribute?

Get Connected

Want to connect with contributors?

• Join us on Slack
• Join the email lists:
  • BOINC Overall
  • BOINC Projects
  • BOINC Development
  • BOINC Alpha Testing
• Join one of the community calls:
  • The BOINC Projects call occurs quarterly and is announced on the BOINC Projects email list
  • The BOINC Contributor call occurs every other week and is announced on the BOINC Development email list

Promote Volunteer Computing

Want to help promote volunteer computing and work on ways to attract new users? Join the #communications channel on Slack

Help Translate

See: https://boinc.berkeley.edu/trac/wiki/TranslateIntro

Help Test

You can help new versions of the client.

• Become an Alpha Tester
• Signup to be a BOINC Android Tester

Report Bugs

Did you find a bug? Make a Bug report.

• Ensure the bug was not already reported by searching on GitHub under Issues.
• If you're unable to find an open issue addressing the problem, open a new one.

Suggest Enhancements

Do you have a feature idea? Make a feature request.

• Ensure the feature was not already requested by searching on GitHub under Issues.
• If you're unable to find an open issue addressing the idea, open a new one.

Contribute Code

Do you want to fix a bug or implement a new feature? Read about how to implement a code contribution.

Styleguides

BOINC Coding Styles

See https://boinc.berkeley.edu/trac/wiki/CodingStyle

Git Commit Messages

• Use the present tense ("Add feature" not "Added feature")
• Use the imperative mood ("Move cursor to..." not "Moves cursor to...")

Thanks! ❤️

BOINC Team