The OpenChain Project helps to identify and share the core components of a high quality open source compliance program. OpenChain builds trust in Open Source by making things simpler, more efficient and more consistent. It is the industry-standard for managing Open Source compliance across the supply chain.
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.
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.
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.
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.
Yes, of course. Everyone from any company, organization or government is welcome to participate. We also welcome individuals interested in the topics we cover. There is no registration or membership required. Get started here.
There is no membership requirement to attend our meetings, to join our calls and webinars, or to help edit our standard and reference material. There is currently one membership level for the OpenChain Project: Platinum Membership. This is available to user companies (not vendors) and it provides a seat and a vote on our governing board and our steering committee. To learn more contact the General Manager at email@example.com. There is a partner program for vendor companies to engage with OpenChain. You can learn more here.
This is the FAQ for the OpenChain specification. We highly recommend all contributors to specification’s development review these questions and answers as a first step to contributing. There are four principles that guide the development of the specification:
- Build trust around the use of open source in constructing Modern Software Solutions.
- Less is More
- Avoid boiling the ocean – Focus specifically on providing the necessary and sufficient requirements of a “quality” compliance program
- Focus on meaningful pain points based on actual practice use cases
- Focus of the what and why (avoid the how and when)
- Embrace the implementation of different practices to solve a given requirement
- Avoid providing specific legal advice or specific best practices
- Function as an open development initiative – open to all to contribute – inclusion via discussion and consensus that adhere to these guiding principles
To define a core set of requirements a Open Source compliance program should satisfy to achieve: a level of trust that an organization provides the artifacts required to achieve Open Source license compliance for software it shares with others. Compliance artifacts consist of: source code, build scripts, license copies, attribution notices, modification notices, SPDX data and other materials open source licenses governing a software deliverable may require.
Does a FOSS program need to satisfy all the requirements of the specification to be considered OpenChain Conforming?
Does all software in an organization need to be covered by an OpenChain Conforming program to achieve program conformance?
No. Organizations are sometimes composed of different groups and/or departments which may have different programs and release procedures (e.g., engineering vs professional services). One Open Source program within an organization can be classified as OpenChain conforming if it satisfies the specification requirements while another program may not. One should not associate software with OpenChain conformance if it has not been reviewed under a program that has been assessed to be OpenChain conforming.
Does 85% of software staff in an organization need to have completed open source training within the last 24 months to achieve program conformance?
The 85% may not necessarily apply to the entire organization, but to the totality of those specifically responsible for the design, development and delivery of each Supplied Software release reviewed under an OpenChain conforming program. That is, all the Software staff participating in conforming program represents 100%.
No. The main objective of the specification provides a set of requirements that would help one evaluate whether an existing Open Source compliance program is sufficient. It focuses on the “what and why” aspects of a program and not the how or when. There are many different ways to construct a Open Source compliance program (how and when) such that each way would satisfy the specification. The specification provides a method of measuring whether a program has obtained a base line level of quality and consistency. This allows a software supplier to represent to their users that the compliance artifacts they deliver were prepared under a Open Source program that met a standard level of quality.
The Linux Foundation OpenChain Working Groups functions like an open source project by obtaining input from dozens of individuals, companies and organizations that have experiences preparing for and/or exchanging software in the software supply chain. There are no specific requirements for participating. The working group identified 6 main categories of a compliance program and then had contributors identify important tasks and deliverable for each category. The six categories were:
Know Your Free and Open Source (FOSS) Responsibilities [i.e., “Policy and Training”]
Assign Responsibility for Achieving Compliance
Deliver FOSS Content Documentation and Artifacts
Review and approve FOSS content
Understand FOSS Community Engagement
Certify Adherence to OpenChain Requirements
A number of reference documents were prepared and used as important sources of input into identifying core requirements of a quality compliance program. Several of those documents include:
- The Supplier License Compliance Audit (SLCA)
No. The OpenChain Specification is simply structured to provide a list of requirements where each requirement maintains a set of acceptance criteria (Verification Artifacts). Each requirement is a description of an important quality a Open Source program must maintain. The Verification Artifacts for a requirement represent a list of tangible artifacts that must exist in order for one to determine the specific requirement has been met. Although artifacts must exist, one is not required to make them public. The key goal of the specification is to foster trust around Open Source compliance between two parties exchanging software. Although currently an audit by a third party is not a requirement of the OpenChain specification, a partner or customer may ask for evidence of the Verification Artifacts as a condition for doing business (e.g., under an Non-Disclosure agreement). That is, the obligation to provide evidence of the existence of the artifacts, and the willingness to do so, is determined by the relationship entered into by two parties. It has been discussed that a future version of the specification may provide more specific guidelines on how to obtain third party certification.
No. The specification does not provide legal guidance. It does require an organization to designate a legal expert who can assist with legal guidance. Furthermore the specification requires that a process exists that ensures the appropriate attention is given to license obligation analysis and and fulfillment.
No, but it significantly increases the probability that license compliance will be achieved for software releases prepared under a OpenChain conforming program.
The OpenChain Curriculum working group has developed training reference materials that greatly facilitate the creation (or enhancement) of a Open Source compliance training program. The OpenChain Conformance working group has developed a questionnaire to guide an organization in self-certifying a program to be OpenChain conforming. The Linux Foundation sponsors various open source projects and initiatives that provide useful tools and compliance program resources that can help implement an OpenChain Open Source compliance program (e.g., SPDX, FOSSology, …). These resources can be found in the Linux Foundation Open Compliance Program.
In the specification text we do *not* use the term “Compliance” with respect to satisfying the spec requirements not to confuse it with “license compliance” or “Open Source Compliance program” which is frequently mentioned through out the spec. We use the term “Conformance” instead to mean a program has satisfied all the spec‘s requirements. It is possible that someone might make reference to the fact that their program “complies” with Spec 1.1 or that the program is “compliant” with version X of the spec which would be equivalent to stating the program “conforms” or has achieved “conformance” with version X.
The OpenChain Specification is designed to build trust around open source through being a clear and impartial standard. The approach is “less is more”, a focus on what and why (rather than how and when) and by functioning as an open project. Conformance is equally focused – it seeks to provide the simplest method of asking the right questions to measure conformance.
OpenChain Self-Certification is designed to assess the status of OpenChain Conformance in relation to a specific version of the OpenChain Specification. Organizations of any size can accomplish Self-Certification through the OpenChain Project Online Self-Certification Web App. A company that completes the Online Self-Certification confirms they meet the OpenChain Specification requirements.
OpenChain Self Certification page.
You will see an Unsubmit button at the bottom of the page after signing in to the Online Self-Certification site. Clicking this button will cancel your previous OpenChain Self-Certification submission. You can then re-submit the conformance check.
Artifacts are a tangible by-product of implementing OpenChain conformance policies. These can include digital documents, websites or paper documents public or private. All Artifacts should be verified internally by the organization using them.
Email firstname.lastname@example.org with the name of the organization you are concerned about and the reason you disagree with their submission. You should expect a response within 4 weeks.
If all information is correct, the submittal will automatically be approved by the system. Any omissions or incorrect answers will be reported by the user.
OpenChain Community website for information on how to join and contribute.
This FAQ is focused on the OpenChain Curriculum Training Slides. These are the core of the curriculum and have been widely adopted, adjusted and redistributed by companies, consultancies and law firms around the world. That said, the OpenChain Curriculum also contains checklists, flowcharts, guides and kanban documents. The FAQ equally applies to these: they are designed to provide simple, clear reference material to assist with confirming that a company has implemented – or can implement – the key requirements of a quality open source compliance program.
The OpenChain Curriculum slide deck provides reference material to meet OpenChain Specification requirement 1.2.
The OpenChain Curriculum is intended to help companies shipping Open Source Software and the companies receiving such software through the supply chain.
The reference slides are designed to be delivered in a half day training session. They are split into chapters to allow flexible delivery across different timescales and – given the CC-0 licensing – to allow companies to “pick and choose” the sections they need to expand on any existing in-house training materials.
The OpenChain Curriculum reference slides are focused on US law. Companies need to take this into account when considering the use of the reference slides for in-house training. Different legal jurisdictions have different legal requirements.
No, this is a reference deck. It is intended to help companies either get started with an OpenChain conformant compliance training program or to expand on existing training programs to help conform with the OpenChain Specification.