Slashdot Mirror
How New, Polite Linus Torvalds Points Out Bad Kernel Code (phoronix.com)
Linus Torvalds "has shown already for the new Linux 4.20~5.0 cycle he isn't relaxing his standards but is communicating better when it comes to bringing up coding," reports Phoronix, adding "So far it looks like Linus' brief retreat is paying off with still addressing code quality issues -- and not blatantly accepting new code into the kernel as some feared -- but in doing so in a professional manner compared to his past manner of exclaiming himself over capitalized sentences and profanity that at time put him at odds with some in the Linux kernel community."
AmiMoJo quotes their report: Last Saturday he took issue with the HID pull request and its introduction of the BigBen game controller driver that was introduced: the developer enabled this new driver by default. Linus Torvalds has always frowned upon random new drivers being enabled by default in the kernel configuration driver. [H]e still voiced his opinion over this driver's default "Y" build configuration, but did so in a more professional manner than he has done in the past:
We do *not* enable new random drivers by default. And we most *definitely* don't do it when they are odd-ball ones that most people have never heard of.
Yet the new "BigBen Interactive" driver that was added this merge window did exactly that.
Just don't do it.
Yes, yes, every developer always thinks that _their_ driver is so special and so magically important that it should be enabled by default. But no. When we have thousands of drivers, we don't randomly pick one new driver to be enabled by default just because some developer thinks it is special. It's not.... Please don't do things like this.
Phoronix also describes another "kernel oops" testing Torvalds' patience, in which Linus responded tactfully that "What makes me *very* unhappy about this is that if I'm right, I think it means that code was literally not tested at all by anybody who didn't have one of the entries in that list."
AmiMoJo quotes their report: Last Saturday he took issue with the HID pull request and its introduction of the BigBen game controller driver that was introduced: the developer enabled this new driver by default. Linus Torvalds has always frowned upon random new drivers being enabled by default in the kernel configuration driver. [H]e still voiced his opinion over this driver's default "Y" build configuration, but did so in a more professional manner than he has done in the past:
We do *not* enable new random drivers by default. And we most *definitely* don't do it when they are odd-ball ones that most people have never heard of.
Yet the new "BigBen Interactive" driver that was added this merge window did exactly that.
Just don't do it.
Yes, yes, every developer always thinks that _their_ driver is so special and so magically important that it should be enabled by default. But no. When we have thousands of drivers, we don't randomly pick one new driver to be enabled by default just because some developer thinks it is special. It's not.... Please don't do things like this.
Phoronix also describes another "kernel oops" testing Torvalds' patience, in which Linus responded tactfully that "What makes me *very* unhappy about this is that if I'm right, I think it means that code was literally not tested at all by anybody who didn't have one of the entries in that list."
That should be impossible with just a few written words, right?
SJW: Someone who has run out of real oppression, and has to fake it.
I miss the old Linus.
Compare 2010:
https://lkml.org/lkml/2010/5/20/218
This is just unbelievable SH*T: ...
First it says "only ask if EMBEDDED", and then it says "default to Y if
not embedded".
Why? Why the hell did somebody decide that everybody and their pet dog
should get that totally uninteresting driver, whether they want it or not?
I realize that every single developer thinks that their driver is the most
important thing in the universe, but come on! This kind of thing is
totally inappropriate, and to make matters worse, it looks like there are
a few commits that won't even compile because the whole file wasn't even
added until later.
And this piece of shit was made _mandatory_?
Get a grip, people. I'm not pulling idiotic crap like this. Some quality
control before you ask me to pull, for chissake!
2018:
We do *not* enable new random drivers by default. And we most *definitely* don't do it when they are odd-ball ones that most people have never heard of.
Yet the new "BigBen Interactive" driver that was added this merge window did exactly that.
Just don't do it.
Yes, yes, every developer always thinks that _their_ driver is so special and so magically important that it should be enabled by default. But no. When we have thousands of drivers, we don't randomly pick one new driver to be enabled by default just because some developer thinks it is special. It's not.... Please don't do things like this.
This is clearly developer behavior which Linus just HATES, but now he has to be polite in expressing his disdain for it.
I expect Linus to be committed to the looney bin in a matter of months.
If you want a healthy productive community, the correct way to handle repeated violations of policy is to document the policy and direct people to it when its violated.
If instead he said, you have violated our driver enablement policy, documented at link, then everyone one involved in the offending change making it in would have a much more pleasant time correcting their behavior and also have the opportunity to learn about such rules in advance easier.
In the software industry, it is standard practice to take repeat issues like this and document then in your best practices document along with examples and justifications. Its better for everyone involved (less work and stress for people like Linus, less being singled out and less feeling like they are being targeted by the contributors).
Personally I find that the canonical policy documentation is in Linus's head to be a bigger issue than his attitude. There is more to being fostering a positive developer community than not speaking in a rude way: you actually need to be inclusive/transparent when it comes to forming the policies, and in this case having a written best practices document everyone can read and discuss when they have disagreements rather than suffer a personal attack for an authority figure would make this a much better experience for most people.
At least that's my personal take coming from from the big company cooperate software engineering environment. I've dealt with this kind of feedback before, and it always feels like "my arbitrary opinion that you don't have access to says you should stop being wrong". I like it much better when a perceived mistake is instead address with the question of how we can help future people from making the mistake (ex: new documentation) or how I can help myself from making similar mistakes (ex: direct me to existing documentation). Its the difference of attitude between you messed up, vs how can we learn from this to improve the system so less people fall into the same trap you did.
They very well could be, at least in the future. Just imagine that anytime someone really wanted to say fuck, they just added some asterisks around the modified text instead. Eventually everyone figures it out to the point where asterisks are just read as someone cursing out you. Maybe it even ends up being a part of the language if it's popular enough over a long enough period of time. If you can't say "fuck" people will just find a new way to convey the same sentiment. Banning words does nothing to change the people or situations that gave rise to them in the first place. Eventually asterisks just become the new way of expressing that someone has fucked up.
/. enough times to look up what the fuck (sorry, I'm not really about the asterisks) it was supposed to be about. Maybe that meme dies like so many others probably until it gets censored and replaced with something else. I don't know when this started, but at some point, surrounding text in multiple set of parenthesis became an anti-Semitic remark, when prior to that it would have just been nonsense or a weird choice of formatting.
I think there's actually a relevant example of this online now where apparently surrounding text in multiple sets of parenthesis is supposed to be an indication that the thing in parenthesis is a Jewish plot or something like that. I've seen it on
> and not particularly professional
A crack-whore is a professional. All "professional" means is that you get paid to do work. "Amateur" is someone who does it for the love of it. I'd rather sleep with and amateur than a professional any day.
"Professional" is one of those weasel-words that gets used to control and manipulate others rather than having any real useful meaning (beyond the above). For me, as soon as someone uses the word "professional" I know they are a worthless piece of shit and I can simply ignore them as they are irrelevant to anything that actually matters.
Go be a whore (professional) and leave the work to the amateurs!
Oh fuck off. We do *not* enable new random drivers by default. And we most *definitely* don't do it when they are odd-ball ones that most people have never heard of.
Yet the new "BigBen Interactive" driver that was added this merge window did exactly that.
Just don't fucking do it.
Yes, yes, you always thinks that your driver is so special and so magically important that it should be enabled by default. But no. When we have thousands of drivers, we don't randomly pick one new driver to be enabled by default just because some developer thinks they are special. You're not. Don't fucking do things like this.