undefined | Better HN

0 pointslondons_explore2y ago0 comments

It mostly happens via private messaging, but yes. It's part of the "you are either with us or against us" mentality of many campaign groups.

See ~2 years ago when every opensource project was forced to publish a code of conduct and diversity and inclusion policy... Often the people asking for the policies weren't even users of the software involved, let alone interested in writing code for the proect. That campaign seems to have ended, and nobody cares if your project has either anymore.

0 comments

azangru2y ago

> That campaign seems to have ended, and nobody cares if your project has either anymore.

Has the movement to rename every master branch to main quietened down as well?

anononaut2y ago

This still makes my blood boil. I've seen people dance around the word master now.

justrealist2y ago

GitHub changed the default to "main" so 95% of new projects will default there.

dijit2y ago

Gitlab too, and there is enough reason to believe the tool itself will change to “main”: https://news.ycombinator.com/item?id=26488039

dijit2y ago

Only because it was successful.

simoncion2y ago

There are many active 'master' branches at work, and many, many active 'master' branches on Github.

By that measure, the movement to rename every 'master' branch to 'main' has been a resounding failure.

(If you look at the events at the time it sprung up, you could pretty safely say that it was encouraged as a way to distract from the then-current "GitHub is doing business with US's ICE!" hatestorm, and man was it successful.)

dijit2y ago

If your only active metric is "all or nothing". Sure, there's a few.

But the major git hosting platforms are only using 'main' as the default for new branches, and there is significant enough social stigma for new projects that it's preferred to use main.

I don't have precise statistics, but I would happily wager that even though master was the default for so long that the majority of git repositories that have been contributed to in the last 30 days are not 'master' as the default branch name.

To change a default with such inertia as to completely skew the demographic in favour of the new rather than the status quo: I would certainly merit that as success.

1 more reply

j / k navigate · click thread line to collapse

0 comments

azangru2y ago

> That campaign seems to have ended, and nobody cares if your project has either anymore.

Has the movement to rename every master branch to main quietened down as well?

anononaut2y ago

This still makes my blood boil. I've seen people dance around the word master now.

justrealist2y ago

GitHub changed the default to "main" so 95% of new projects will default there.

dijit2y ago

Gitlab too, and there is enough reason to believe the tool itself will change to “main”: https://news.ycombinator.com/item?id=26488039

dijit2y ago

Only because it was successful.

simoncion2y ago

There are many active 'master' branches at work, and many, many active 'master' branches on Github.

By that measure, the movement to rename every 'master' branch to 'main' has been a resounding failure.

dijit2y ago

If your only active metric is "all or nothing". Sure, there's a few.

But the major git hosting platforms are only using 'main' as the default for new branches, and there is significant enough social stigma for new projects that it's preferred to use main.

To change a default with such inertia as to completely skew the demographic in favour of the new rather than the status quo: I would certainly merit that as success.

1 more reply

j / k navigate · click thread line to collapse