4 ms·
I don't see what makes it different from any other open source project. Of course it's going to have technical leads and core committers, it's not like you can
by Zikes 11y ago
I don't see what makes it different from any other open source project. Of course it's going to have technical leads and core committers, it's not like you can go force a PR merge on jQuery trunk any time you please. I'm aghast that you would even suggest such a thing.
And CLA's aren't fun, but they're hardly new, either.[1]
If you don't like that it's Google, that's fine, but at least be honest with yourself about it. But unless you've submitted a PR or can cite a PR (on any Google OSS repo at all) that they've rejected purely on the basis that Google is somehow doing wrong by the developers, then what are we even talking about?
[1] https://en.wikipedia.org/wiki/Contributor_License_Agreement#Users https://en.wikipedia.org/wiki/Contributor_License_Agreement#...
- ajsalminen 11y agoTo me the problematic part that makes it different to at least some open source projects is that all those technical leads and core committers are apparently employed by Google (and working on company time, I assume). That could mean Google, and Google alone, gets to decide where it goes.
- Zikes 11y agoHonestly, the only criticism I'm hearing over and over is "because Google", and considering their track record with Chrome, Android, Angular, Polymer, Go, and literally hundreds of other open-source projects, I'm perfectly okay with that.