4 ms·

From my personal exchanges with people on Twitter on various contributions to projects in the Kubernetes ecosystem, I have frequently seen that some AWS employe

by alpb 6y ago

From my personal exchanges with people on Twitter on various contributions to projects in the Kubernetes ecosystem, I have frequently seen that some AWS employees (and sometimes the companies they partner with) want to make it seem like AWS is _really_ doing open source with real contributions. Every time I pointed my finger and asked, I got a response from such people "you should know not all contributions to the open source are code". I'm not gatekeeping what "real contributions" are: You can fund development of OSS, you can provide Project Manager support, you can publicize and organize events (for the sake of the tech; not sales), do DevRel for something, provide UX/UXR/design support etc. They're all real contributions. But for some reason, AWS contributions to 3rd party OSS projects stops right at "it works fine on AWS". It's kind of a meme at this point. Disclaimer: I work at GCP on Kubernetes/OSS.

_msw_ 6y ago
Disclosure: I work at Amazon on AWS infrastructure. And sometimes I have exchanges with ahmetb on Twitter. I cannot dispute the fact that Google has more developers working on k8s than AWS does. And that AWS developers have been focused more on making sure that k8s works great on AWS, rather than the core code. I've heard folks say that they think that k8s works better on Google because of all the Google developers using it. And that might have been true at some point. But, in any case, that means that you're probably going to see more activity making k8s work well on AWS than work in other areas. But it doesn't mean that other "3rd party" packages don't see more general activity that goes beyond "it works fine on AWS". Like the work in the upstream Linux kernel to apply the retpoline approach (invented by folks at Google, but not applied to upstream Linux) to mitigate Spectre. [1] It is meme when people pick it up and propagate it. [1] https://www.slideshare.net/ennael/kernel-recipes-2018-mitigating-spectre-and-meltdown-and-l1tf-david-woodhouse https://www.slideshare.net/ennael/kernel-recipes-2018-mitiga...

by alpb 6y ago

_msw_ 6y ago

Disclosure: I work at Amazon on AWS infrastructure. And sometimes I have exchanges with ahmetb on Twitter. I cannot dispute the fact that Google has more developers working on k8s than AWS does. And that AWS developers have been focused more on making sure that k8s works great on AWS, rather than the core code. I've heard folks say that they think that k8s works better on Google because of all the Google developers using it. And that might have been true at some point. But, in any case, that means that you're probably going to see more activity making k8s work well on AWS than work in other areas. But it doesn't mean that other "3rd party" packages don't see more general activity that goes beyond "it works fine on AWS". Like the work in the upstream Linux kernel to apply the retpoline approach (invented by folks at Google, but not applied to upstream Linux) to mitigate Spectre. [1] It is meme when people pick it up and propagate it. [1] https://www.slideshare.net/ennael/kernel-recipes-2018-mitigating-spectre-and-meltdown-and-l1tf-david-woodhouse https://www.slideshare.net/ennael/kernel-recipes-2018-mitiga...