git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Taylor Blau <me@ttaylorr.com>,
	git@vger.kernel.org, James Ramsay <james@jramsay.com.au>,
	Bryan Turner <bturner@atlassian.com>
Subject: Re: Consensus on a new default branch name
Date: Wed, 1 Jul 2020 17:57:44 -0400	[thread overview]
Message-ID: <20200701215744.GA952178@coredump.intra.peff.net> (raw)
In-Reply-To: <20200701173108.GD21462@kitsune.suse.cz>

On Wed, Jul 01, 2020 at 07:31:08PM +0200, Michal Suchánek wrote:

> > > > > 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.
> > > 
> > > My opinion is that "main" is the best suggestion I've heard.
> > 
> > See also
> > https://lore.kernel.org/git/20200616210701.22924-1-zeevriend@gmail.com/
> 
> So you completely ignore this input.

I didn't ignore it. I just didn't have anything useful to add after
reading your email.

If there's a potential problem with "main", I think it's worth
considering. But I have a very difficult time figuring out how to
consider all of the inputs. Personally, I don't find "main" to be a
problematic word. It has no other connotations in my personal
experience. But then the same is true of "master" as well.

Anybody in a similar position who is working on the project and might
need to form an opinion about which default word to use has to rely on
input from others. The email linked above is one data point. There are
other data points arguing that "master" is bad.

In an ideal world, we'd have a name that has no data points at all
arguing against it. But I'm not sure how feasible it is to accommodate
everybody. There seem to be enough data points arguing against "master"
that I can believe there's a non-trivial number of people who would like
the default changed to something else[1]. I had wondered if other people
might speak up against "main", but I have not seen anyone do so (neither
here, nor in other forums where the name "main" has been discussed).
That doesn't invalidate the opinion of the author above. But if we have
to choose something from among an imperfect set of options, then that
may involve picking the least-bad name.

I am open to the argument that the very people the author suggests might
be bothered by "main" might also not be well represented on this list or
in other forums discussing the change. It would be helpful if any
proponents of that argument could try to gather some evidence.

> That kind of gives confirmation to the naysayers that point out this is
> not really about inclusivity but about US-internal politics.
> 
> If that is so be more honest and clearly say that by being based in the
> US you must give way to certain activists or be potentailly subject to
> terrorism from the same or more radical colleagues of the activists that
> request the change.

I'm not sure what constructive action you're asking for here. The link
to the email above suggests that you might be arguing for a different
alternative besides "main". If so, please suggest it (or if you did
elsewhere already and I missed it: sorry, please repeat it).

If your point is to argue "you care about master but not about main,
therefore you're a hypocrite and we should change nothing". Then one,
I do not agree with that characterization, and two, I don't think that's
a very helpful addition to the conversation.

If you meant something else, please help me figure out what it is.

-Peff

[1] I'm also open to the argument that the number of data points arguing
    against "master" are inflated by well-meaning people who claim to
    speak on behalf of others. But it seems very hard to me to collect
    useful data on this kind of thing. My personal feeling is that it
    makes sense to err on the side of empathy where it's practical to do
    so.

  reply	other threads:[~2020-07-01 21:58 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 [this message]
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
  -- 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=20200701215744.GA952178@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=james@jramsay.com.au \
    --cc=me@ttaylorr.com \
    --cc=msuchanek@suse.de \
    /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).