Edit history
Earlier versions of Allow alternative licensing options, newest first.
Current version | Edited by Rex
Changes
Offer a dual licensing option, one that allows self-hosting without the AGPL-3.0 obligations while still letting the project maintain its open-source version.Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing discussions and didn't find a duplicate.Removed:
Show
Allow alternative licensing options
Edited by Rex
Changes
Offer a dual licensing option, one that allows self-hosting without the AGPL-3.0 obligations while still letting the project maintain its open-source version.Removed: ### Notes (optional)Removed: Removed: _No response_Removed: ### Checks
Show
Allow alternative licensing options
Problem
AGPL-3.0 introduces complexity, compatibility concerns, and potential legal liability that many teams and organizations simply can't take on. For those reasons, software under this license carries too much risk for most organizations and teams to consider.Proposed solution
Offer a dual licensing option, one that allows self-hosting without the AGPL-3.0 obligations while still letting the project maintain its open-source version.Checks
- ☑ I searched for existing discussions and didn't find a duplicate.
Original by Rex
Show
Allow alternative licensing options
Problem
AGPL-3.0 introduces complexity, compatibility concerns, and potential legal liability that many teams and organizations simply can't take on. For those reasons, software under this license carries too much risk for most organizations and teams to consider.Proposed solution
Offer a dual licensing option, one that allows self-hosting without the AGPL-3.0 obligations while still letting the project maintain its open-source version.Notes (optional)
No responseChecks
- ☑ I searched for existing discussions and didn't find a duplicate.