384
Code Rule
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Feb 2024
384 points (100.0% liked)
196
16484 readers
1556 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 1 year ago
MODERATORS
I'm honestly glad Linus learned to tone down this kind of talk or at least reserve it for situations in which it is more merited.
Because while in the majority of instances he was correct, he left a lot of folks feeling like The Dude from The Big Lebowski.
For a long time it was a particularly hostile environment to people trying to learn the ropes of open source contribution.
However, on the flip side, I am also glad he hasn't turned it off completely, because while it is important to foster a welcoming and inclusive environment, sometimes creating that welcoming environment involves sternly telling someone off about their behavior, when that behavior is unwelcoming or generally unhelpful.
Anyway, applause for Linus for showing emotional and social growth.
i agree with you except here
noone there is learning, and mainteiners also aren't paid to teach anyone
Wrong. Dead wrong.
In the email chain subsequent to this exchange Linus even addressed the fact that the contributor would be better off learning about kernel development by focusing on the removal of unnecessary code and clean up.
No one jumps into kernel development knowing everything.
Maintainers need to teach people, not just about the culture and ethos, but about best practices and Linus had taught people constantly.
He has also learned a lot from others. To suggest otherwise is to think that Linus knew everything about kernel development back when he first began Linux development.
The kernel development isn't supposed to be the place to learn
It absolutely is. It's not the place to learn the basics obviously, but members need to learn what is expected of them, just like on any other team/organization.
Linus's outbursts absolutely hinder growth. He's lucky that his project has become so important and people will work on it regardless, but he and the Linux kernel would have been better off if he was wasn't driving people away as much as he was.
If they don't know what is expected of them or think they'll get by with shit code then I think it's fairly understandable to tell them to at least lurk moar.
I'm just worried with him gone if shitty code and practises will seep in.
There are projects out there with excellent practices with a good culture surrounding quality where people aren’t told to kill themselves. There are other ways to establish that culture and set high expectations.
No doubt, but I can't say I much disagree with his sentiment about requiring sudo password for connecting to a wifi.