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

[Yousong Zhou]

Hi,

I vote no on this.

One thing is that like others I see no technical gain in doing this.
They are doing a good job but for this cvs branch renaming thing I
think time can be better spent on other matters than purging existing
non-evil, no-bad-intentioned use of the word "master".

The other thing is that I am worried that this may be going too far
and the world getting too sensitive to such added rules to a point
that will hurt expression.

Regards,
                yousong

On Mon, 27 Feb 2023 at 15:06, Felix Fietkau <nbd at nbd.name> wrote:
>
> Hi all,
>
> 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'
>
> Once this change is well established, we can look into removing
> 'master', but we should definitely take our time with that.
>
> - Felix
>
> _______________________________________________
> openwrt-adm mailing list
> openwrt-adm at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-adm