[VOTE] Switch 'master' to 'main' branch for repositories

[Rafał Miłecki]

On 27.02.2023 10:17, Rafał Miłecki wrote:
> On 27.02.2023 08:05, Felix Fietkau wrote:
>> More and more projects are switching their repositories to use the 'main' branch instead of the 'master' branch. This also includes many Linux upstream trees as well. Some trees are even removing their 'master' branches already.
>>
>> I think this is becoming more and more mainstream and expected of projects, so we should do the same.
>>
>> I would like to propose the following:
>>
>> 1. Change the git server side to automatically update the 'master' branch, whenever an update is pushed to 'main'.
>> It's important to have a long transition period in order to avoid breaking downstream users' workflows.
>>
>> 2. Change the git server side to refuse a push to 'master' if 'main' exists. This avoid accidental branch divergence
>>
>> 3. Developers simply change their git configs to always push to 'main'
> 
> Nack
> 
> I don't see why we should complicite stuff just to match some projects.
> Sounds nonsense.
> 
> 
>  > Once this change is well established, we can look into removing 'master', but we should definitely take our time with that.
> 
> Well, this actually sounds stupid.
> You want to add "main" branch to match some people expectations.
> You want to delete "master" branch breaking some people expectations.

I believe I missed some important discussion on this due to my absence
on the last meeting.

Could someone explain me what exactly is going on here?

Sure we can rename "master" to "main" today.
Then maybe "main" to "primary" tomorrow.
Why not "primary" to "major" later.

Is that worth it just because projects <foo>, <bar>, <qux> decided to
go with "main"? Is there some technical problem?