From: Derrick Stolee <stolee@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>, git@vger.kernel.org
Cc: git@sfconservancy.org,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Jeff King" <peff@peff.net>,
"'Junio C Hamano '" <gitster@pobox.com>
Subject: Re: [PATCH] CODE_OF_CONDUCT: expect tolerance, not respect
Date: Wed, 23 Dec 2020 09:46:56 -0500 [thread overview]
Message-ID: <3d21cc06-415d-860b-7bd2-31047d68bc05@gmail.com> (raw)
In-Reply-To: <20201223061718.102779-1-felipe.contreras@gmail.com>
On 12/23/2020 1:17 AM, Felipe Contreras wrote:
> As many argued; respect cannot be manufactured at will. If you don't
> respect an idea (for example that the Earth is flat), then it doesn't
> matter how hard you try; you still will not respect it.
...
> * Using welcoming and inclusive language
> -* Being respectful of differing viewpoints and experiences
> +* Being tolerant of differing viewpoints and experiences
> * Gracefully accepting constructive criticism
> * Focusing on what is best for the community
> * Showing empathy towards other community members
As mentioned in 5cdf230 (add a Code of Conduct document, 2019-09-24):
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.
It is highly recommended to stick to the widely-used and carefully
crafted phrasing.
Specifically, "Being respectful" is different from "Have respect", which
negates your argument for changing this word. We can only enforce what
is evidenced by actual communication, not the internal lives of community
members.
I could just as easily argue that it is possible to be tolerant without
being respectful.
Thanks,
-Stolee
next prev parent reply other threads:[~2020-12-23 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 6:17 [PATCH] CODE_OF_CONDUCT: expect tolerance, not respect Felipe Contreras
2020-12-23 14:46 ` Derrick Stolee [this message]
2020-12-23 15:19 ` Felipe Contreras
2020-12-23 20:10 ` brian m. carlson
2020-12-23 20:24 ` Johannes Schindelin
2020-12-24 2:09 ` Felipe Contreras
2020-12-23 20:58 ` Junio C Hamano
2020-12-24 0:53 ` Ævar Arnfjörð Bjarmason
2020-12-24 3:14 ` Felipe Contreras
2020-12-27 15:07 ` Michal Suchánek
2020-12-27 17:06 ` Felipe Contreras
2020-12-27 15:45 ` Jason Pyeron
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d21cc06-415d-860b-7bd2-31047d68bc05@gmail.com \
--to=stolee@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).