Clarify license and add note about future migration to MIT#6
Clarify license and add note about future migration to MIT#6johnnyshields wants to merge 5 commits intomasterfrom
Conversation
…t be made under the MIT license
LICENSE
Outdated
| (see: LICENSE-MIT) in the future. Effective November 8, 2023, by | ||
| contributing to this repository, you consent to license under the MIT License | ||
| your contribution together with any other contributions to this repository, | ||
| its forks, and other repositories in the "prawnpdf" GitHub organization, | ||
| in addition to the existing license(s). This includes without limitation: |
There was a problem hiding this comment.
Do you mean that contributions done, for example, only to prawnpdf/prawn should fall under the MIT?
There was a problem hiding this comment.
Hmm I've dialed back the language for now so it covers just this repo. Basically, I'd like to ensure previous Prawn contributors have opted-in to MIT.
I think what I will do instead is make a checkbox in the Issue/PR template something like [ ] I agree for my Prawn contributions (including any other contributions) to be licensed under the MIT License.
Thoughts?
There was a problem hiding this comment.
I think you would need to differentiate between code for this repo and all other code written by the person which might include code for Prawn.
So maybe something like [ ] My contribution is licensed under the MIT license. (just for this repo) and [ ] I agree to license all my contributions that are/will be included in this repo under the MIT license. (for all code from that one person).
Edit: I think you may have part one already covered via the license file and the statement there. However, the second part makes more sense when the first is also there so that the difference between the two is clearly shown.
There was a problem hiding this comment.
Yep that's exactly what I was thinking.
2 participants
Clarify license terms
Add provision that future contributions must be made under the MIT license