this post was submitted on 30 Aug 2024
109 points (93.6% liked)
Open Source
30511 readers
394 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Because it does not comply with the Open Source definition?
SSPL violates these two:
ELv2 violates these four:
Simply putting in the AGPLv3 does not remove unfair restrictions. I mean, SSPLv1 is not compatible with AGPLv3.
Do you... not know how multi-licensing works? You can use the project's code under the terms of whichever license you prefer, you don't use all three at once. Simply putting the AGPLv3 does remove unfair restrictions, because it means you don't have to use either of the proprietary licenses the project was previously only available under.
This is getting so tiring because I've mentioned it earlier too - section 13 of AGPLv3 and SSPLv1 have different scopes. Just read this article by ScyllaDB - this is with respect to MongoDB, which has a similar licensing model. If it were "really" open-source, then RedHat wouldn't have removed MongoDB from their "free" repositories.
Are you saying that the mere existence of the option of using a non open source license invalidate the provisions in the open source option? That is, if they offered only AGPL, they would be oss but if they offer your choice of AGPL and something non oss, the AGPL option would no longer be oss too? The article you linked does not address this as far as I can tell.