CD Foundation Blog

I think this "lesson" is not lost on many, including those that built and work with Jenkins and plugins. The Jenkins X project moved to a very different approach, a fresh start. see https://cd.foundation/ & https://jenkins-x.io (it works with Jenkins if you like, but natively uses the new pipelines and no SPOF masters). Might not be for everyone but worth a look. disclosure: cofounder of cloudbees here (wanted to comment on original article but not able to for some reason on medium).

Maybe you'll like the CD Foundation which seems to be modeled like its brethren Cloud Native Computing Foundation (CNCF) but focuses purely on continuous delivery pipelines and related services. https://cd.foundation/ PS: You don't want to build this stuff yourself, especially since you have stuff like ArgoCD and Tekton well capable to provide the basics ;)

Jenkins is now part of the CD Foundation (https://cd.foundation/) which is one of the linux foundation sub-foundations. Don't expect it to show up in the apache foundation.

Just something I wanted to share which might be of interest on this side of things. The CD Foundation has a SIG around MLOps which is pretty active and has some awesome folk participating. For anyone who's interested in this space, there's some more detail here: https://cd.foundation/blog/2020/02/11/announcing-the-cd-foundation-mlo…

I didn't write the job listing, but I understand it as being interested in OSS contributions, maybe already being a contributor to some projects. > hiring someone to contribute to open source, makes that person likely represent interest of the corporation That's true, and this is why my team is active within the project by having a member on the Technical Oversight Committee and several others in SIGs. The point is not to push our own agenda, we have made a lot of changes that are mainly relevant to our use cases and that don't necessarily make sense to upstream. Whenever we work on features that we know others would benefit from, we engage with the project's relevant committees and make the changes requested in pull request reviews. To be clear, I don't speak for my employer and this is only my own experience. Not all teams are like this. > I think much better idea to "contribute back" is to actually pay the existing contributors rather than having own pet one. Contributing features and supporting existing contributors in other ways are not incompatible. We have a whole team working on this code base full time, and so do other companies. Of course all of these people collaborate. This project is not really run by volunteers but mostly receives contributions from a number of companies (originally created at Netflix, large parts came from Google, etc). edit: See TOS members here for a list of the companies involved:…