11 ms·
These problems are complex. If companies start putting together tiger teams to support open source then they never really get to everything they use, just what
by kodah 6y ago
These problems are complex.
If companies start putting together tiger teams to support open source then they never really get to everything they use, just what open source projects are most important to them.
When companies fork/adopt/insert themselves we have concerns over corporate influencing, sustainability, and independence.
When companies just throw willy nilly money at big hunking shells like the CNCF it gates projects into this very corporatized world that is quite distinct from open source culture, and again damages open source.
This just touches on the contribution model, this doesn't even touch on the thousands if not hundreds of thousands of license violations (if you're behind on updates who has time to go enforce licenses?) It mentions but doesn't touch on corporatization or undue influence.
I'm not sure I know what to do but it's a problem worth solving.
- mfer 6y ago> When companies just throw willy nilly money at big hunking shells like the CNCF it gates projects into this very corporatized world that is quite distinct from open source culture, and again damages open source. How does giving money to something like the CNCF gate projects? How is the world those are developed in differ culturally from open source culture? I've developed for CNCF projects and random projects (some of which have become popular). I didn't notice a culture difference. I did notice an outside support difference. I'm curious what you mean.
- kodah 6y agoThe CNCF is pretty distinct from organizations like Debian or The Linux Foundation, and even Debian comes under the same sort of fire I'm about to lay down here. At this time, I think it's more skepticism than the understanding of what the problem is, but it boils down to corporate influence and what level of influence companies are allowed to have on projects. Companies have several methods of influence: - Financial contributions (and the projects nature of dependence) - Developer interest and representation (eg: when a mega-corp installs a developer and combines that with things like funding) - Board representation A quick anecdotal example was the whole kerfuffle about Google using it's influence to insert kustomize into kubectl. [0] Big organizations like Debian or the CNCF are attractively large targets for the above concerns. [0] https://goteleport.com/blog/kubernetes-kustomize-kep-kerfuffle/ https://goteleport.com/blog/kubernetes-kustomize-kep-kerfuff...