this post was submitted on 30 Aug 2024
110 points (93.7% liked)
Open Source
31359 readers
347 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
I don't follow. ElasticSearch was only available under proprietary source-available licenses. Now, it's also available under the AGPL, which is open source, meaning ElasticSearch is now open source software. What part of this is deceptive or contradictory?
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.
The SSPL is irrelevant, you pick the AGPL license and the SSPL doesn't apply to you.
Qt is dual-licensed as proprietary and LGPL and nobody complains about that, KDE is in most distro's repos. You pick the LGPL licensed version and you're good to go, the proprietary license doesn't apply to you.
What benefits does the developer get from using both licenses, if the user gets to decide which one to use? Serious question, by the way. I truly don't know.
The developer benefits from reaching more people, some of whom are likely to purchase the proprietary license. Or sometimes you dual-license just so that licenses are compatible. Each license has pros and cons for both the developers and the users.
Qt for example, the LGPL means you need to dynamically link to it, and if you ship your own Qt libraries you must provide the source code for it. But if you're a company that writes proprietary software and can't dynamically link, then you can purchase the proprietary license which allows you to do a lot more, but you're compensating the devs for it. And for the Qt devs that's good because either you pay them, or you use it for free but must share your changes with everyone.
For ElasticSearch, that makes it so Amazon can't just patch it up and sell the modified version without sharing what they changed. They wanted to add back a FOSS license to stop the bleed to OpenSearch which many in the FOSS community switched to purely for the license because even separate software should be compatible license-wise if you want a sustainable FOSS project. But the AGPL requires sources merely for being able to talk to it over the network, so Elastic gets the free dev work, or the juicy license payments. The other free licenses achieve similar goals with technical differences that might matter for the user. But as a developer using ElasticSearch maybe you do want to ship your software under the SSPL, so you can pick the SSPL version.
Dual-licensing MIT/GPL for example, you can build proprietary software, or GPL software where you can vendor it in as GPL-only as well, and thus guarantee your user their GPL rights.
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.
And which parts does the AGPL violate? Because that's what the article is about: it becoming available under the AGPL.
Assuming they own the copyright (which I believe they do, since they were able to relicense it to begin with) they can absolutely offer it under a dual licensing arrangement even if the licenses are incompatible. It would only be an issue if other peoples' AGPLv3 licensed code was in there, but as it is not the only copyright they would theoretically be violating is their own, which is literally not possible.
Dual licensing under a free software license and proprietary EULA is a common business model, especially when the free software license is a strong copyleft like the AGPL, since the proprietary licensors do not have to abide by certain conditions that free license users have to.
So source available. Not open source. Got it!
Isn't that the point of the article? It's not open-source currently, but will be, once the AGPL option is added.
But Shay was so excited.
I think you are confused. You can use ELK under AGPL with this news going forward. The fact that they have to retain SSPL, too, because of previous contributors under that license, has nothing to do with the fact that you can use AGPL going forward. I've read your other responses,but they all seem to go down the same seemingly incorrect direction.
Am I missing something?