From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: 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 23:37:28 +0000 [thread overview]
Message-ID: <20190924233728.6iueqaktlhhfwn7k@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20190924064454.GA30419@sigill.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
On 2019-09-24 at 06:44:54, 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
I wholeheartedly agree with this assessment.
> 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.
I've already mentioned that I think this is a good idea, and I
appreciate your thorough rationale in the commit message.
Acked-by: brian m. carlson <sandals@crustytoothpaste.net>
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-09-24 23:37 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
2019-09-24 23:37 ` brian m. carlson [this message]
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=20190924233728.6iueqaktlhhfwn7k@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.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=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).