From: Felipe Contreras <felipe.contreras@gmail.com>
To: 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>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: [PATCH] CODE_OF_CONDUCT: expect tolerance, not respect
Date: Wed, 23 Dec 2020 00:17:18 -0600 [thread overview]
Message-ID: <20201223061718.102779-1-felipe.contreras@gmail.com> (raw)
A lot of people confuse respect with tolerance, but they are not the
same thing.
This was debated when Cambridge University decided to implement a
freedom of speech policy demanding respect, which caused a huge
backlash, not just within the university.
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.
In that sense respect is like belief; nobody can force you to believe
the Moon is made of cheese.
You can pretend to believe in something, and you can pretend to
respect something, but you really don't. Any policy that asks people to
pretend is not a good policy.
What should be asked for is tolerance.
Tolerance simply means allowing an idea to exist, and that's what the
Git project should ask from participants within the community.
We don't need to pretend we respect other viewpoints, we just need to
tolerate them.
[1] https://www.theguardian.com/world/2020/dec/09/cambridge-university-rejects-proposal-it-be-respectful-of-all-views
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
CODE_OF_CONDUCT.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index fc4645d5c0..3324d9f151 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -22,7 +22,7 @@ Examples of behavior that contributes to creating a positive environment
include:
* 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
--
2.30.0.rc1
next reply other threads:[~2020-12-23 6:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 6:17 Felipe Contreras [this message]
2020-12-23 14:46 ` [PATCH] CODE_OF_CONDUCT: expect tolerance, not respect Derrick Stolee
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=20201223061718.102779-1-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@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).