+1 Regardless of the members@ discussion, we should do this. Although perhaps this should be done as a formal vote.
I'm assuming this is something that can be relatively easily scripted, but if does require manual work, I'd be happy to help. On Sun, Jun 14, 2020 at 4:38 AM <[email protected]> wrote: > Hi all, > > It seems that the members@ discussion is moving in this direction now as > well... > > Best, > > David > > On Sat, 13 Jun 2020 at 09:57, <[email protected]> wrote: > > > Hi all, > > > > What would others think about renaming the 'master' branches to 'main' in > > Sling? > > > > I know that there is discussion going on at members@ where people think > > that 'master' on its own is not problematic, with suggestions to document > > this somewhere. This could be an alternative. > > However I personally think that it would be preferable to avoid > > any potential problematic language in our codebases. I think renaming the > > 'master' branch to the 'main' branch would solve that. > > > > I know Sling has a lot of git repositories, and if we decide to agree on > > this I would be happy to help progressing this. > > > > Kind regards, > > > > David Bosschaert > > >
