I wanted to license our repository under AGPLv3, specifically so that folks who use our source code will have to share improvements back with the community. I asked JetBoom if this was possible and he stated:
As long as it doesn't override or conflict with the existing license anything is fine.
However, section 7 of the AGPLv3 states:
All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.
The JBGM License contains terms disallowing commercial use, which I'd consider a further restriction to AGPLv3, so I don't think it's possible to relicense entirely under AGPLv3.
This PR is an experiment in designing an exception to the JBGM License that incorporates the specific terms related to source conveyance from AGPLv3.
Other examples of license exceptions, although most of these provide additional freedoms vs. impose additional restrictions:
Overview
I wanted to license our repository under AGPLv3, specifically so that folks who use our source code will have to share improvements back with the community. I asked JetBoom if this was possible and he stated:
However, section 7 of the AGPLv3 states:
The JBGM License contains terms disallowing commercial use, which I'd consider a further restriction to AGPLv3, so I don't think it's possible to relicense entirely under AGPLv3.
This PR is an experiment in designing an exception to the JBGM License that incorporates the specific terms related to source conveyance from AGPLv3.
Other examples of license exceptions, although most of these provide additional freedoms vs. impose additional restrictions:
Testing Instructions
N/A.
Checklist
fixup!commits have been squashed