Hi, just my 2 cents:
While I am generally critical of changing language to achieve social progress, I see no harm in using "main", "develop" or something like that instead of "master". There might be a tool or two out there that treat "master" specially, but I can't think of anything that would directly affect Django. If Github is going to settle for "main", it will likely become the new convention, so maybe Django should pick that one? allow_list / deny_list is a similar case. I see no advantage in keeping the current names. To me, allow_list / deny_list is at least as clear as white_list / black_list. When Django directly references externally defined technical terms (e.g. underlying APIs), I think more consideration is needed. For RFC 5782, I think that is not the case. Regards, René -- René Fleschenberg -- 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/7d0f24b3-e042-0964-6be0-6689fc930af1%40fleschenberg.net.
