201–210 of 378 posts
Honestly, every relevant FOSS project should adopt a similar license to prevent exploitation from corporations.
The correct FOSS way to do this is using a FOSS license, an SSPL is not one of these. AGPLv3 is and provides a nice protection.
Earlier quoted context omitted.
You are being too cynical. Their argument is, more charitably: "We built this, we released it for free. Our business model is professional support and hosted services. In order for us, the creators of this software, to continue building it, we cannot allow megacorporations to freely spin up a loss-leading competitive service and cut us out."
Some observations: (1) It's interesting how much of the reasoning/argumentation for these restrictive licenses ultimately comes down to a more articulate form of "but that's not fair!". I also wonder how much the implicit beliefs that "unrestrained capitalism is a bad thing", "markets naturally lead towards monopolies", "antitrust law is legitimately necessary", etc are impacting peoples' reasoning here. (2) If they…
Sounds good to me. This is clearly targeted at big cloud providers who have been free-riding for years on the work of open source projects.
Yet now Elastic isn't content with competing in the market with its own managed offering (ironic because their offering is way better than AWS' anyway). Instead, they want to call themselves open source while switching to a proprietary license. Shameful.
Earlier quoted context omitted.
I'm not sure if people are really confused about this or sowing FUD. Using Elasticsearch to search your own webapp is not providing Elasticsearch as a service. It's using Elasticsearch to provide functionality in your application. Providing Elasticsearch as a service means allowing people to upload their own data and giving them an Elasticsearch instance to search it. There's some grey area where it's a question if y…
I wish it would be explained that way
For my side project, I am using a dual-licensed MIT/Apache (your choice) but with an exclusion which prohibits companies like AWS from offering it alone as a service. Here's a copy of the (quite human-readable) license:
https://gist.github.com/slimsag/2164520b9e249fbae4e08e2bdf6e...
Earlier quoted context omitted.
Even worse, Elasticsearch is a great product for adding "search" to your webapp. I don't see how integrating it doesn't run afoul of: Making the functionality of the Program or modified version available to third parties as a service includes, without limitation, enabling third parties to interact with the functionality of the Program or modified version remotely through a computer network...
I'm not sure if people are really confused about this or sowing FUD. Using Elasticsearch to search your own webapp is not providing Elasticsearch as a service. It's using Elasticsearch to provide functionality in your application. Providing Elasticsearch as a service means allowing people to upload their own data and giving them an Elasticsearch instance to search it. There's some grey area where it's a question if y…
Earlier quoted context omitted.
I highly doubt anybody chooses an explicitly free and open source license without intending to offer their software to users under the terms of that license.
And to flip it around, the question isn't whether Elastic envisioned use case X. The whole meaning behind FOSS is that you're explicitly saying "I don't care what your use case is, you're free to use it". So to later turn around and say "hey we never envisioned Amazon et all turning around and selling Elasticsearch as a service" is looking at it backwards. When you release something under Apache 2 (or a similar non-r…
Earlier quoted context omitted.
Even worse, Elasticsearch is a great product for adding "search" to your webapp. I don't see how integrating it doesn't run afoul of: Making the functionality of the Program or modified version available to third parties as a service includes, without limitation, enabling third parties to interact with the functionality of the Program or modified version remotely through a computer network...
I'm not sure if people are really confused about this or sowing FUD. Using Elasticsearch to search your own webapp is not providing Elasticsearch as a service. It's using Elasticsearch to provide functionality in your application. Providing Elasticsearch as a service means allowing people to upload their own data and giving them an Elasticsearch instance to search it. There's some grey area where it's a question if y…
Yes, and if you let your internal company blogging platform ping a service upon every new post, which then feeds that post into Elastic so blog posts across your company are searchable?
I suspect one way to avoid this would be “buy a commercial license” (or use Amazon’s fork if you’re so minded), but if you’re using Elastic’s open source offerings — I’d be careful about licensing anything under SSPL, whatever your intentions are.
It's just a change to make sure that those who resell ES as a service share their code. We use AWS's ES. And, as far as I'm concerned they already open-source their version. SSPL is actually helping the open-source community here
Which means AWS is going to fork their own version of ES and not push their fixes upstream.
I hope that SSPL becomes the standard for companies so that at least it becomes a known entity instead of a proliferation of bespoke licenses: like if CockroachDB moved to it as well. Personally, I'd rather see a more aggressive AGPL where REST calls are considered linking and trigger virality and I believe that would meet the definition of open source by the OSI while preserving the value of the commercial version.
i agree with your point on license proliferation. the osi has failed, in my opinion, for not approving sspl or something similar. i respect them a lot less for it than i used to. sspl does not technically impose any restrictions on any class of users; it’s just an extreme copy left license. instead, osi spent a time arguing about mongo business model, technical capabilities, and sales tactics. mongo eventually pulled…
I can understand the motivation - AWS' approach, particularly to elastic, has been pretty awful, and migrating away from Apache/GPL/MIT is like a coming of age for the big databases (Mongo, Cockroach, Elastic...) - but calling the article 'Doubling Down on Open' stretches credibility. Be honest, treat us like adults and cut all the 'we're doing this to remain open' crap. You are a public company who wants to increase…