From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>,
Andreas Schwab <schwab@suse.de>,
Joseph Myers <joseph@codesourcery.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Florian Weimer <fweimer@redhat.com>, DJ Delorie <dj@redhat.com>,
"Ryan S. Arnold" <ryan.arnold@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Re: Rename "master" branch to "main" for glibc 2.35 release.
Date: Tue, 1 Feb 2022 01:45:59 +0530 [thread overview]
Message-ID: <efe3afd1-d9e8-da6f-2a9a-67aa97a100a6@gotplt.org> (raw)
In-Reply-To: <e3bc84a9-7516-6653-7ce4-82e5952db935@linaro.org>
On 31/01/2022 23:39, Adhemerval Zanella via Libc-alpha wrote:
> I must say that I am failing to see any technical advantage or improvement
> of doing this change.
>
There's no technical advantage because it is not a technical issue to
begin with. In fact, rejecting the suggestion saying that there's no
technical advantage sends the unsaid message that we don't care enough
to give this social issue any more serious thought than trying to glean
technical merit from it.
I personally have no lived experience about the master/slave
nomenclature since I'm not from the USA and I'm not
African/African-American. I don't think we have any regular African or
African-American contributors either who could share their experiences
about how (or if) the nomenclature affects them. We're a mostly white
community with smidges of Asian for flavour, albeit geographically very
diverse (perhaps our relative ignorance/indifference towards this
mostly-American origin movement is because of the latter) so I don't
think any of us can reasonably speak to this.
My personal impression is that mentorship/paid programs would do far
more good than renaming things, but it's just that, a third person
impression with no lived experience in that context. Besides, why not both?
This is a social issue, so maybe it makes more sense to look at the
social advantages and/or disadvantages of making (or not) the change and
not focus so much on technical reasons.
Siddhesh
next prev parent reply other threads:[~2022-01-31 20:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 22:32 Carlos O'Donell
2022-01-29 22:45 ` Phil Blundell
2022-01-29 23:33 ` DJ Delorie
2022-01-30 1:35 ` Mike Frysinger
2022-01-30 2:10 ` DJ Delorie
2022-01-30 3:45 ` Mike Frysinger
2022-01-30 2:35 ` Paul Eggert
2022-01-30 5:41 ` Siddhesh Poyarekar
2022-01-31 12:46 ` Florian Weimer
2022-01-31 13:41 ` Andreas Schwab
2022-01-31 14:55 ` Carlos O'Donell
2022-02-01 0:59 ` Dmitry V. Levin
2022-02-01 3:05 ` Carlos O'Donell
2022-01-31 12:50 ` Tulio Magno Quites Machado Filho
2022-01-31 16:19 ` Joseph Myers
2022-01-31 17:59 ` Dan Raymond
2022-01-31 18:04 ` Dan Raymond
2022-01-31 22:49 ` Carlos O'Donell
2022-01-31 23:04 ` Joseph Myers
2022-02-01 3:02 ` Carlos O'Donell
2022-01-31 18:09 ` Adhemerval Zanella
2022-01-31 18:14 ` H.J. Lu
2022-01-31 18:21 ` Adhemerval Zanella
2022-01-31 18:28 ` DJ Delorie
2022-02-01 3:08 ` Siddhesh Poyarekar
2022-02-01 3:44 ` DJ Delorie
2022-02-01 5:05 ` Siddhesh Poyarekar
2022-02-01 7:25 ` Carlos O'Donell
2022-01-31 20:15 ` Siddhesh Poyarekar [this message]
2022-01-31 21:24 ` Adhemerval Zanella
2022-02-01 2:51 ` Siddhesh Poyarekar
2022-02-01 9:49 ` Florian Weimer
2022-02-01 10:26 ` Siddhesh Poyarekar
2022-02-03 5:57 ` Carlos O'Donell
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=efe3afd1-d9e8-da6f-2a9a-67aa97a100a6@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=ryan.arnold@gmail.com \
--cc=schwab@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).