Re: Proposal: Replace all references to master/slave in GNOME modules
- From: Ask Hjorth Larsen <asklarsen gmail com>
- To: Matthias Klumpp <matthias tenstral net>
- Cc: Michael Catanzaro <mcatanzaro gnome org>, Desktop Devel <desktop-devel-list gnome org>
- Subject: Re: Proposal: Replace all references to master/slave in GNOME modules
- Date: Fri, 26 Apr 2019 20:33:45 +0200
Am Fr., 26. Apr. 2019 um 19:11 Uhr schrieb Matthias Klumpp
<matthias tenstral net>:
Am Fr., 26. Apr. 2019 um 18:12 Uhr schrieb <mcatanzaro gnome org>:
I'm a little surprised that nobody has yet mentioned the elephant in
the room. The definition of "git" is not very inclusive:
[ ...]
Please don't ready any of the statements above as an attempt to be
super-objective - I don't think that is possible, and I don't even
think objectivity can be the goal here, as the issue is so deeply tied
to individual opinions and experiences as well as cultural histories
and the languages one knows. That's why IMHO the "right" solution here
is actually ultimately what the community comes up with collectively,
and what feels right for us.
Sorry, I missed this thread and only now subscribed to the list.
I agree with most of what Matthias said, except to me this is an issue
of making technical changes for very wrong reasons. When it comes to
making technical changes, one should care about those who are affected
by the technical changes. This is why I care strongly enough to keep
writing these emails: It is simply a really bad idea and I will pay
the consequences. Plainly put: It is unfair and solves nothing.
0) It is problematic to work with hundreds of projects when they do
not use the same branch name (translators like myself), but this time
we want to make it consistent, so ...
1) Changing branch name for all the projects in GNOME will take time,
some projects might lack maintainers and so on. Many people are
involved. It won't become consistent easily, and meanwhile we only
lose time. I.e.: See point 0).
2) Tomorrow some other word will fall out of grace and we will again
have to take care not to offend anyone at any price. Word X is
offensive in culture Y, what are the odds that we don't have a lot of
potentially offensive stuff around? We gain /nothing/ by making this
kind of change.
3) This only happens because we are touching on US sensibilities.
Remember when it was brought up years ago that the foot logo is rude
in South-East Asia and that maybe we should change it since it might
be better for the GNOME brand there? Nothing was done. At least that
point had one argument in favour: It affects users. But now
US/Western/Anglocentric sensibilities are at stake, so we must change
even though it has no positive effect. I frankly think that this
hypersensitivity about slavery does more to offend than to include.
It readily conjures a problem where none was.
An important part of getting things to work in multicultural
environments is to not see offense where none was implied.
Best regards
Ask
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]