Re:AWS announces forks of Elasticsearch and Kibana
by sg47 on Thursday January 21, 2021 @06:40PM
(#25866248)
That's 9 PRs vs, as someone pointed out below, roughly 41000 commits in the project.
Re:AWS announces forks of Elasticsearch and Kibana
by _msw_ on Thursday January 21, 2021 @07:24PM
(#25866653)
Disclosure: 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.
Re:AWS announces forks of Elasticsearch and Kibana
by myroon5 on Thursday January 21, 2021 @07:39PM
(#25866762)
The other comment claiming 600 Amazon PRs was mistaken:
Re:AWS announces forks of Elasticsearch and Kibana
by _msw_ on Thursday January 21, 2021 @08:58PM
(#25867310)
That'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 <[email protected]>
Date: Wed Jul 3 04:37:07 2019 -0700
Ensure to access RecoveryState#fileDetails under lock
Closes #43840
> 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?