News for hackers. Stuff that matters.
Re:"Giving up upstream-ing my patches & feel free to pick th... by perfmode on Saturday January 31, 2026 @03:23PM (#46840441)
maybe you’ve already done this and I’m sorry if i’m telling you the obvious.

You could analyze the repo to identify others who have modified the same files. and reach out to them specifically.

Re:"Giving up upstream-ing my patches & feel free to pick th... by Analemma_ on Saturday January 31, 2026 @03:40PM (#46840591)
I think if I were a random Google employee submitting Kubernetes patches at my day job-- i.e. not a project maintainer, but just someone in the K8s org chart-- I'd be kind of annoyed if I got cold-emailed asking me to help merge their patches. I'd probably trash that email and assume it was some kind of scam.

I get that the current system isn't working, but I don't think you should just go emailing random committers, that seems likely to just piss people off to no benefit.

Re:"Giving up upstream-ing my patches & feel free to pick th... by pklausler on Saturday January 31, 2026 @05:44PM (#46841662)
Github suggests reviewers to PR authors based on who's been modifying nearby code recently (ok, I don't know whether that's a general policy, but it happens to me all of the time). And for the past year or so I have been getting tagged to review more and more AI slop from newcomers to the project that we chose to maintain in public. I just immediately nope out of all reviews now if I don't recognize the submitter, because I don't scale enough to be the only actual human involved with understanding the code coming at me. This sucks for the newcomers who actually wrote the patch themselves, but I can't always tell. Put some misspellings in your comments and I'm actually more likely to review it!