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/05/17 19:23] mgisi |
openchain:specification-questions-and-answers [2018/10/05 13:40] mgisi [Does a FOSS program need to satisfy all the requirements of the specification to be considered OpenChain Conforming?] |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| ==== What are the Specification Guiding Principles? ==== | ==== What are the Specification Guiding Principles? ==== | ||
| There are four principles that guide the development of the specification: | There are four principles that guide the development of the specification: | ||
| - | - Build trust around the use of open source in constructing software solutions that are shared with others. | + | - Build trust around the use of open source in constructing software solutions that are shared with others (with a focus on license compliance). |
| - Less is More | - Less is More | ||
| * Avoid boiling the ocean - Focus specifically on providing the necessary and sufficient requirements of a “quality” compliance program | * Avoid boiling the ocean - Focus specifically on providing the necessary and sufficient requirements of a “quality” compliance program | ||
| Line 16: | Line 16: | ||
| * 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 best practices | ||
| - | - Function as an open development initiative - open to all to contribute - inclusion via discussion and consensus that adhere to these guiding principles | + | - 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. |
| 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. | ||
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
