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 | ||
|
openchain:specification-questions-and-answers [2019/02/20 01:59] mgisi [OpenChain Specification FAQ] |
openchain:specification-questions-and-answers [2019/11/17 19:12] (current) mgisi [Does the specification describe how to comply with the most popular Open Source licenses?] |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| - Less is More | - Less is More | ||
| * Avoid boiling the ocean - Focus specifically on providing the necessary and sufficient requirements of a “high quality” compliance program | * Avoid boiling the ocean - Focus specifically on providing the necessary and sufficient requirements of a “high quality” compliance program | ||
| - | * Focus on meaningful pain points based on actual practice use cases | + | * Focus on meaningful pain points based on practical use cases |
| + | * If we could remove words and still preserve meaning and value then use fewer words | ||
| - Focus of the what and why (avoid the how and when) | - Focus of the what and why (avoid the how and when) | ||
| * Embrace the implementation of different practices to solve a given requirement | * Embrace the implementation of different practices to solve a given requirement | ||
| - | * Avoid providing specific legal advice or specific best practices | + | * Avoid providing specific legal advice or specific common practices |
| - | - Function as an open development initiative - open to all to contribute - inclusion via discussion and consensus that adhere to these guiding principles. Consider adopting best practices from standard initiatives which complement the open development approach. | + | - Function as an open development initiative - open to all to contribute - inclusion via discussion and consensus that adhere to these guiding principles. Consider adopting best practices from standard initiatives which complement an open development approach. |
| Line 30: | Line 31: | ||
| ====What does it mean that a software offering is OpenChain Conforming?==== | ====What does it mean that a software offering is OpenChain Conforming?==== | ||
| - | For the 1.0 version of the specification supplied software itself is not identified as being OpenChain Conforming. An Open Source compliance program which the software is prepared under is a candidate for OpenChain conformance. When a software supplier states they are OpenChain conforming it means they have a program that satisfies all the requirements of the OpenChain specification. A software supplier may declare the software offered was prepared under an OpenChain conforming program. Similarly, a software recipient may ask the supplier if the software they received was prepared under an OpenChain conforming program. | + | |
| + | An organizaition's Supplied Software itself is not identified as being OpenChain Conforming. An Open Source compliance **program** which the software is prepared under is a candidate for OpenChain conformance. When a software supplier states they are OpenChain conforming it means they have a **program** that satisfies all the requirements of the OpenChain specification. A software supplier may declare the software offered was prepared under an OpenChain conforming **program**. Similarly, a software recipient may ask the supplier if the software they received was prepared under an OpenChain conforming **program**. | ||
| ====Does all software in an organization need to be covered by an OpenChain Conforming program to achieve program conformance?==== | ====Does all software in an organization need to be covered by an OpenChain Conforming program to achieve program conformance?==== | ||
| Line 38: | Line 40: | ||
| ====Does the specification serve as a best practice guide?==== | ====Does the specification serve as a best practice guide?==== | ||
| - | 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. | + | 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 provided were prepared under a Open Source program that satisfied a core set of requirements. |
| ====How was the specification developed?==== | ====How was the specification developed?==== | ||
| Line 49: | Line 51: | ||
| - Understand Open Source Community Engagement | - Understand Open Source Community Engagement | ||
| A number of references that document the history of the specs development include: | A number of references that document the history of the specs development include: | ||
| - | * {{https://lists.linuxfoundation.org/mailman/listinfo/openchain-specification | specification mailing list}} | + | * {{ https://lists.openchainproject.org/g/specification | specification mailing list}} |
| * {{ https://github.com/OpenChain-Project/Specification/issues | github issue tracking}} | * {{ https://github.com/OpenChain-Project/Specification/issues | github issue tracking}} | ||
| * This FAQs | * This FAQs | ||
| Line 55: | Line 57: | ||
| ====Is a third party audit required to declare an Open Source Compliance program to be OpenChain Conforming?==== | ====Is a third party audit required to declare an Open Source Compliance program to be OpenChain Conforming?==== | ||
| - | No. 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 Materials). Each requirement is a description of an important quality a Open Source Compliance program must satisfy. The Verification Materials for a requirement represent a list of tangible evidence that must exist in order for one to determine the specific requirement has been met. Although evidence 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. A partner or customer may ask for evidence of the Verification Materials 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 materials, and the willingness to do so, is determined by the relationship entered into by two parties. | + | No. The specification was designed to provide a list of requirements where each requirement maintains a set of acceptance criteria (Verification Materials). Each requirement is a description of an important quality an Open Source Compliance program must satisfy. The Verification Materials for a requirement represent a collection of evidence that must exist in order for one to determine the specific requirement has been met. Although evidence 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. A partner or customer may ask for evidence of the Verification Materials 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 materials, and the willingness to do so, is determined by the relationship entered into by two parties. |
| ====Does the specification describe how to comply with the most popular Open Source licenses?==== | ====Does the specification describe how to comply with the most popular Open Source licenses?==== | ||
| - | 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. 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. |
| ====Does OpenChain program conformance guarantee license compliance?==== | ====Does OpenChain program conformance guarantee license compliance?==== | ||
| Line 76: | Line 78: | ||
| ==== What is the different between Conformance vs Compliance ==== | ==== What is the different between Conformance vs Compliance ==== | ||
| - | 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 version X of the spec 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. | + | In the specification text we do *not* use the term "Compliance" with respect to satisfying the spec requirements - so 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 version X of the spec or that the program is "compliant" with version X of the spec which would be equivalent to stating the program "conforms"; "is conformant"; or "has achieved conformance" with version X. |
openchain/specification-questions-and-answers.1550627977.txt.gz · Last modified: 2019/02/20 01:59 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
