ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] New CoC and Brendan Eich
Date: Thu, 04 Oct 2018 21:33:15 +0300	[thread overview]
Message-ID: <6108593.JtmfA2IdsK@avalon> (raw)
In-Reply-To: <CAKON4OxHUoVQ3zso=avoGE35MwWnkGaU13R_qPaw9zAqMVCDxQ@mail.gmail.com>

Hi Jon,

On Thursday, 4 October 2018 19:23:33 EEST jonsmirl@gmail.com wrote:
> I would highly recommend getting the new CoC reviewed and approved by
> some of the very smart lawyers that help out the Linux community.  I
> would also recommend discussing the Brendan Eich situation at Ksummit.
> A situation like this needs to be planned for since an improper
> response will make things much worse leading to legal challenges.
> 
> Some random articles to refresh everyone's memory...
> https://www.telegraph.co.uk/finance/newsbysector/mediatechnologyandtelecoms/
> digital-media/10743456/Mozilla-chief-Brendan-Eich-steps-down-over-gay-marria
> ge-row.html
> https://www.theguardian.com/commentisfree/2014/apr/07/brendan-eich-has-the-> right-to-fight-gay-rights-but-not-to-be-mozillas-ceo
> https://www.bbc.com/news/technology-26868536
> https://www.telegraph.co.uk/technology/technology-topics/10745283/Brendan-Ei
> ch-is-a-homophobe-Im-a-lesbian-and-neither-of-us-deserves-to-lose-our-jobs.h
> tml

We're facing a textbook case that has a probability of generating heated 
discussions no lower than 100%. I remember having a pretty strong opinion on 
the topic when it came under public scrutiny (and while I generally don't mind 
discussing it, I won't disclose that opinion here as that's entirely 
irrelevant). The more interesting part was that waiting for the debate to cool 
down gave me time to think, and realize that what is often perceived as a 
black-and-white situation most often turns out to be more complex than 
initially perceived.

One point that I would like to explore is thus how we can take the time needed 
to solve such matters when the mob is waiting outside of the courtroom with 
tar and feathers. I don't want to discuss here what our response to such a 
case should be, but the process that we should follow to come up with a 
response. It is of paramount importance in my opinion for the body tasked with 
handling those issues to follow a process that ensures it will be able to keep 
a cool head and have enough time available to think the response carefully.

Another point that I believe is important is the issue of representation. The 
code of conduct mentions both "project" and "community". While neither are 
defined, the term project is quite straightforward, but the term community not 
really so. The code of conduct gives a mandate to the TAB to handle 
enforcement in the name of the project (I don't want to focus here on whether 
the TAB is the right instance to handle those issues, this will likely be 
discusses separately and possibly be changed, I will just use TAB here to 
refer to the code of conduct enforcement body for simplicity), and I would 
argue that the mandate extends to representing the community as a whole. When 
the TAB will have to decide on a case that will generate a wide diversity of 
opinions, what kind of process can we put in place to ensure that all 
community members will feel represented (and thus heard) ? To put it 
differently, how can we make sure that the community members who don't fully 
agree with the final decision will agree to disagree and still feel part of 
the community ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2018-10-04 18:33 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 16:23 jonsmirl
2018-10-04 18:33 ` Laurent Pinchart [this message]
2018-10-04 19:05   ` jonsmirl
2018-10-04 19:21     ` Rodrigo Vivi
2018-10-04 19:53       ` jonsmirl
2018-10-05  7:21       ` Geert Uytterhoeven
2018-10-08 21:35       ` Mauro Carvalho Chehab
2018-10-08 23:20         ` Rodrigo Vivi
2018-10-09 10:07           ` Mauro Carvalho Chehab
2018-10-09 15:59             ` Rodrigo Vivi
2018-10-09 16:52             ` Chris Mason
2018-10-09 22:03               ` Dan Williams
2018-10-10  6:47                 ` Geert Uytterhoeven
2018-10-10 13:57                   ` Mauro Carvalho Chehab
2018-10-10 17:21                     ` Josh Triplett
2018-10-10 18:28                       ` Mauro Carvalho Chehab
2018-10-10 19:56                         ` Josh Triplett
2018-10-10 20:12                           ` Mauro Carvalho Chehab
2018-10-10 20:17                             ` Josh Triplett
2018-10-04 19:34     ` Laurent Pinchart
2018-10-04 20:39   ` Al Viro
2018-10-04 20:56     ` Jonathan Corbet
2018-10-04 21:27       ` Thomas Gleixner
2018-10-04 22:04         ` Jonathan Corbet
2018-10-05 16:03           ` Theodore Y. Ts'o
2018-10-04 22:05         ` Tim.Bird
2018-10-05  6:23           ` Christoph Hellwig
2018-10-05  7:12       ` Geert Uytterhoeven
2018-10-05  7:50         ` Josh Triplett
2018-10-05  9:20           ` Jani Nikula
2018-10-05  9:57             ` Laurent Pinchart
2018-10-05 10:45               ` Joe Perches
2018-10-05 10:55                 ` Laurent Pinchart
2018-10-05 12:59               ` Jani Nikula
2018-10-05 13:09                 ` Laurent Pinchart
2018-10-05 15:17                 ` James Bottomley
2018-10-05 18:28                   ` Josh Triplett
2018-10-05 18:39                     ` James Bottomley
2018-10-04 20:57     ` Josh Triplett
2018-10-05  7:16       ` Geert Uytterhoeven
2018-10-05  7:51         ` Josh Triplett
2018-10-05  8:00           ` Geert Uytterhoeven
2018-10-05  8:44             ` Josh Triplett
2018-10-05 15:26           ` James Bottomley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6108593.JtmfA2IdsK@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox