4 ms·
Seeing some of the mailing list threads about this gives me anxiety. If you thought your PR review process was painful, try reading through some of the nitpick
by candiddevmike 3y ago
Seeing some of the mailing list threads about this gives me anxiety. If you thought your PR review process was painful, try reading through some of the nitpicks, useless feedback, and tangents Kent has fought through. You can find it on lore, I'm not going to link directly to anything specific.
As an outsider, there seems to be too many egos to placate when it comes to contributing to Linux.
- Szpadel 3y agothe same story was from ashai Linux developers. I saw on mastodon that they said they will not be upstreaming all changes for that reason
- tuna74 3y agoWhat won't be upstreamed?
- Szpadel 3y agoAFAIR this was post by Hector Martin but he didn't mention anything specific. He was mostly venting out his flustrations around review process. I tried to find any of those messages but mastodon search looks broken or I have no idea how properly search for specific user posts.
- nilstycho 3y agoI think you're referring to https://social.treehouse.systems/@marcan/111268799920192168 https://social.treehouse.systems/@marcan/111268799920192168
- tuna74 3y agoNot fixing everything in Linux is not the same as not upstreaming. Martin seems to want to upstream the code for the drivers but not touch anything else. Which is totally fair!
- viraptor 3y agoI don't think that's fair. He does touch other things to improve interfaces sometimes. I see this not as "not touch anything else", but rather "not touch everything else".
- arp242 3y agoHe seems to complain about everything and everyone, so I find it hard to take any of these complaints serious without direct and concrete examples.
- deleted 3y ago[deleted]
- tuna74 3y agoYes, and the biggest ego is the one who started it all.
- dboreham 3y agoThis is because code review without some sort of organizational structure becomes a form of institutionalized mental abuse.
- tux3 3y agoI don't think that explains it, there is a structure (various levels of mainteners) and mainteners aren't outright malicious. Theoretically there is also a CoC. The problem's more that you're going to have strong conflicts of opinions that you can't hash out face to face between people who are already overworked and under stress It's hard for devs, but you also have people quitting because the maintener position is not just thankless, but fucking thankless. It is not as simple as reviewers abusing developpers because of a lack of structure. A large part of the kernel is under resourced, lacking mainteners, and that is stressful for everyone