git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: "René Scharfe" <l.s.r@web.de>,
	git@vger.kernel.org, git@sfconservancy.org,
	"Derrick Stolee" <stolee@gmail.com>,
	"Emily Shaffer" <emilyshaffer@google.com>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	garimasigit@gmail.com
Subject: Re: [PATCH] add a Code of Conduct document
Date: Wed, 25 Sep 2019 14:34:15 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1909251424380.15067@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20190924210918.GC20858@sigill.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]

Hi,

On Tue, 24 Sep 2019, Jeff King wrote:

> On Tue, Sep 24, 2019 at 10:14:55PM +0200, René Scharfe wrote:
>
> > > +* Trolling, insulting/derogatory comments, and personal or
> > > political attacks
> >
> > Hmm.  Trolling can be helpful, if done right.  I consider this to be
> > a good example: https://git-man-page-generator.lokaltog.net/.  Wrote
> > some texts that look like that..
>
> I suppose one man's joke is another man's troll. [...]

And we could now try to dive into that rabbit hole and discuss every
detail about it, but...

> [...]
>
> Again, I really think the point here is not to enumerate all
> possibilities. It's to set some general expectations, and to make it
> clear that we value the idea of having a genial atmosphere for
> communication that we have a document and a reporting mechanism.

This is a very important point. No CoC can be complete, ever, just like
Git will probably never be complete.

The proposed solution is to give power to a committee of trusted members
of the Git developer community. The key word here is _trust_. I don't
think there can be any doubt that Junio, Peff, Christian and Ævar have
earned the trust of the Git developer community.

For those two reasons, I am totally fine with leaving mostly
hypothetical scenarios a little vague. Because I trust that committee.

Ciao,
Dscho

  reply	other threads:[~2019-09-25 12:34 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
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 [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.1909251424380.15067@tvgsbejvaqbjf.bet \
    --to=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=l.s.r@web.de \
    --cc=peff@peff.net \
    --cc=stolee@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).