Skip to content

How to Contribute#

Issues and suggestions can be logged on GitHub

Want to fix it yourself#

We'd love to accept your patches and contributions to this project. There are just a few small guidelines you need to follow.

When you are ready to get started developing, see our development guide for how to get started!

BitOps Community Meetings#

Join bi-weekly community meetups organized by the BitOps core team and contributors. Every 2nd Wednesday at 12:00 PM US East we’re gathering for 1 hour to discuss the ongoing BitOps work, issues, plans, and ideas.

General Agenda:

  • Roadmap and Milestones
  • Issues and Discussions
  • Features and Proposals
  • Use cases and user Adoption

See BitOps Community Meetings for more info how to join.

We would like to invite everyone interested to join us!

Developer Certificate of Origin#

To contribute to this project, you must agree to the Developer Certificate of Origin (DCO) for each commit you make. The DCO is a simple statement that you, as a contributor, have the legal right to make the contribution.

See the DCO file for the full text of what you must agree to.

To signify that you agree to the DCO for a commit, you add a line to the git commit message:

Signed-off-by: Jane Smith <>

In most cases, you can add this signoff to your commit automatically with the -s flag to git commit. You must use your real name and a reachable email address (sorry, no pseudonyms or anonymous contributions).

Code reviews#

All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose.