git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: CB Bailey <cb@hashpling.org>
To: Jeff King <peff@peff.net>, Emily Shaffer <emilyshaffer@google.com>
Cc: Denton Liu <liu.denton@gmail.com>, Git List <git@vger.kernel.org>,
	git@sfconservancy.org, Derrick Stolee <stolee@gmail.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>,
	garimasigit@gmail.com
Subject: Re: [PATCH] CODE_OF_CONDUCT: mention individual project-leader emails
Date: Fri, 27 Sep 2019 19:58:26 +0100	[thread overview]
Message-ID: <442a1736-d935-6033-c59a-e88c1ac179e9@hashpling.org> (raw)
In-Reply-To: <20190926072046.GB20653@sigill.intra.peff.net>

On 26/09/2019 08:20, Jeff King wrote:
> On Tue, Sep 24, 2019 at 04:52:56PM -0700, Emily Shaffer wrote:
>> I helped my other FOSS project to adopt a Code of Conduct earlier in
>> the year (https://github.com/openbmc/docs/blob/master/code-of-conduct.md)
>> and we got around this by asking for volunteers from the technical
>> steering committee to agree to have their contact info listed on the
>> escalation path; at the end of the escalation path we also listed
>> someone external to the project (which we were able to do because we
>> had been adopted by the Linux Foundation, and they have someone for
>> that).
> 
> Yeah, I think this is sort of the same thing except that I
> pre-volunteered the whole project committee. ;)
> 
> We could have a separate list of contacts for the code of conduct, but
> it seems simplest to just use the existing group that we already have,
> unless there's a compelling reason not to.

I, too, wondered if it might be more appropriate to have the list of
names and email addresses separated from the repository and just linked
from the CoC. Perhaps someone would need to expunge themselves from the
list permanently, or perhaps we'd want to protect against a hypothetical
person in a position of control changing the list to their trusted
cronies. I cannot think of a realistic scenario or practical setup which
would actually guarantee any such benefits and this solution is simple
and practical.

Overall for this proposed CoC patch: ACK

CB

  parent reply	other threads:[~2019-09-27 18:58 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 [this message]
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=442a1736-d935-6033-c59a-e88c1ac179e9@hashpling.org \
    --to=cb@hashpling.org \
    --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=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).