Proposal: Adopt AGPL license for prototypes, MIT upon release of 1.0

callahad commented 8 years ago

We need to decide on how we're going to license Let's Auth.

I suggest we start with a strong copyleft license like the AGPLv3 while we're prototyping, since we want to discourage fragmentation until we know that our core design is sound.

Once we're happy with 1.0, I suggest we relicense our reference implementation to something maximally permissive, like MIT or ISC to encourage the greatest possible adoption of Let's Auth.

If agreed, we need to:

Add a LICENSE file with the license text.
Add a human-grokkable summary of this plan to our README.
Add a PULL_REQUEST_TEMPLATE and/or CONTRIBUTING file to ensure contributors agree with the licensing terms. Consider using the Developer Certificate of Origin (DCO) for this.

jleclanche commented 8 years ago

I don't think licensing on prototypes matters much, but I'm OK with this.

lofidevops commented 8 years ago

If your goal is "maximally permissive", perhaps Apache 2.0 is a good fit? In addition to copyright permissiveness, it provides patent permissiveness (which MIT/ISC do not)... http://en.swpat.org/wiki/Patent_clauses_in_software_licences#Apache_License_2.0

stephank commented 3 years ago

Closing this, because I believe it's no longer relevant. We're past prototype and in beta.

portier / portier.github.io

Proposal: Adopt AGPL license for prototypes, MIT upon release of 1.0 #2