4 ms·
The announcement claims: > All changes to Elasticsearch were sent as upstream pull requests (#42066, #42658, #43284, #43839, #53643, #57271, #59563, #61400, #6
by jrochkind1 6y ago
The announcement claims:
> All changes to Elasticsearch were sent as upstream pull requests (#42066, #42658, #43284, #43839, #53643, #57271, #59563, #61400, #64513), and we then included the “oss” builds offered by Elastic in our distribution. This ensured that we were collaborating with the upstream developers and maintainers, and not creating a “fork” of the software.
With links on the issue numbers. Why should we not understand this as contributing back?
- sg47 6y agoThat's 9 PRs vs, as someone pointed out below, roughly 41000 commits in the project.
- _msw_ 6y agoDisclosure: I work at Amazon on cloud infrastructure, but not directly on the codebase being discussed here. Someone pointed out elsewhere: *Correction after looking a bit closer, I think Amazon has submitted at least 600 PRs, they only listed 9 in the blog post. That's better but it still doesn't change the fact their business model doesn't allow the companies they're building on the backs of to have a sustainable revenue stream.
- myroon5 6y agoThe other comment claiming 600 Amazon PRs was mistaken: https://news.ycombinator.com/item?id=25866527 https://news.ycombinator.com/item?id=25866527
- _msw_ 6y agoThat's counting emails. Unlike other Git-based projects like the Linux kernel, it seems a lot of commits are made with users.noreply.github.com email addresses. For example. commit 8e413f85e8978da83db107aae51e5543d4779dba Author: paulward24 <52216289+paulward24@users.noreply.github.com> Date: Wed Jul 3 04:37:07 2019 -0700 Ensure to access RecoveryState#fileDetails under lock Closes #43840