Hi Michael, Je ven, 2019-04-26 je 09:24 +1000, Michael Gratton skribis:
On Thu, Apr 25, 2019 at 09:02, Carmen Bianca Bakker <carmen carmenbianca eu> wrote:Defaults and conventions matter. One reason I like GNOME so much is because the defaults are amazing. And while "master" is a bit of a sucky default, it still has a lot of weight as a default. And I question whether it is worth the effort to change that default over a tiny bit of suckiness.This precisely indicates the problem with the current situation: The current default sucks, but nobody is willing to change it because nearly everyone every one else is doing it.
I understand this sentiment. And while I can appreciate wanting to change sucky defaults, I suppose what I'm trying to say is that maybe the default isn't sucky enough to justify going through all the pain of changing it. I'm making the assertion that "master" in the context of Git branches is not an obstacle towards social inclusiveness within GNOME. That assertion is entirely unfounded, but it's what makes sense to me. If someone can demonstrate that "master"---in this specific context--- is indeed harmful, then obviously renaming the default branch would be a goal worth pursuing. But I'm doubtful whether it is possible to demonstrate that, or whether anybody has the resources available to do that. So I don't know what the best thing to do is. It's like knowing that driving on the left side of the road is just a slight little bit safer than driving on the right side of the road. It'd be _nice_ if we could all just change to driving on the left side of the road, but the monumental effort that that would require just isn't worth the extremely slight bump in safety. Maybe that metaphor isn't one-to-one applicable, but I think it gets my sentiment across.
(Carmen, this isn't a dig at you, but at us in general)
:-) With kindness, Carmen
Attachment:
signature.asc
Description: This is a digitally signed message part