Note that the term "blacklist" only appears twice in the Django tree and only in comments/docs, as shown by David's patch. The first one can be omitted while the second one can be replaced by "exclude". That is trivial to do and shouldn't even require a discussion.
About replacing "whitelist" par "allowlist", I'm not totally convinced but will accept any community decision. It has a very small impact change in code (in EmailValidator). Changing git "master" branch names is really looking ridiculous to me, but I can understand that it might be linked to cultural sensibilities. This will generate many work overhead, for what gain? A "master" is a totally valid word in many contexts that have nothing to do with slavery. We should primarily fight against racism by education and our own day-to-day behavior. Claude -- 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/d327c497-18f7-4b50-8b38-93b0c0bea330o%40googlegroups.com.
