Re: announcing: Open Source License Compliance Handbook


J Lovejoy
 

Thanks Christian!  I’m glad you are finding it useful.

Cheers,
Jilayne

On Mar 13, 2019, at 2:05 AM, <christian.paterson@...> <christian.paterson@...> wrote:

Thanks Jilayne
 
This is really a great resource. Well done to you, the FINOS team and other contributors.
 
Regards
Christian
 
Head of Orange Open Source Governance
Cell. : +33 (0)6 84 72 94 18
 
De : openchain-bounces@... [mailto:openchain-bounces@...] De la part de J Lovejoy
Envoyé : mardi 12 mars 2019 20:19
À : openchain@...
Objet : [OpenChain] announcing: Open Source License Compliance Handbook
 
Hi OpenChain folks,
 
I want to tell you about a project I’ve been working on with Aaron Williamson and the Fintech Open Source Foundation (FINOS) that I think many of you may be interested in. 
 
FINOS has announced the initial release of the Open Source License Compliance Handbook. The Handbook is itself an open source project, available on Github. It consists of:
  • Structured compliance data about open source licenses, stored in a simple YAML format for easy consumption by machines and lawyers alike (licensed CC-BY-SA-4.0),
  • A Python script to compile the license entries and introductory material into an asciidoc-formatted markup document (licensed Apache 2.0), and
  • "Binaries" of the document in docx and PDF formats (as well as an intermediate DocBook version) (CC-BY-SA-4.0).
We're excited to get this resource into the hands of the community and get your input and contributions, as well as ideas on the potential to integrate this into all the great open source tooling that is out there. Aaron and I recognize that there's always the potential for ruffled feathers at efforts to "summarize" licenses and I have no doubt some of our efforts are imperfect. But the Handbook is meant for a particular purpose -- not to exhaustively summarize licenses or address every GPL corner case, but to help developers and compliance professionals address the most common requirements in the most common use cases.

Please take a look, file an issue, or submit a pull request :) (Be warned, FINOS requires signing a dreaded CLA first!)
 
Thanks,
Jilayne
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

Join main@lists.openchainproject.org to automatically receive all group messages.