Why are we doing this? OpenChain is at the top of the compliance stack defining inflection points where processes should exist. We leave it up to individual companies to select the appropriate process content for their size, market and customer base.
-
-
Show this thread
-
However, we provide reference material like policies, process examples and checklists. Frequent requests come in about automation and - given many of our community use open source tooling for open source compliance - it makes sense to unify and freely share this work onward.
Show this thread
End of conversation
New conversation -
-
-
Not a tool per se, but probably the REUSE principles are an interesting addition for your best practices. It makes adding copyright and licensing information to source files easier. Version 3.0 of the specification is likely to be published in August.https://reuse.software
-
We have had a version of REUSE as part of the
@openchainproj reference material for a while: https://github.com/OpenChain-Project/curriculum/blob/master/guides/reusing_software.md … It would be super great if FSFE contributes the new version under CC-0 too!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.