Open Source PR Rejected With Maximum Politeness After Significant Effort
Description
A mobile screenshot of a GitHub pull request titled 'feat: Plan mode' on the google-gemini/gemini-cli repository. A collaborator named jacob314 posted a comment thanking @linegel for their hard work, saying they will 'definitely take everything you did in this PR under consideration' as they work to implement plan mode, and that they'll 'loop you in as we start to have PRs ready for review.' However, the comment then states they 'unfortunately won't be able to accept this PR' due to 'a lot of nuances to how this will need to be implemented.' The collaborator also mentions adding a lock emoji 'maintainer only' label to certain issues to clarify which contributions won't be accepted. At the bottom, the PR is shown as 'closed with unmerged commits' by jacob314. The screenshot was taken at 22:31 with Slack notification visible in the status bar
Comments
18Comment deleted
Translation: 'We love your free labor, we'll steal the ideas, but the actual commit authorship? That's maintainer only.' The corporate open-source playbook, page 1
"fuck off" label just dropped Comment deleted
I can imagine this hurt a bit. Comment deleted
Is this the same Google that requires an officially signed clearance for submitting your code? One must be really motivated to pass through all this, not to mention the actual code review which may result in multiple iterations of refactoring the submission. Comment deleted
I was fine with it As well as total close of PR to be honest Typically I only care about work being done and done properly Comment deleted
I don't understand. Is it that from their pov your PR sucks but the first paragraph is corporate correctness? Comment deleted
Nah, they just didn’t had any specs anywhere for that feature But plan mode is absolutely essential for anyone doing vibe coding with serious face Aaand, instead of moving in at least some iterations they decided that they will prefer to not have it for now at all and handle it by themselves It’s not that bad idea actually, the real problem is that this feature is still missing Comment deleted
lmao Comment deleted
F tho Comment deleted
F Comment deleted
F Comment deleted
Plot twist: no one ever heard any feedback from UX team since then 🥲 Comment deleted
common big corpo "open source" problem Comment deleted
not contributing to mastodon anymore for this exact reason. and they're not even that large, especially back when I still contributed Comment deleted
At least Google guys are all over social networks and they actually talked to me in DMs on Twitter and LinkedIn (don’t judge the platform choice, it’s not a point) Comment deleted
I’m intrigued if they will actually "loop me in" once they will start work on this epic Comment deleted
"cам решу~" ("i'll deci~de") I mean, they just want to do some important features by themselves, taking much more time than by free labor... But yeah, UX, they definitely should make a couple of dozens of meetings about that, sure. Comment deleted
"The worst she can say is no" 🥀 Comment deleted