From: Daniel Stenberg <daniel@haxx.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Jeff King" <peff@peff.net>,
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 08:39:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1909250834220.4757@tvnag.unkk.fr> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1909241426580.15067@tvgsbejvaqbjf.bet>
On Tue, 24 Sep 2019, Johannes Schindelin wrote:
> A CoC can very easily create clarity in such circumstances. By stating
> explicitly the standards to which we promise to hold ourselves, as well as
> others. And it can even help those who think of themselves as decent to
> improve on that front.
As one of the lurking not-really-in-this-project persons around, I just want
to step out of the shadows for a sec and say:
I think this is totally the right move and I'm a strong +1 on the CoC as
suggested.
--
/ daniel.haxx.se
next prev parent reply other threads:[~2019-09-25 6: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 [this message]
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
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=alpine.DEB.2.20.1909250834220.4757@tvnag.unkk.fr \
--to=daniel@haxx.se \
--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 \
--cc=szeder.dev@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).