34 ms·

Open source is free to do what you will, but how many PR's does AWS send back to origin?

sg47 6y ago
Usually zero.
EwanToo 6y ago
I don't know about Rabbit MQ, but for redis AWS sends back a lot, so much that one of their developers is now a core team member https://redislabs.com/blog/redis-core-team-update/ https://redislabs.com/blog/redis-core-team-update/
NathanKP 6y ago
Disclosure: I work at AWS and this is my personal opinion. I've seen growing levels of AWS contribution back to upstream projects over the past four years. Teams start out by operating a piece of software at scale, whether it is Redis, Kubernetes, etc. After they have operated it for a while they discover the bugs or performance issues, or customers of the service complain about something. At that point the team now has enough real world experience with that software to begin to contribute back to upstream. It takes time: to learn the ins and outs of the software well enough to know where and what improvements should be made, to understand the software's design and history well enough not to make bad suggestions or contributions that were already determined to be dead ends in the past, and to earn the approval of the community and existing maintainers enough to get significant contributions accepted in the first place.
- wojack2dot0 6y ago
  Hey Thief, Which team you work on? Why would you cheer taking other people's work and defend the monetization? Do you publish PRs secretly pulling from public records, huh? You are not welcome here.
pabs3 6y ago
They have quite a number of commits from various authors to the Linux kernel at least: linux (master=) $ git shortlog -ns --author amazon 79 Arthur Kiyanovski 76 Gal Pressman 59 David Woodhouse 51 Sameeh Jubran 45 Netanel Belgazal 38 KarimAllah Ahmed 35 SeongJae Park 30 Jan H. Schönherr 26 Frank van der Linden 18 Andra Paraschiv 12 Paul Durrant 11 Talel Shenhar 10 Shay Agroskin ...

sg47 6y ago

Usually zero.

I don't know about Rabbit MQ, but for redis AWS sends back a lot, so much that one of their developers is now a core team member https://redislabs.com/blog/redis-core-team-update/ https://redislabs.com/blog/redis-core-team-update/

NathanKP 6y ago

Disclosure: I work at AWS and this is my personal opinion. I've seen growing levels of AWS contribution back to upstream projects over the past four years. Teams start out by operating a piece of software at scale, whether it is Redis, Kubernetes, etc. After they have operated it for a while they discover the bugs or performance issues, or customers of the service complain about something. At that point the team now has enough real world experience with that software to begin to contribute back to upstream. It takes time: to learn the ins and outs of the software well enough to know where and what improvements should be made, to understand the software's design and history well enough not to make bad suggestions or contributions that were already determined to be dead ends in the past, and to earn the approval of the community and existing maintainers enough to get significant contributions accepted in the first place.

wojack2dot0 6y ago
Hey Thief, Which team you work on? Why would you cheer taking other people's work and defend the monetization? Do you publish PRs secretly pulling from public records, huh? You are not welcome here.

pabs3 6y ago

They have quite a number of commits from various authors to the Linux kernel at least: linux (master=) $ git shortlog -ns --author amazon 79 Arthur Kiyanovski 76 Gal Pressman 59 David Woodhouse 51 Sameeh Jubran 45 Netanel Belgazal 38 KarimAllah Ahmed 35 SeongJae Park 30 Jan H. Schönherr 26 Frank van der Linden 18 Andra Paraschiv 12 Paul Durrant 11 Talel Shenhar 10 Shay Agroskin ...