Earlier quoted context omitted.
Agreed, The author in summary states: > It [the rewrite] has 43% as many words, but loses none of the meaning. It's still forceful and unambiguous. Yet, I found the rewrite to be feeble and ambivalent. > If you were in the "I'm afraid that being nicer would hurt Linux" group, do you think that this email is worse? Yes. I wanted to add one additional question. Are there environments where ad hominem and disrespect are…
People have done science to answer your last question. In general the answer is no.
A Case Study in Not Being a Jerk in Open Source
21–30 of 55 posts
Re: A Case Study in Not Being a Jerk in Open Source
#22If Linus had written the reworded email the author is proposing here, this author wouldn't be writing this blog post, and we wouldn't be clicking it on HN and reading the contents of Linus' points. As to the actual detail of the author's proposed rewordings: > I'm not talking about the changes themselves - I can live with them. But the _rationale_ is pure and utter garbage, and dangerously so. becomes > These changes…
Re: A Case Study in Not Being a Jerk in Open Source
#23If Linus had written the reworded email the author is proposing here, this author wouldn't be writing this blog post, and we wouldn't be clicking it on HN and reading the contents of Linus' points. As to the actual detail of the author's proposed rewordings: > I'm not talking about the changes themselves - I can live with them. But the _rationale_ is pure and utter garbage, and dangerously so. becomes > These changes…
You'd really forget an email from the head of the project (the "CEO," to use another user's example on here) telling you you've messed up, just because the language was neutral?
I'm not sure I understand that. I don't think most people need yelling and raving in order to know something is important or understand what needs to get done.
Even so, I'm sure better versions exist. Do you have an idea of a polite-but-forceful rewrite of this email that'd be more effective?
Re: A Case Study in Not Being a Jerk in Open Source
#24If Linus had written the reworded email the author is proposing here, this author wouldn't be writing this blog post, and we wouldn't be clicking it on HN and reading the contents of Linus' points. As to the actual detail of the author's proposed rewordings: > I'm not talking about the changes themselves - I can live with them. But the _rationale_ is pure and utter garbage, and dangerously so. becomes > These changes…
I agree. The revised email is respectful and courteous, but it is also woefully forgetful. While you shouldn't do it all the time, there are times when you just really need to drive a point home
Re: A Case Study in Not Being a Jerk in Open Source
#25This "Linus is a jerk" meme is old and tired. The moral-superiority bullies are jerks too. Same as people who use their position to push their politics. Maybe we should all just be adults and focus on the work.
So it is Linus who is not being an adult.
Re: A Case Study in Not Being a Jerk in Open Source
#26This "Linus is a jerk" meme is old and tired. The moral-superiority bullies are jerks too. Same as people who use their position to push their politics. Maybe we should all just be adults and focus on the work.
Re: A Case Study in Not Being a Jerk in Open Source
#27This must be a cultural thing. There are plenty of people who happily interact like this daily. It is a personality. People talk and act in different ways, they are different people, I think it is reasonable for them to continue acting like themselves. I don't find the way Linus writes offensive in the slightest. To me it is mildly amusing while making a point. I don't want to have all communications in a forced poli…
Yes. Parts of the FOSS community have a culture that apologizes for jerky behavior.
>There are plenty of people who happily interact like this daily.
There are plenty of jerks, yes.
> I think it is reasonable for them to continue acting like themselves.
Being part of a team means accommodating your team members. We can argue what is a reasonable accommodation or what is not. But it's not too much to ask for Linus to stop typing in all caps, or accusing his team members of being morons.
> I don't find the way Linus writes offensive in the slightest. To me it is mildly amusing while making a point.
It's possible to be amusing and make a point without singling out a contributor for humiliation. Obviously, we have to be free to criticize other's work. But as the article shows, most of Linus's message isn't constructive criticism. It can be re-written to mean the same thing, yet preserve the dignity of the person he's criticizing.
We need people to contribute to open source projects. Being a jerk to others scares contributors away.
Re: A Case Study in Not Being a Jerk in Open Source
#28Earlier quoted context omitted.
I agree. The revised email is respectful and courteous, but it is also woefully forgetful. While you shouldn't do it all the time, there are times when you just really need to drive a point home
Why do you have to insult people on a personal level to drive points home?
Re: A Case Study in Not Being a Jerk in Open Source
#29If Linus had written the reworded email the author is proposing here, this author wouldn't be writing this blog post, and we wouldn't be clicking it on HN and reading the contents of Linus' points. As to the actual detail of the author's proposed rewordings: > I'm not talking about the changes themselves - I can live with them. But the _rationale_ is pure and utter garbage, and dangerously so. becomes > These changes…
I don’t know if that matters, but it strikes me as odd that people who seem to appreciate how this site works think that Linus is some exception because of just how mission critical he is. I also think it likely reflects the lack of soft skills some here have that they can’t imagine a better way being as or more effective, despite the living example of HN itself.
Re: A Case Study in Not Being a Jerk in Open Source
#30Linus seems like a jerk if you see him as an entitled engineer maintaining a popular OSS library. But if you instead see him as a CEO, responsible for every single part of the Linux kernel, running on one billion machines, his behavior becomes natural. Even warranted, since, often-times the people at the recieving end of his wrath are not making some whoops-daisy technical mistake; they are trying to exert power and…
Instead, I'll offer this. In my experience, great leadership is the skill of getting a group of people to take action on a cause without having/using authority over them. Instead, you seem to think leadership is about taking authority over people by being a jerk to them.
No one's saying that Linus shouldn't be a strong advocate for the kernel. This is entirely about his refusal to acknowledge or improve lousy communication skills that obfuscate his generally excellent technical arguments, and needlessly push away contributors who have actual self respect.