Open Source Requirements for COSS

The Contriboss (COSS) initiative distinguishes between the COSS Brand Usage Guidelines (which govern the use of the COSS Mark and adherence to its principles) and the underlying software licenses that apply to the actual code of COSS-branded projects.

COSS-branded projects must have open source code to ensure transparency and prevent vendor lock-in mechanisms. Any license type is acceptable as long as the code remains open source.

License Requirements for COSS-Branded Projects

Open Source Code Required

Requirement: The COSS initiative requires that software code of COSS-branded projects be open source, but does not restrict the license type.

Why Open Source?

• Transparency: Open source code ensures users can inspect, understand, and verify that no vendor lock-in mechanisms are present.
• Freedom from Lock-in: Open source prevents hidden dependencies or restrictions that could create vendor lock-in.
• Community Trust: Open code builds trust and allows community verification of COSS principles.
• Interoperability: Open source enables better integration and prevents proprietary barriers.

License Flexibility:
Projects can use any license type - MIT, GPL, Apache, BSD, proprietary licenses, or any other license - as long as the code is open source and free from vendor lock-in mechanisms.

Important Distinction

• The software license governs the rights and permissions related to the software code itself.
• The COSS Brand Usage Guidelines govern the use of the COSS Mark and the project’s adherence to the COSS Principles (neutrality, anti-lock-in, etc.).
• A project must have open source code and comply with the COSS Brand Usage Guidelines to be considered a COSS-branded project.
• The specific license type is not restricted - the focus is on open source transparency and anti-vendor lock-in principles.

Disclaimer: This page provides general information. It is not legal advice. For legal advice regarding software licensing, please consult with a qualified legal professional.