[License-discuss] Seeking public comments for the OpenChain Specification version 2.0

[Gisi, Mark]

We are seeking public comments for the next version of OpenChain Specification.

For those new to the OpenChain Specification  - The OpenChain project developed a specification that defines a core set of requirements that a high quality Open Source Compliance program is expected to satisfy.  Although specification provides a minimum set of "must have" requirements, a great deal of flexibility is given on how an organization can implement them.

We have recently completed the last round of feedback from the OpenChain community and the spec draft is now being circulated more broadly for public comments which concludes on March 22nd. The current draft is available at:
   https://wiki.linuxfoundation.org/_media/openchain/openchainspec-2.0.draft.pdf
past readers of the spec might find the marked up version useful:
   https://wiki.linuxfoundation.org/_media/openchain/OpenChainSpec-2.0.draft.MarkUp.pdf
A high level summary of the changes made over the current version (1.2) can be found on page 3.

You can send feedback via:

*       the Mailing list: Openchain-specification at lists.linuxfoundation.org<mailto:Openchain-specification at lists.linuxfoundation.org>;

*       the issues wiki: https://github.com/OpenChain-Project/Specification/issues; or

*       replying to me directly if you wish to remain anonymous (mark.gisi at windiver.com<mailto:mark.gisi at windiver.com>)

To obtain a better understanding of the goals and the context in which the Specification was developed before providing feedback, you can review the following FAQ list:
              https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers

We look forward to your feedback.

best,
Mark


Mark Gisi | Wind River | Director, IP & Open Source
Tel (510) 749-2016 | Fax (510) 749-4552

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20190223/80fb3efa/attachment-0001.html>