10 Jun
2025
10 Jun
'25
4:15 a.m.
Hello dear XSF Members,
I see that we are still using "master" as the name of the main branch on Git
repositories (here, for instance: https://github.com/xsf/xeps ).
You are probably all aware that the use of this term has raised controversy in
recent years, as it can be perceived as a reference to slavery (see https://
en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy for
instance).
To avoid this unwanted reference and ensure the XSF is welcoming to everyone,
I propose that we change these branch names to "main," as many notable
projects have done (such as Python, the Linux Kernel, or GitHub).
I'm not sure whether this matter should be discussed in the Board or Council
(as it is a technical issue), but it would be good to add it to the agenda.
Thank you!
Goffi
10 Jun
10 Jun
4:34 a.m.
Thanks Goffi,
I would second this. Apart from the non-technical motivation: the XSF's
repos are one of the only ones that I still use that use 'master' rather
than 'main'. Where my muscle memory previously disliked 'main', it now
dislikes 'master'.
We would be far from the first to apply such a change. Tooling has matured
well over the years to make the change pretty easy. I hope that this helps
to take away most concerns that are of a technical nature.
Kind regards,
Guus
On Tue, Jun 10, 2025 at 12:16 PM Goffi <goffi(a)goffi.org> wrote:
Hello dear XSF Members,
I see that we are still using "master" as the name of the main branch on
Git
repositories (here, for instance: https://github.com/xsf/xeps ).
You are probably all aware that the use of this term has raised
controversy in
recent years, as it can be perceived as a reference to slavery (see
https://
en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy for
instance).
To avoid this unwanted reference and ensure the XSF is welcoming to
everyone,
I propose that we change these branch names to "main," as many notable
projects have done (such as Python, the Linux Kernel, or GitHub).
I'm not sure whether this matter should be discussed in the Board or
Council
(as it is a technical issue), but it would be good to add it to the agenda.
Thank you!
Goffi
4:42 a.m.
I agree with Guus and was about to comment on similar lines.
I would second this. Apart from the non-technical
motivation: the
XSF's repos are one of the only ones that I still use that use
'master' rather than 'main'. Where my muscle memory previously
disliked 'main', it now dislikes 'master'.
My muscle memory, too, has come to expect 'main', and when I see
'master' my first (unfounded) impression is that this is an old repo or
some king of legacy project.
We would be far from the first to apply such a change.
Tooling has
matured well over the years to make the change pretty easy. I hope
that this helps to take away most concerns that are of a technical nature.
Adding
to this: there are many web pages explaining specifically how to
change the "master" to "main", including this one that I found from a
quick web search. It seems simple enough:
https://www.hanselman.com/blog/easily-rename-your-git-default-branch-from-m…
You are probably all aware that the use of this term has raised
controversy in
recent years, as it can be perceived as a reference to slavery
(see https://
en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy
<http://en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy>
for
instance).
I wasn't aware of that controversy. But if those connotations are indeed
there I'd be happy to see the name changed, even on non-technical grounds :)
Best,
Badri
7:50 a.m.
Hello,
one question: If agreed, who would volunteer to do the work (without breaking anything)?
Cheers,
Eddie
Jun 10, 2025 12:43:46 PM Badri Sunderarajan <badrihippo(a)disroot.org>rg>:
I agree with Guus and was about to comment on similar
lines.
I would second this. Apart from the non-technical
motivation: the XSF's repos are one of the only ones that I still use that use
'master' rather than 'main'. Where my muscle memory previously disliked
'main', it now dislikes 'master'.
My muscle memory, too, has come to expect 'main', and when I see 'master'
my first (unfounded) impression is that this is an old repo or some king of legacy
project.
We would be far from the first to apply such a
change. Tooling has matured well over the years to make the change pretty easy. I hope
that this helps to take away most concerns that are of a technical nature.
Adding
to this: there are many web pages explaining specifically how to change the
"master" to "main", including this one that I found from a quick web
search. It seems simple enough:
https://www.hanselman.com/blog/easily-rename-your-git-default-branch-from-m…
You are probably all aware that the use of this term has raised
controversy in
recent years, as it can be perceived as a reference to slavery
(see https://
en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy
<http://en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy>
for
instance).
I wasn't aware of that controversy. But if those connotations are indeed
there I'd be happy to see the name changed, even on non-technical grounds :)
Best,
Badri
10:19 a.m.
On 10/06/25 7:20 pm, E.M. wrote:
Hello,
one question: If agreed, who would volunteer to do the work (without breaking anything)?
I don't mind doing it, but one concern is I'm new to how things are set
up, so I may not know what to look out for and how to avoid breaking
things (:
I'd be happy to help out where I can (maybe with some overseeing from
the Infrastructure team?)
My main concern is if there are any automated tools which pull the git
repos and expect to see things at a specific branch named 'master'. And
everyone who's cloned anything would also have to update their workflows
accordingly, of course.
Best,
Badri
11 Jun
11 Jun
3:08 a.m.
Le mardi 10 juin 2025, 15:50:21 heure d’été d’Europe centrale E.M. a écrit :
Hello,
one question: If agreed, who would volunteer to do the work (without
breaking
anything)?
Cheers,
Eddie
Hi,
Someone with access to the Git repository needs to handle this. The Git-side
process should be straightforward. If a script is relying on the branch name
and there’s an error, it’s simple to fix by simply updating the branch name.
While we can’t guarantee that nothing will break, any issues that arise should
be quick to resolve.
Best,
Goffi
10 Jun
10 Jun
3:04 p.m.
While I don't think that this use of master (as opposed to master/slave)
derives from the same usage, it's clear that some people do, and it's a
small and easy change to make. I agree we should do it.
The different repositories are under the purview of different teams, I
think - the website is probably Board, the XEP repository is Editor, for
instance. Happy to propose a policy from Board to push these all through
though.
On Tue, 10 Jun 2025 at 11:16, Goffi <goffi(a)goffi.org> wrote:
Hello dear XSF Members,
I see that we are still using "master" as the name of the main branch on
Git
repositories (here, for instance: https://github.com/xsf/xeps ).
You are probably all aware that the use of this term has raised
controversy in
recent years, as it can be perceived as a reference to slavery (see
https://
en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy for
instance).
To avoid this unwanted reference and ensure the XSF is welcoming to
everyone,
I propose that we change these branch names to "main," as many notable
projects have done (such as Python, the Linux Kernel, or GitHub).
I'm not sure whether this matter should be discussed in the Board or
Council
(as it is a technical issue), but it would be good to add it to the agenda.
Thank you!
Goffi
11 Jun
11 Jun
3:15 a.m.
Hi,
Le mardi 10 juin 2025, 23:04:49 heure d’été d’Europe centrale Dave Cridland a
écrit :
While I don't think that this use of master (as
opposed to master/slave)
derives from the same usage, it's clear that some people do, and it's a
small and easy change to make. I agree we should do it.
The different repositories are under the purview of different teams, I
think - the website is probably Board, the XEP repository is Editor, for
instance. Happy to propose a policy from Board to push these all through
though.
Yes please.
I can ask Daniel to put this on next meeting agenda for the `xeps`,
`registrar`, `schemas`, `xep-attic` and `rfcs` repositories (which other repos
would be Council territory?).
Best,
Goffi
12
days inactive
13
days old
7 comments
5 participants
participants (5)
-
Badri Sunderarajan -
Dave Cridland -
E.M. -
Goffi -
Guus der Kinderen