Skip to content

[RFC] Introducing Dual Licensing strategy in Emmett and Pongo #260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

oskardudycz
Copy link
Collaborator

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 🙂

@oskardudycz oskardudycz added the RFC label Aug 4, 2025
@oskardudycz oskardudycz changed the title [RFC] Added RFC for Dual Licensing strategy in Emmett and Pongo [RFC] Introducing Dual Licensing strategy in Emmett and Pongo Aug 4, 2025
@oskardudycz oskardudycz force-pushed the rfc/002-License branch 2 times, most recently from a78487d to 52cb1c9 Compare August 4, 2025 11:13
Copy link

@watford-ep watford-ep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No concerns.

@oskardudycz
Copy link
Collaborator Author

No concerns.

Thank you @watford-ep for reviewing it, much appreciated!


### Adoption Barriers

Some organisati ons prohibit AGPL or SSPL. The dual approach maximises compatibility, but some potential users will be lost. Better sustainable development with narrower adoption than broad adoption of an abandoned project.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Some organisati ons prohibit AGPL or SSPL. The dual approach maximises compatibility, but some potential users will be lost. Better sustainable development with narrower adoption than broad adoption of an abandoned project.
Some organisations prohibit AGPL or SSPL. The dual approach maximises compatibility, but some potential users will be lost. Better sustainable development with narrower adoption than broad adoption of an abandoned project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants