News for hackers. Stuff that matters.
Re:AWS announces forks of Elasticsearch and Kibana by riquito on Thursday January 21, 2021 @07:09PM (#25866521)
> "We proposed to give back jointly at a significant level and were turned down." Adrian Cockcroft (VP AWS)

https://twitter.com/adrianco/status/1105178074499375106?s=20

Re:AWS announces forks of Elasticsearch and Kibana by jeswin on Thursday January 21, 2021 @08:36PM (#25867127)
There's a good quote on that thread which captures what AWS is doing with products like ElasticSearch:

"My argument is that AWS is eating seed grain, on its supply side, and doesn't know it."

Re:AWS announces forks of Elasticsearch and Kibana by SamoyedFurFluff on Thursday January 21, 2021 @07:12PM (#25866542)
We have no idea what “significant level” means here.
Re:AWS announces forks of Elasticsearch and Kibana by kapilvt on Friday January 22, 2021 @01:05AM (#25868859)
~1k lines (per enumerated prs in blog post) against millions of lines, aka less than a fraction of a percent.. plus ignoring code review, issue triaged etc. insignificant level might be more apt.
Re:AWS announces forks of Elasticsearch and Kibana by __blockcipher__ on Friday January 22, 2021 @01:20AM (#25868965)
Amazon is literally under no obligation to contribute any code back. Yet they do because most people prefer to merge upstream if they can, and Amazon is no exception.

Frankly Elastic has been very hostile at accepting PRs if they seem like they’d compete with Elastic’s proprietary offerings. Glaring conflict of interest. So I’m glad Elastic forced a full fork.

BTW, in case you didn’t realize this license change will not prevent Amazon from running their own fork. So even from a greedy business perspective Elastic made a horrible decision, even ignoring the ethics of lying to the community as they have done repeatedly and without showing any remorse.

edit: Fixed typo where I wrote "Elastic" instead of "Amazon" when talking about Amazon being no exception to preferring to merge upstream where possible