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 18:22] mgisi [OpenChain Specification FAQ] |
openchain:specification-questions-and-answers [2018/06/11 03:18] mgisi [What are the Specification Guiding Principles?] |
||
---|---|---|---|
Line 2: | Line 2: | ||
===== OpenChain Specification FAQ ===== | ===== OpenChain Specification FAQ ===== | ||
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. | 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. | ||
+ | |||
+ | ====What is the objective of the OpenChain specification?==== | ||
+ | |||
+ | 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. | ||
==== 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 12: | 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. |
- | |||
- | ====What is the objective of the OpenChain specification?==== | ||
- | |||
- | 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. | ||
====Where can I obtain a copy of the current version of the specification?==== | ====Where can I obtain a copy of the current version of the specification?==== |