This shows you the differences between two versions of the page.
Both sides previous 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/05/17 19:23] mgisi |
||
---|---|---|---|
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? ==== | ||
Line 14: | Line 18: | ||
- 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 | ||
- | |||
- | ====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?==== |