lkml.org 
[lkml]   [2013]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Ksummit-2013-discuss] [ATTEND] How to act on LKML (was: [ 00/19] 3.10.1-stable review)
On Tue, Jul 16, 2013 at 03:43:57PM -0700, Sarah Sharp wrote:
> I don't think we disagree on this, Ted. I've stated that I view
> personal attacks and insults negatively, and I don't see an issue with
> pointing out that code is bad. I think you're agreeing with me on this.

Perhaps I misundrestood you, then; when you replied to Olivier's
message, which used as his example "your code is crap", and "Let's
leverage my fifth grade nephew's capabilities to assist you in fixing
the code", it seemed to me that you called one a "personal attack",
and the other an "indirect personal insults".

If we're trying to say that "words matter", then it would be useful if
we are careful in what we describe as "a personal atack", and what
gets described as "abuse".

For example, when you brought up the example of Linus yelling at
Mauro, most of what I saw was Linus "yelling" (electronically) about
his behaviour being unacceptable. I saw mostly, "your behaviour is
idiotic", not "you are an idiot". Which perhaps is a finer gradation
than the difference between "your code is crap" and "you are crap".
Still, while I might call Linus's words to Mauro many things, "a
personal attack" wouldn't have been one of those words. Emphatic?
Yes. Yelling? Yes. Something I wouldn't do? Probably. But "A
personal attack"? I'm not so sure.

And then when you start reading comments from folks forua suc as G+
and Hacker News calling Linus "a dick" or "a douchebag", the irony is
quite palpable....

> > Keep in mind that there are some cultures where even pointing out a
> > technical flaw in code might considered bringing deep shame on the
> > engineer and their company. So how sensitive people are to criticism
> > during an electronic exchange is always going to be highly culutrally
> > and personally variable.
>
> Yes, that's true. Some kernel developers are better at moderating their
> comments and tone towards individuals who are "sensitive".

... and actually, I think it's actually quite difficult to find cases
where Linus has used a very harsh tone towards someone who would be
"sensitive". The argument which I've more commonly heard is one of
"collatoral damage". That is, that people other than the transgressor
of the bad behaviour see Linus's messages, and (a) don't realize that
the vast majority of his e-mails are not that harsh, and (b) assume
that Linus would use that language on them.

And certainly that is a downside of sending messages of chastisement
publically rather than privately. I doubt that neither Linus nor you
would disagee that there is a downside tradeoff. On the other hand,
if such messages are sent priviately, they are much less useful as far
as establishing community norms around technical excellence,
especially in regards to "no regressions" and "don't break userspace".
I suspect that you and he come down on different sides of the
question, "is it worth the tradeoff".

The other question where I think you and Linus differ is the belief
whether polite messages of the form, "it's really rude to break the
kernel ABI, I would rather prefer if you wouldn't do that" are as
effective at establishing community norms, compared with his style of
e-mail messagtes, and whether the priority in establishing community
norms around technical excellence compares with the priority around
community norms around "civility".

(And of course, what is considered "civil", and what is considered a
"personal attack", and what isn't.)

Hopefully this helps to clarify the discussion. I'm trying rather
purposely not take one side or another, but instead trying to
articulate what I think I've been hearing people say (over, and over,
and over again, on this very long mail thread).

Regards,

- Ted


\
 
 \ /
  Last update: 2013-07-17 02:21    [W:0.194 / U:1.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site