From: Phillip Wood <phillip.wood123@gmail.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>, "Jeff King" <peff@peff.net>
Cc: git@vger.kernel.org, git@sfconservancy.org,
Derrick Stolee <stolee@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>,
garimasigit@gmail.com
Subject: Re: [PATCH] add a Code of Conduct document
Date: Tue, 24 Sep 2019 15:40:39 +0100 [thread overview]
Message-ID: <9e65e95c-4a8d-c904-d8e9-bdd494f41ce0@gmail.com> (raw)
In-Reply-To: <20190924090152.GA7209@szeder.dev>
Hi Gábor
On 24/09/2019 10:01, SZEDER Gábor wrote:
> On Tue, Sep 24, 2019 at 02:44:54AM -0400, Jeff King wrote:
>> [...]
>>
>> After some poking around at various CoC options, this one seemed like
>> the best fit to me. But I'm open to suggestions or more discussion. It
>> seems to me that the important piece is having _some_ CoC, and picking
>> something standard-ish seems a safe bet.
>
> We are decent people, and know how to behave properly and treat each
> other with respect. It is my fundamental assumption that all future
> contributors are decent and respectful human beings as well.
History suggests that almost all will be decent but there will be one or
two who aren't and cause trouble.
> A CoC
> like this, which is "explicit about the behavior we want to model"
> (quoting the original discussion starter) inherently insinuates that
> we aren't decent, and can't behave without being told how to do so.
> Frankly, I find this borderline insulting to me, to my parents, to all
> fellow contributors, and to future contributors as well.
I don't find it insulting, to me it just sets out that the project
welcomes contributors who behave decently.
> There are locations, nationalities and cultures, where the avarage
> wide-spread CoCs, like Contributor Covenant and its derivatives, are
> perceived as (paraphrasing) too "American", politically overcorrect,
> corporate BS, etc., which are forced upon open-source projects.
> Consequently, such CoCs are often found rather discouraging, and
> announcements about their adoption in open-source projects generally
> get negative reaction.
>
> Less is more. Much-much more. A concise CoC that treats its readers
> as responsible, well-behaved human beings is met with much approval.
I was pleasantly surprised at how short the proposed CoC is, I don't
think it's too long at all. It only takes a couple of minutes to read
and is quite clear.
Best Wishes
Phillip
> Take, for example, the TrueOS Rules of Conduct, which in just a few
> short sentences covers everything that's worth covering:
>
> https://www.trueos.org/rulesofconduct/
>
> If diversity and inclusion of other cultures is indeed a priority,
> then we should carefully consider that some potential contributors
> will rather choose not to contribute because of a CoC like this.
>
>
>> If people are on board with this direction, it might be fun to pick up a
>> bunch of "Acked-by" trailers from people in the community who agree with
>> it. It might give it more weight if many members have publicly endorsed
>> it.
>
> Because of the above I'm leaning towards NACK.
>
next prev parent reply other threads:[~2019-09-24 14:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 6:44 [PATCH] add a Code of Conduct document Jeff King
2019-09-24 9:01 ` SZEDER Gábor
2019-09-24 13:20 ` Johannes Schindelin
2019-09-24 15:50 ` Jeff King
2019-09-25 6:39 ` Daniel Stenberg
2019-09-24 14:40 ` Phillip Wood [this message]
2019-09-24 12:13 ` Derrick Stolee
2019-09-24 15:51 ` Jeff King
2019-09-24 14:13 ` Phillip Wood
2019-09-24 16:53 ` Garima Singh
2019-09-24 16:56 ` Deb Nicholson
2019-09-24 17:12 ` Denton Liu
2019-09-24 20:05 ` Pratyush Yadav
2019-09-24 20:10 ` Doug Maxey
2019-09-24 20:52 ` Jeff King
2019-09-24 20:46 ` Jeff King
2019-09-24 23:52 ` Emily Shaffer
2019-09-26 7:20 ` [PATCH] CODE_OF_CONDUCT: mention individual project-leader emails Jeff King
2019-09-26 12:16 ` Derrick Stolee
2019-09-26 21:37 ` Emily Shaffer
2019-09-27 18:58 ` CB Bailey
2019-09-24 17:23 ` [PATCH] add a Code of Conduct document Jonathan Tan
2019-09-24 17:40 ` Thomas Gummerer
2019-09-24 20:14 ` René Scharfe
2019-09-24 21:09 ` Jeff King
2019-09-25 12:34 ` Johannes Schindelin
2019-09-24 23:37 ` brian m. carlson
2019-09-26 17:42 ` Elijah Newren
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=9e65e95c-4a8d-c904-d8e9-bdd494f41ce0@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=garimasigit@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=phillip.wood@dunelm.org.uk \
--cc=stolee@gmail.com \
--cc=szeder.dev@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).