From: Thomas Gummerer <firstname.lastname@example.org> To: Jeff King <email@example.com> Cc: firstname.lastname@example.org, email@example.com, Derrick Stolee <firstname.lastname@example.org>, Emily Shaffer <email@example.com>, Jonathan Nieder <firstname.lastname@example.org>, Johannes Schindelin <Johannes.Schindelin@gmx.de>, Junio C Hamano <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH] add a Code of Conduct document Date: Tue, 24 Sep 2019 18:40:56 +0100 Message-ID: <20190924174056.GA55104@cat> (raw) In-Reply-To: <20190924064454.GA30419@sigill.intra.peff.net> On 09/24, Jeff King wrote: > We've never had a formally written Code of Conduct document. Though it > has been discussed off and on over the years, for the most part the > behavior on the mailing list has been good enough that nobody felt the > need to push one forward. > > However, even if there aren't specific problems now, it's a good idea to > have a document: > > - it puts everybody on the same page with respect to expectations. > This might avoid poor behavior, but also makes it easier to handle > it if it does happen. > > - it publicly advertises that good conduct is important to us and will > be enforced, which may make some people more comfortable with > joining our community > > - it may be a good time to cement our expectations when things are > quiet, since it gives everybody some distance rather than focusing > on a current contentious issue > > This patch adapts the Contributor Covenant Code of Conduct. As opposed > to writing our own from scratch, this uses common and well-accepted > language, and strikes a good balance between illustrating expectations > and avoiding a laundry list of behaviors. It's also the same document > used by the Git for Windows project. > > The text is taken mostly verbatim from: > > https://www.contributor-covenant.org/version/1/4/code-of-conduct.html > > I also stole a very nice introductory paragraph from the Git for Windows > version of the file. > > There are a few subtle points, though: > > - the document refers to "the project maintainers". For the code, we > generally only consider there to be one maintainer: Junio C Hamano. > But for dealing with community issues, it makes sense to involve > more people to spread the responsibility. I've listed the project > committee address of email@example.com as the contact point. > > - the document mentions banning from the community, both in the intro > paragraph and in "Our Responsibilities". The exact mechanism here is > left vague. I can imagine it might start with social enforcement > (not accepting patches, ignoring emails) and could escalate to > technical measures if necessary (asking vger admins to block an > address). It probably make sense _not_ to get too specific at this > point, and deal with specifics as they come up. > > Signed-off-by: Jeff King <firstname.lastname@example.org> I don't have much to add to this, the commit message spells out all the reasons why we should have this nicely and I wholeheartedly agree with introducing it, and choosing the Contributor Covenant as our template. So I'm adding my ACK to the others that have been coming in already. Thanks for submitting this!
next prev parent reply other threads:[~2019-09-24 17:41 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-24 6:44 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 [this message] 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=20190924174056.GA55104@cat \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
firstname.lastname@example.org list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ email@example.com public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git