The "default" is name is just a convention. It can be other things and after a few days of "teething" issues, and everyone will be back to being as productive as they are right now.
Sent from Outlook Mobile<https://aka.ms/blhgte> ________________________________ From: django-developers@googlegroups.com <django-developers@googlegroups.com> on behalf of אורי <u...@speedy.net> Sent: Tuesday, June 16, 2020 7:05:19 PM To: Django developers (Contributions to Django itself) <django-developers@googlegroups.com> Subject: Re: The blacklist / master issue I think master is the default branch name in any Git repository. It's not about Django and even not GitHub. Do you want to change the default branch name in Git? אורי u...@speedy.net<mailto:u...@speedy.net> On Mon, Jun 15, 2020 at 7:28 PM Tom Carrick <t...@carrick.eu<mailto:t...@carrick.eu>> wrote: This ticket was closed wontfix<https://code.djangoproject.com/ticket/31670#ticket> as requiring a discussion here. David Smith mentioned this Tox issue<https://github.com/tox-dev/tox/issues/1491> stating it had been closed, but to me it seems like it hasn't been closed (maybe there's something I can't see) and apparently a PR would be accepted to add aliases at the least (this is more recent than the comment on the Django ticket). My impetus to bring this up mostly comes from reading this ZDNet article<https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/> - it seems like Google have already made moves in this direction and GitHub is also planning to. Usually Django is somewhere near the front for these types of changes. I'm leaning towards renaming the master branch and wherever else we use that terminology, but I'm less sure about black/whitelist, though right now it seems more positive than negative. Most arguments against use some kind of etymological argument, but I don't think debates about historical terms are as interesting as how they affect people in the here and now. I don't think there is an easy answer here, and I open this can of worms somewhat reluctantly. I do think Luke is correct that we should be concerned with our credibility if we wrongly change this, but I'm also worried about our credibility if we don't. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com<mailto:django-developers+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHoz%3DMZrOAQ94Whn0PpDa%2BuJzGSs%3DWAWHbO0nn8rc0D94uUAcw%40mail.gmail.com<https://groups.google.com/d/msgid/django-developers/CAHoz%3DMZrOAQ94Whn0PpDa%2BuJzGSs%3DWAWHbO0nn8rc0D94uUAcw%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com<mailto:django-developers+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABD5YeH3ixuxTqBvB6FdLzimDbB4D5uGHKEawwjvqXVHU%3DcvKg%40mail.gmail.com<https://groups.google.com/d/msgid/django-developers/CABD5YeH3ixuxTqBvB6FdLzimDbB4D5uGHKEawwjvqXVHU%3DcvKg%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/BYAPR14MB2918D1D9008D787BC2AF1F95A39D0%40BYAPR14MB2918.namprd14.prod.outlook.com.
