Re: Consensus on a new default branch name

[Jeff King <peff@peff.net>]

On Tue, Jun 16, 2020 at 08:11:01PM +0300, Oleg wrote:

> > Not statistics, but anecdotally, many major projects and communities
> > have expressed interest in switching. Some of them are listed here:
> > 
> >   https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/
> 
> This is not "many", Jeff :-D. There is info just about *few* major projects
> (i counted not more than *15*!), that also politically biased and are
> intimidated.

I didn't count them. 15 who have already said they are interested does
seem like "many" to me, especially as I'd expect more to do so as the
issue gets more attention. I don't think it matters if they're
politically biased or not. I just said they expressed interest in
switching.

But anyway. You asked what I based my statement on. I told you.

> > I don't think 100 million is the right number to think about. Many of
> > those aren't active, or aren't collaborative. A project like Chrome
> > changing their branch name has a much bigger impact than somebody's
> > homework repo with three commits.
> 
> Jeff, this is a discrimination ;-). And no. This isn't right. How many
> repos on github is inactive? May be 20 millions? Add to 80 millions gitlab and
> all another git repos from the world. I think we can easily collect around
> 150-200 million of active repos. Do you really think that count of developers of
> these all projects be less than count of Chrome developers? Why do 15 projects
> (politically biased) outweighs 200 millions of projects? Is this example of
> democracy or rationale mind? May be some there is corruption :-)?

Please stop making strawmen. I never said that the number of Chrome
developers was higher than the number of other developers. The original
claim I made that started this portion of the thread was only that
projects have expressed interest in changing, so tools are going to deal
with seeing non-master branches (and in fact already have been).

> And even so - 6% :-D. Jeff, this is really needed thing! :-D

Again, my point wasn't that a majority of people have changed or even
would change.My point was just that a significant enough percentage of
repos use the non-default name that it's a thing tools will need to deal
with. Perhaps you think 6% isn't enough to say so, but we may just agree
to disagree there.

> > question is whether the more abstract benefits to people are worth the
> > potential costs.
> 
> Of course, not. This is obvious.

You're asserting your position without providing any argument here.
Clearly other people feel the opposite way.

To be honest, I am not sure if it the benefits outweigh the costs or
not, and I am skeptical that any kind of accurate data gathering (e.g.,
a poll of opinions) could be done at this point, both because of the
vagueness of the task and because the issue has become so charged (not
just within Git, but in the greater world). But I'm inclined to err on
the side of empathy, especially if we can keep the cost side relatively
low.

-Peff