From: "James Ramsay" <james@jramsay.com.au>
To: "Taylor Blau" <me@ttaylorr.com>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Bryan Turner" <bturner@atlassian.com>,
"Daniel Gruesso" <dgruesso@gitlab.com>
Subject: Re: Consensus on a new default branch name
Date: Tue, 16 Jun 2020 10:50:33 +1000 [thread overview]
Message-ID: <41438A0F-50E4-4E58-A3A7-3DAAECB5576B@jramsay.com.au> (raw)
In-Reply-To: <20200615205722.GG71506@syl.local>
On 16 Jun 2020, at 6:57, Taylor Blau wrote:
> Concurrently with this, GitHub, GitLab [3], and Bitbucket are working
> together
> in order to make a similar change across our respective products.
> Because of
> this, we are met with a bit of a challenge: we would like to make
> these changes
> before the next version(s) (and so need to settle on a new default
> branch name),
> but we also want to avoid a situation where the community is fractured
> (eg.,
> GitHub uses 'main', Git uses 'default', etc).
Avoiding inconsistency is definitely front of mind for me.
> My interpretation thus far is that 'main' is the planned replacement
> for
> 'master'. Consensus seems to have formed around this name [5], but if
> that's
> incorrect--or there are yet-unvoiced opinions that you would like to
> share--now
> is the time to discuss further.
Based on informal surveys internally, and polling on
https://gitlab.com/gitlab-org/gitlab/-/issues/221164, ‘main’ seems
to be the preferred option. Using GitLab’s MECEFU (Mutually Exclusive,
Collectively Exhaustive, Few Words, Ubiquitous Language) [1] approach to
naming I think ‘main’ ticks all the boxes. None of the other
proposals seem as clear.
I think Elijah’s points in other messages about the problems of
‘default’ are particularly helpful. I would prefer to avoid that
name.
Thanks,
James
[1]: https://about.gitlab.com/handbook/communication/#mecefu-terms
next prev parent reply other threads:[~2020-06-16 0:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:57 Consensus on a new default branch name Taylor Blau
2020-06-15 21:10 ` Santiago Torres Arias
2020-06-15 21:21 ` Taylor Blau
2020-06-16 14:31 ` Jeff King
2020-06-16 14:52 ` Oleg
2020-06-16 16:00 ` Jeff King
2020-06-16 17:11 ` Oleg
2020-06-16 17:32 ` Konstantin Ryabitsev
2020-06-16 18:54 ` Oleg
2020-06-16 22:18 ` Jeff King
2020-06-16 16:10 ` Konstantin Ryabitsev
2020-06-16 16:13 ` Santiago Torres Arias
2020-06-16 16:48 ` Jeff King
2020-06-16 16:14 ` Jason Pyeron
2020-06-16 16:47 ` Jeff King
2020-06-16 17:44 ` Steve Litt
2020-06-16 19:00 ` Oleg
2020-06-17 18:06 ` Michal Suchánek
2020-07-01 17:31 ` Michal Suchánek
2020-07-01 21:57 ` Jeff King
2020-07-02 12:21 ` Whinis
2020-07-02 21:15 ` Philip Oakley
2020-07-02 21:59 ` Whinis
2020-07-02 22:47 ` Philip Oakley
2020-07-02 23:08 ` Whinis
2020-07-01 22:25 ` Jonathan Nieder
2020-06-15 22:38 ` Elijah Newren
2020-06-16 14:32 ` Jeff King
2020-06-17 20:13 ` Junio C Hamano
2020-06-15 23:24 ` brian m. carlson
2020-06-16 0:50 ` James Ramsay [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-16 1:58 Nomen Nescio
2020-06-16 2:22 ` Jonathan Nieder
2020-06-16 2:31 ` Taylor Blau
2020-06-16 14:38 ` Jeff King
2020-06-17 0:01 Anonymous Remailer (austria)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41438A0F-50E4-4E58-A3A7-3DAAECB5576B@jramsay.com.au \
--to=james@jramsay.com.au \
--cc=bturner@atlassian.com \
--cc=dgruesso@gitlab.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).