Hey All, I see this opportunity to rename these things to be what they in plain, descriptive language. Since we will rarely have as many people together considering this change, I find it useful to think what we would have named these things from the beginning and then consider if our naming could be more clear.
I also found the term master odd when I first started using git. It didn't map to anything or have an analogy that I found useful. If we switched to main/trunk or whatever Github decides on, I don't much care what the new name scheme is. Further, I find the allow/deny, accept/block for lists of things as far more descriptive. Some elaboration: when I first came into professional technical circles, I found the tendency to use color as a short-cut for culturally accepted meaning to be potentially confusing to those from other cultures. White/black, red/green/yellow may have received _technical_ meanings from the last 50-60 years or so from the American-centric culture, and I speak ignorantly, since I'm an American, but I don't know if I can assume that other cultures do the same. Robert Roskam On Monday, June 15, 2020 at 12:28:23 PM UTC-4, Tom Carrick 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/53ebc9a5-d795-4449-9900-af948135bd33o%40googlegroups.com.
