[RFC] Introducing Dual Licensing strategy in Emmett and Pongo#260
[RFC] Introducing Dual Licensing strategy in Emmett and Pongo#260oskardudycz wants to merge 3 commits into
Conversation
oskardudycz
changed the title
oskardudycz
force-pushed
the
rfc/002-License
branch
2 times, most recently
from
a78487d to
52cb1c9
Compare
oskardudycz
force-pushed
the
rfc/002-License
branch
from
52cb1c9 to
9667c1b
Compare
Thank you @watford-ep for reviewing it, much appreciated! |
Co-authored-by: Marcin Lach <marcin.lach.90@gmail.com>
|
|
||
| "Users interacting over a network" means any service where users access the functionality - web applications, APIs, any network protocol. This applies only to modifications of the licensed software itself. | ||
|
|
||
| Many developers misunderstand this. They believe AGPLv3 requires open sourcing their entire application. It doesn't. If you build a banking system using Emmett, your business logic remains proprietary. Only if you modify Emmett's core event sourcing engine and expose that modified version as a service would you need to share those Emmett modifications. |
There was a problem hiding this comment.
I think you might be wrong about this. There's a lot that has yet to be litigated in a court of law, but based on my reading of the linking discussion, integrating a (A)GPL library into your code, regardless of whether you change the GPL library code, is considered a derivative work, which in turn must be shared under the same license. I think in part it has to do with whether it is integrated as an external program, or the code interfaces are directly integrated into your code.
There was a problem hiding this comment.
More in the GPL FAQ. There is the LGPL which behaves more like what you're describing here.
|
I'm glad there are more people out there who see the value of SSPL. I have been mulling over using SSPL exclusively, but the public perception of it is so negative because the OSI didn't approve it. Anyways I read the full markdown and didn't see any typos or issues that popped out to me |
5 participants
Summary
I propose dual licensing Emmett and Pongo under AGPLv3 and SSPL. Users choose which license suits their needs. The intention is to establish clear, flexible licensing for users and due diligence to prevent exploitation, enabling a sustainable model for maintainers.
🙏🥺 We're really open to your questions, suggestions and constructive criticism.
See full human-Readable form: https://github.com/event-driven-io/emmett/blob/rfc/002-License/rfc/002-License.md
Feedback is more than welcome!
Feel also invited to join our Discord Channel if and discuss that in the dedicated topic 🙂