From: Jeff King <peff@peff.net>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: Denton Liu <liu.denton@gmail.com>,
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 16:52:27 -0400 [thread overview]
Message-ID: <20190924205226.GB20858@sigill.intra.peff.net> (raw)
In-Reply-To: <20190924200533.pfi7zjv73zklaahw@yadavpratyush.com>
On Wed, Sep 25, 2019 at 01:35:33AM +0530, Pratyush Yadav wrote:
> > As I said above, I couldn't find a public list of the people who were on
> > the project committee. Perhaps that's because my Googling skills are bad
> > but I feel uncomfortable knowing that *anyone* will be given judge, jury
> > and executioner power, let alone people whom I don't know anything
> > about.
>
> I agree with this. I would certainly like to know who the people who
> will judge these cases are.
See my other reply to Denton for details here.
> I want to add another question: what will the judgement process be like?
> Will it be an open discussion on this list, or will it be decided behind
> closed doors by the committee, and we just get to hear the results?
I think we'll have to approach this on a case by case basis to some
degree. If people are having conflict on the mailing list, I'd like to
see it resolved there, too. If somebody is sexually assaulted at the Git
Contributor Summit, that probably needs to be handled with more
discretion.
Keep in mind that a lot of this isn't changing the status quo. When we
had a problem on the mailing list in the past, it was discussed on the
list _and_ in private. And ultimately decisions came down to the
maintainer: am I going to start ignoring this person's patches, or will
I continue to encourage them to interact with the project even though
they're causing problems.
So I think a lot of this is really just writing down the current
practice.
> While there might be no plans regarding this as of now, I'd _really_
> like an open discussion regarding these issues that arise in the future,
> rather than it being decided behind closed doors with us regular old
> contributors getting no say in it. A closed discussion would be much
> more prone to power abuse, if any.
Yes, I don't like the idea of creating a pseudo-judicial system that has
none of the normal guarantees of rights (like say, facing your accuser
and seeing their evidence). At the same time, I don't want to re-create
a court system (badly). Especially given that most of our enforcement is
pretty "soft" in the first place; i.e., the most we can probably do is
stop interacting with a person, and maybe ask vger admins to block them
from using the list.
-Peff
next prev parent reply other threads:[~2019-09-24 20:52 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 [this message]
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
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=20190924205226.GB20858@sigill.intra.peff.net \
--to=peff@peff.net \
--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=liu.denton@gmail.com \
--cc=me@yadavpratyush.com \
--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).