All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Senol Yazici <sypsilon@googlemail.com>,
	Junio C Hamano <gitster@pobox.com>,
	"Randall S. Becker" <rsbecker@nexbridge.com>,
	git@vger.kernel.org, jpyeron@pdinc.us
Subject: Re: [RFE] Demilitarize Documentation (was RE: Delivery Status Notification (Failure))
Date: Tue, 19 Feb 2019 15:47:08 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1902191540220.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20190219103906.3fc4c231@naga.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

Hi Michal,

On Tue, 19 Feb 2019, Michal Suchánek wrote:

> On Tue, 19 Feb 2019 09:02:43 +0100
> Senol Yazici <sypsilon@googlemail.com> wrote:
> 
> > Suggestion for substitution: Assistant or assistant integrator.
> 
> So now the terms sound a lot like a corporate lingo. Is it now turn for
> enthusiasts and entrepreneurs to feel excluded because git is meant
> only for corporations, and for people who had bad experience as
> corporate employees to feel offended?

The concern that was raised is a valid one. Words can do real harm, and we
should try not to keep perpetrating that same harm. We still have language
in our very README that puts off some people, for no good reason
whatsoever.

I find your comments quite offensive, as they seem to all try to downplay
the importance of words, when all you could say is that *you* have the
insane luck of being in a time and place where *you personally* are not
affected. But to belittle others who do not share that privilege is quite
out of line.

So let's give voice to those who have kind words, and rest our combative
language.

In other words, I welcome Senol's contribution, and hope that it will
cumulate in a Pull Request that fixes the website.

Ciao,
Johannes

  reply	other threads:[~2019-02-19 14:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 16:51 [RFE] Demilitarize Documentation (was RE: Delivery Status Notification (Failure)) Randall S. Becker
2019-02-18 17:26 ` Michal Suchánek
2019-02-18 18:39 ` Junio C Hamano
2019-02-19  8:02   ` Senol Yazici
2019-02-19  9:39     ` Michal Suchánek
2019-02-19 14:47       ` Johannes Schindelin [this message]
2019-02-19 16:28         ` Michal Suchánek
2019-02-19 10:01     ` SZEDER Gábor
2019-02-19 11:00       ` Senol Yazici
2019-02-19 14:58       ` Johannes Schindelin
2019-02-19 16:20         ` Michal Suchánek
2019-02-20 19:54           ` Johannes Schindelin
2019-02-19 20:16         ` Philip Oakley
2019-02-20 11:17         ` SZEDER Gábor
2019-02-19 11:19     ` Ævar Arnfjörð Bjarmason
2019-02-19 13:33       ` Michal Suchánek
2019-02-19 13:52       ` Christian Couder
2019-02-19 13:58         ` Michal Suchánek

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=nycvar.QRO.7.76.6.1902191540220.41@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jpyeron@pdinc.us \
    --cc=msuchanek@suse.de \
    --cc=rsbecker@nexbridge.com \
    --cc=sypsilon@googlemail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.