4 ms·
In your pricing > faq - there is a mention of why you chose SSPL and NOT AGPLv3! And then you are on AGPLv3 ? Can you please share your thoughts on why you mo
by samblr 7y ago
In your pricing > faq - there is a mention of why you chose SSPL and NOT AGPLv3!
And then you are on AGPLv3 ?
Can you please share your thoughts on why you moved to AGPLv3 ?
- masonhensley 7y agoYa, repo looks like SSPL too... https://github.com/rudderlabs/rudder-server/commit/db9d53a05d82057c4763fd4d8fe519989e3baabd https://github.com/rudderlabs/rudder-server/commit/db9d53a05...
- soumyadeb 7y agoYes, very recently did we switch from SSPL to AGPLv3 (as noted in updates above)
- masonhensley 7y agoBut the repo says SSPL... in the readme & in the LICENSE file isn't that the source of truth? Or what matters to an organization evaluating adoption?
- soumyadeb 7y agoThanks for pointing it out. The LICENSE file was old, removed it now. The README says AGPLv3. Or am I missing something?
- deleted 7y ago[deleted]
- masonhensley 7y ago@soumyadeb - can't reply another level deep here. I'll create an PR in the repo. https://github.com/rudderlabs/rudder-server/pull/183 https://github.com/rudderlabs/rudder-server/pull/183 Cool project!
- soumyadeb 7y agoThanks for the pull request :) Merged...
- soumyadeb 7y agoOops, that was old. We had long discussions on and off HN about this topic. The biggest problem with SSPL is it is not an open-source license and we got a bunch of pushback (rightly so) for calling ourselves open-source. We initially went with SSPL to help prevent cloud providers from offering this as a service. However, there was a viewpoint that AGPLv3 already provides this and there is no reason for SSPL. Also, neither has been held up in court. In the end, we prioritized something which our community felt strongly about. The business risk was questionable anyway.