list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <>
To: Jeff King <>, Eric Wong <>
Cc: Junio C Hamano <>,,
	Johannes Schindelin <>
Subject: Re: Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks
Date: Thu, 17 Oct 2019 14:56:00 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi all,

On 11/10/2019 06:58, Jeff King wrote:
> I snipped your concerns with some of the language. I do agree with you
> that a lot of is open to interpretation. But I also think it's
> impossible to get it 100% airtight. My feeling was that it was a good
> idea to go with some existing, well-established text, even if it has
> some wiggle room. And then rely on the existing community and especially
> the people listed above to do that interpretation.
> So...
>> Just pointing out some concerns of mine.  No ack from me
>> (but it's not a NACK, either).  I'm pretty ambivalent...
> For me it is obviously an ack, but I wanted to make clear that I think
> your concerns (and those of others who spoke up, like René and Gábor)
> are certainly_valid_. I just think that adopting this CoC is, while not
> perfect, the least-bad option.
> I'd also say that we might consider living with it for a while (6
> months? a year?) and seeing if people have an interest in revising it
> after that point based on experience.
  I also didn't positively ack the CoC (code of conduct).

I'm not sure it addresses the broader _underlying_ issues that may need 
to be addressed that are behind the pressure for CoCs. I'd also 
commented [1] on the git-for-windows CoC partly because the CoC didn't 
positively address the need for tolerance.

These CoCs are essentially defensive, rather than forward looking. In 
essence they say:

We are a welcoming and inspiring community, open to anyone and 
everyone(all 2^16 variants).

We list various egregious behaviours that are unwanted and hence 

We list responses to such intolerable behaviour.

However we (in the CoC document) don't really address what we may need 
to do to extend the community to the broader many.

Part of the wider problem is we often don't appreciate our pre-existing 
organisational biases (e.g.[2, 3]) that we fit into within a community. 
For example the implicit gender bias toward independent sole author 
contributions[4], rather than the inclusiveness of co-authorship as a norm.

While following peff's "interpretation" document link [5], I did see, in 
the wider kernel document, that it does have a "Co-developed-by:" option 
[6] but then requires a secondary "Signed-off-by:", thus making those 
who co-author do extra work, which shouldn't be required.

Thus, while the CoC is good, for clarifying the egregious behaviour 
issues, it doesn't really address the wider 'Diversity and Equality' 
*expectations* within the community.


[2] "institutional racism"
[3] "institutional sexism" ... no Wikipedia article?

  reply	other threads:[~2019-10-17 13:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  3:38 What's cooking in git.git (Oct 2019, #02; Mon, 7) Junio C Hamano
2019-10-08 19:36 ` jk/code-of-conduct, was " Johannes Schindelin
2019-10-09  0:14   ` Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks Junio C Hamano
2019-10-09  0:22     ` Taylor Blau
2019-10-09  1:41     ` Emily Shaffer
2019-10-09  8:07       ` Johannes Schindelin
2019-10-09  1:48     ` Jonathan Nieder
2019-10-09 10:36     ` Christian Couder
2019-10-09 15:13     ` Phillip Wood
2019-10-09 18:29     ` Elijah Newren
2019-10-09 19:37       ` Junio C Hamano
2019-10-09 19:52     ` William Baker
2019-10-09 20:50     ` CB Bailey
2019-10-10  0:18     ` Eric Wong
2019-10-11  5:58       ` Jeff King
2019-10-17 13:56         ` Philip Oakley [this message]
2019-10-11  4:39     ` Junio C Hamano
2019-10-11  6:01       ` Jeff King
2019-10-09  1:39   ` jk/code-of-conduct, was Re: What's cooking in git.git (Oct 2019, #02; Mon, 7) SZEDER Gábor

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:

  List information:

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

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).