Open-Source Standards Enforcement
When companies choose to open-source parts of their technology, they hope not only to give back to the community but also to grow the ecosystem around and adoption of their products. However, open-sourcing comes with challenges:
1. Contributors do not always follow policies around standardization, security, and best practices, so contributions require thorough reviews.
2. If the open-source project becomes popular, contributors outnumber maintainers, creating bottlenecks in the review process.
3. If pull requests (proposed changes) are allowed to languish for too long, contributors lose interest and the community wanes.
Enforce standards for open-source contributions with Datree
Organizations use Datree to set and enforce contribution policies for their open-source projects. Their communities flourish while standards are maintained and overhead is kept to a minimum. Here’s how:
1. Maintainers set policies in one place and activate enforcement throughout the GitHub org or in specific repos. For example, commit messages must match a certain format, no use of private keys, and more.
2. Administrators have visibility of all contributors, repositories, and packages used throughout the open-source project, as well as the policy compliance status of each.
3. Administrators have visibility of all contributors, repositories, and packages used throughout the open-source project, as well as the policy compliance status of each.