Task #93815
closed
Renaming of "master" branch into "main" branch
0%
Description
Hi together,
in the context of inclusive wording more and more projects rename master into main. I think we should consider this for typo3 as well.
Not sure if this is already somewhere in the backlog/planning.
Best regards
Eckard.
Updated by Martin Kutschker almost 3 years ago
Please don't. Without any "slave" around, "master" has many meanings that do not revolve the idea of slavery.
Updated by Benni Mack over 2 years ago
- Status changed from New to Closed
Please use https://decisions.typo3.org/ for deciding on this first. This for sure has more implications than code-wise in our main repository:
- Our release script
- Our subtree splitter script
- Documentation all over the place
- get.typo3.org
- Reconfiguration of gerrit.typo3.org
- All pending reviews need to be adapted to "main, 10.4" etc.
All of these changes are not related to our main repository source code, and need to be consolidated, communication and then taken action on.
One might discuss if you use "next" instead of "main" or "master". so I think this should be discussed first, and the ticket itself is just a todo then (I don't even think we'd need to change something in the source code, maybe some composer.json changes?).
Updated by Helmut Hummel over 2 years ago
- Subject changed from renaming of master branch into main branch to Renaming of "master" branch into "main" branch
Martin Kutschker wrote in #note-1:
Please don't. Without any "slave" around, "master" has many meanings that do not revolve the idea of slavery.
100% disagreement with this statement.
Eckard Gehrke wrote:
in the context of inclusive wording more and more projects rename master into main. I think we should consider this for typo3 as well.
Thanks for the question. I personally would also feel more comfortable with having this branch renamed, which I gladly point out in detail in a place where this can be discussed properly.
Updated by Helmut Hummel over 2 years ago
Eckard Gehrke wrote:
Not sure if this is already somewhere in the backlog/planning.
As Benni pointed out already, there currently is no planning in that regard.
Benni Mack wrote in #note-2:
Please use https://decisions.typo3.org/ for deciding on this first. This for sure has more implications than code-wise in our main repository:
- Our release script
- Our subtree splitter script
- Documentation all over the place
- get.typo3.org
- Reconfiguration of gerrit.typo3.org
- All pending reviews need to be adapted to "main, 10.4" etc.
All of these changes are not related to our main repository source code, and need to be consolidated, communication and then taken action on.
Thanks Benni for the rough overview. It helps already to understand, that it isn't just a drive-by change to make in a couple of minutes. I'd like to add two first steps to this list and that is:
- Discuss with and convince core contributors that this is a good thing to do
- Discuss with and convince the broader community that this is a good thing to do
I also agree that https://decisions.typo3.org/ is an appropriate place to do the second, but my feeling ist that we should reach agreement within the core contributors first, otherwise it will be really hard to implement it.
One might discuss if you use "next" instead of "main" or "master". so I think this should be discussed first, and the ticket itself is just a todo then (I don't even think we'd need to change something in the source code, maybe some composer.json changes?).
I was inclined to say that whether "next" or "main" will not matter, but I'm sure there is potential for discussing this as well.
But here I tend to say that a simple vote with multiple suggestions should be enough.
In any case, my personal take on this is, that the discussion alone is worth any effort, no matter the outcome.