DIDO Wiki

return to the TODO defacto Standards

There are no formal standards on Open Source projects. There are only guides.

Source: The following is from TODO on "Participating in open source communities"

Open source has become the de facto way to build software – not only in tech, but across diverse industries. As companies use open source code to build their own commercial products and services, they also see the strategic value of contributing back to those projects.

However, diving in without an understanding of those projects, their communities, and how they operate can lead to frustrations for those companies as well as the open source communities. Approaching open source contributions without a strategy can tarnish a company’s reputation in the open source community and incur legal risks.

This guide covers what it means to contribute to open source as an organization and how to become a good corporate citizen. Learn how open source projects are structured, how to contribute, why it’s important to devote internal developer resources to participation, and why it’s important to create a strategy for open source participation and management.

• Why contribute to open source?
• How open source projects are managed
• How contributions work
• What it means for an organization to contribute
• How to be a good corporate citizen when participating in an open source project
• Best practices to contribute code upstream
• How to create your open source contribution strategy
• 11 tips for mastering open source contributions
• Final words