openchain:specification-questions-and-answers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
openchain:specification-questions-and-answers [2018/06/11 03:18] mgisi [What are the Specification Guiding Principles?] |
openchain:specification-questions-and-answers [2018/10/05 13:41] mgisi [Is a third party audit required to declare a FOSS program to be OpenChain Conforming?] |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| - | ==== Does a FOSS program need to satisfy all the requirements of the specification to be considered OpenChain Conforming? ==== | + | ==== Does an Open Source Compliance program need to satisfy all the requirements of the specification to be considered OpenChain Conforming? ==== |
| Yes. The specification was designed to provide a core set of requirements to ensure a certain level of program quality has been achieved. In order to ensure there are no significant gaps in an OpenChain conforming program that could lead to poor quality output, a program must satisfy all the requirements to be considered OpenChain conforming. | Yes. The specification was designed to provide a core set of requirements to ensure a certain level of program quality has been achieved. In order to ensure there are no significant gaps in an OpenChain conforming program that could lead to poor quality output, a program must satisfy all the requirements to be considered OpenChain conforming. | ||
| Line 58: | Line 58: | ||
| * The Supplier License Compliance Audit (SLCA) | * The Supplier License Compliance Audit (SLCA) | ||
| - | ====Is a third party audit required to declare a FOSS program to be OpenChain Conforming?==== | + | ====Is a third party audit required to declare an Open Source Compliance program to be OpenChain Conforming?==== |
| - | No. At least not yet. The [[https://wiki.linuxfoundation.org/_media/openchain/openchainspec-1.0.pdf|OpenChain 1.0 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. At least not yet. The [[https://wiki.linuxfoundation.org/_media/openchain/openchainspec-1.2.pdf|OpenChain 1.2 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. |
| ====Does the specification describe how to comply with the most popular FOSS licenses?==== | ====Does the specification describe how to comply with the most popular FOSS licenses?==== | ||
openchain/specification-questions-and-answers.txt ยท Last modified: 2019/11/17 19:12 by mgisi
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
