- cross-posted to:
- purianesimo@fed.dyne.org
- cross-posted to:
- purianesimo@fed.dyne.org
You must log in or register to comment.
Haha, wow that was crazy, right everyone? Geeze, why did we even do that thing we did? What was that even? So weird!
Anyway, everything is back to the way it was before! Maybe even better! You can all come back now from the various forks and open alternatives you’ve spent the last 18 months migrating to!
Hashicorp watching with rapt attention while Hudson sits in the back and laughs.
Having contacted them to get a contract going for the non free license before I doubt they actually give a shit about Foss. They literally wouldn’t give me a price without knowing how many employees the company I was being outsourced to had. And we wanted to self host so it wasn’t even a matter of their costs they literally charge based on what you look like and the schemes were insane they would charge us for amount of active systems and their traffic when we were literally self hosting them
Lol, we had a sales rep in a meeting to talk about licensing while we were already self hosting and using it. When he heard that we would store business data and log data for the same app he said that’s two different use cases, and that we’d need two licenses.
This company may be dogshit, but seat count is the standard licensing structure for most employee facing business software, including on-prem.
Most business software licensing/CRM tools requires that information to generate a quote, as price will be dependent upon several factors, including volume licensing tiers i.e. volume discounts.
Sometimes, licensing structures are simple enough that an employee or rep might be able to give you a quick ballpark without that information, but that would be the exception, not the rule.
And all of that is assuming that pricing is only based on seats, when there could be a whole lot of other variables that would be required even for their system just to generate single quote e.g. core count, support terms, etc.
To be clear, none of that means anyone should trust, or switch back to, elasticsearch. It’s just a minor peak into the mundane horrors of business software licensing.
But I just moved to opensearch.
They got forked and were losing users?
Literally jumping
That’s where I stopped reading.
I work contract. I hope the ‘litchally’ morons never find out they’re paying a tax - just a few percent - for being morons.
So how does triple licensed code work as an end user? They have multiple packages and i pick the one with the license i like? Or just one package and i just declare im using the AGPL ‘essence’ in my instance?
You might say that the definition is ‘Elastic’
I don’t understand how their decision 3 years ago “worked” and that’s why they’re changing the license again.
Maybe it “worked” enough for the execs to realize it was a mistake?
The tl;dr is that we will be adding AGPL as another license option next to ELv2 and SSPL in the coming weeks.
Well, it is still yet to come and other license isn’t going away; i will wait and see
it kinda feels like they need more licenses to complete the collection idk
