What Does The Project Contain?
Our Specification creates trust between organizations. Our Conformance allows new organizations to join the circle of trust. Our Curriculum supports implementation by entities of any size. The result is that Open Source becomes predictable, understandable and optimized for internal and external supply chains of any type.
Who Conforms To The Specification?
We maintain a list of organizations that have a publicly announced OpenChain Conformant Program. Due to the nature of the OpenChain Specification as a supply chain standard, primarily focused on the relationship between suppliers and purchasers, there may be a number of organizations that are conformant without public announcement.
How Is The Project Organized?
The OpenChain Project has four work teams that anyone can contribute to:
- Specification Work Team – identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy.
- Curriculum Work Team – provides training material to help companies meeting the Specification education requirements.
- Conformance Work Team – helps companies check that they are adhering to the Specification requirements.
- Onboarding Work Team – creates overview information to make it easy to explain and understand the OpenChain Project.
There are three committees for member companies:
- Governing Board – Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
- Steering Committee – Development, management and updating of the OpenChain Compliance Specification.
- Outreach Committee – Designing, developing and executing efforts to build an OpenChain compliance ecosystem throughout relevant supply chains in collaboration with the Governing Board.
How Does It Related To CII Best Practices?
OpenChain and the CII Best Practices are both Linux Foundation initiatives that identify FOSS process quality criteria. OpenChain focuses on i) improving compliance programs within organizations that use FOSS from different projects in their solutions and ii) the process for contributing back. In contrast, the CII best practices badge focuses on criteria for well-run FOSS projects themselves. See the CII Best Practices website if you are interested in getting a CII Best Practices badge.