Choose a permissive licence

cds-snc / technical-playbook-manuel-technique

CDS Technical Playbook - Manuel Technique SNC

https://cds-snc.github.io/technical-playbook-manuel-technique/

4 stars 4 forks source link

Choose a permissive licence #2

Closed gcharest closed 7 months ago

gcharest commented 3 years ago

Great work on the playbook! I just wanted to point out that this should be the default when possible.

Depending on the tech stack and architecture choices, you may be required to choose a less permissive licence for compliance purposes.

Which also goes into the automated testing: dependencies licence compliance can be highly automated so that should most likely be part of your project setup.

Thanks! :+1:

wmoussa-gc commented 3 years ago

Thanks Guillaume for your feedback and suggestion. I think that make sense. I was expecting such nuances to be raised. I'm just not sure yet if we should just clarify the skill description or add some extra notes in a reference section. What do you think?

gcharest commented 3 years ago

Probably at least a few notes with regards to compliance: in a Dev team, it does mean being able to know all your dependencies. If you choose a licence, it must abide by the choices you took in terms of development.

Heather Meeker's examples are usually a good way to visualize what we should be thinking of when putting software out there (whether it's OSS or not):