lkml.org 
[lkml]   [2018]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Code of Conduct: Let's revamp it.
Hi,

I'd like to clarify that I am replying here in my personal capacity,
and not on behalf of the TAB or anyone else.

On Thu, Sep 20, 2018 at 12:35 AM, Edward Cree <ec429@cantab.net> wrote:
> On 19/09/18 15:18, Jonathan Corbet wrote:
>> I'd like to address just this part, speaking only for myself.
>> The LF is not in the position of arbitrating anything here. The body
>> charged with that is the LF Technical Advisory Board, which is a
>> different thing.
>
> Thank you for clarifying that.
>
> Jon, you're a good person, and I trust you not to harass developers.
> I'm not expecting you, or gregkh, or hpa to launch a dastardly plot
> to boot an innocent developer off the project.

I would be very surprised if any of my peers on the TAB ever had those
intentions, and I know I would not have them myself.

> But there are too many ways this can go wrong, maybe not now or next
> week but in five or ten years, when maybe a different kind of person
> is on the TAB, or maybe external pressure is brought to bear on TAB
> members.

This is an important topic, and something that will need consideration.

One thing to keep in mind is that we all want what is best for Linux,
to make the best possible kernel. None of this has changed that.

I personally find it unlikely that relevant pressure could be applied
on TAB members; I don't find it a prestigious role such that it is
worth holding on to against my own values or best judgement.

> (Some people are speculating that pressure has already
> been brought to bear on Linus, although I'd like to stress that if
> he feels that changing the way he communicates is best for the
> project then I for one thoroughly respect that.)

We should let Linus speak for himself and his motivations when he's
back, if he wants to. He has shown to be *extremely* resilient to
outside pressure for the entire history of the project, and to
speculate over his motives now doesn't do any good.

> Or maybe some manipulative extrovert will manage to whip up a media
> storm about some developer's innocuous remarks, the court of public
> opinion will immediately convict, other developers will be caught
> in a preference falsification cascade as no-one wants to take the
> risk of defending them. Are you, and the other members of the TAB,
> strong enough to hold back the lynch mobs when you know the guy
> hasn't done anything wrong? Do you really want to take on the
> responsibility to do that, perhaps time and time again? And can
> you be sure that you won't fall for a misleading framing by some
> charismatic sociopath of a fight you missed the start of?

There is a lot of focus in several discussions right now on punishment
and what will be done to those who violate the code of conduct. I'm
much more interested in figuring out what we can do to help mediate in
case of disagreements such that all parties can get along and work
together. That's the end goal for me. It's what the last document
tried to encourage, but as the commit message says, it wasn't showing
to be an effective approach so a new one is worth trying out.

Another common counter argument is that the code of conduct is
imposing what's appropriate thoughts and opinions on everybody. I can
see how that kind of environment _could_ be implemented with the same
code of conduct as a base, but it doesn't have to be and I know I
would fight strongly against that. I much prefer all be free to have
their opinions, but at the same time be respectful of each other when
we communicate. There are extreme edge cases but they're theoretical
at this point.

Disagreements are fine to have, and in many cases they lead to better
solutions in the end. What's not OK to me is when they veer off of the
path of respectful and productive discussion.

> Given that possibility, I think it is important for the kernel
> community to continue to send a strong signal that divisive identity
> politics are not welcome here; and I think that to adopt a Code of
> Conduct that contains in its opening sentence a laundry-list of
> protected classes (and was written by a, shall we say, divisive
> figure with a history of identity politics advocacy) sends precisely
> the opposite signal.

There is a list in the first paragraph, but the preceding words say
that it should be a *harassment-free experience for everyone*. That
part of the paragraph is to me the most important part.

Also, it doesn't particularly matter to me personally who wrote the
text, as much as what is in it, and how we apply it. Just as I might
not agree with everything that FSF or Richard Stallman says or does
but still approve of the GPL as a license.

> Linux is too important to civilisation to allow it to be turned into
> just another battlefield for the American culture war; commit
> 8a104f8b5867 seems like an invitation to both armies to take up
> positions on our fertile farmland. The only rule that gives no
> comfort to discriminatory political abusers (on either side) is—
> ye shall judge by their code alone.

Your above argument that the Code of Conduct is problematic because of
who wrote it seems to contradict your statement that we shall judge by
code (or text) alone.

I don't know of anyone who is looking to make code less important. I
sure am not. To me, this is about how we treat each other when we
discuss said code and other things around it (such as how we run the
project).


Finally, I'd like to comment on your initial concern that you already
have to work hard on communication, and that this makes you fearful of
consequences if you fail to get it right. I'd like to say that you've
been doing a great job at it, well done. Also:
1) I searched for your address in the mailing lists archives I have
here, and from what I see, I have zero concerns with any of what I've
read.
2) Even if that's not the case, I'm of the strong opinion that we
should assume good intentions by default, and help out and mediate in
case something comes up.

When it comes to on-topic mailing list behavior, I can construct
extreme situations that I think should be addressed harder than
de-escalation and mediation from the start, but we've had very little
of that in our community so far. Often it gets bad over time or after
a series of back-and-forth, and if we can help de-escalate or get
people to cool off, that'd resolve a lot of it.


-Olof

\
 
 \ /
  Last update: 2018-09-20 03:17    [W:0.257 / U:0.048 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site