First things first:

I'm glad, Django changed master/slave and blacklist/whitelist to more 
appropriate and adequate terms. Naming things is hard. And just because 
somebody came up with a name decades ago doesn't mean it can't — or even 
shouldn't — be changed. Especially when there are more descriptive alternatives.

I'm glad, Django is in the position to take a stance for a more inclusive 
language in technology and against decades old, racist, terminology.

I'm glad, Django, as several other software projects out there, picked up on 
the Black Lives Matter protests happening in the US and around the globe.

I'm glad, Django has a Code of Conduct 
(https://www.djangoproject.com/conduct/) and a community where racist behavior 
is not tolerated.

---

Alexander, since you brought up the news, I'm sure you're aware that the 
BlackLivesMatter protests are happening around the globe and are not only in 
the US. Racist behavior exists pretty much everywhere, certainly in the US and 
Germany.

I'm a young, white man, from Germany. I have never experienced any racist 
behavior towards me. But I'm fairly certain that there are plenty of people on 
this list who have.

We're still living in a society where white men are privileged in many ways. If 
I can stand in solidarity and support of black colleagues, friends, and members 
of the Django community, by reexamining and addressing language choices that 
have ugly backgrounds to their history, I'm glad!

Markus

On Sun, Jun 21, 2020, at 10:10 PM, Alexander Lyabah wrote:
>  Daryl, that is very strange, that you bring it here now.
> 
> > One of Django's strengths is that decision making is *not* polluted by one 
> > strong opinion, a whim by a marketing department, or trend-following. 
> 
> renaming whitelist and blacklist is exactly what is in trend right now. 
> I understand that not everybody are following US-news, but if you 
> google "blacklist blm" you will find, how big the trend is, actually.
> 
> Also, thank you sharing those link, but can you plz elaborate more, why 
> do you bring those and what do you what to proof by sharing those 
> links, so when I read those links again, I know on what point I should 
> focus more. 
> 
> Thank you for being involved in this conversation.
> 
>  -- 
>  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/267f6649-a434-47fb-93c9-880b594d213ao%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/django-developers/267f6649-a434-47fb-93c9-880b594d213ao%40googlegroups.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/cd9101a8-f93d-4ba7-b6e8-f97f8bc57d3b%40beta.fastmail.com.
          • ... Alexander Lyabah
            • ... Alexander Lyabah
            • ... Hooshyar Naraghi
    • ... Ahmad A. Hussein
      • ... Alexander Lyabah
  • Re:... Alexandr Tatarinov
  • Re:... Robert Roskam
    • ... Alexander Lyabah
      • ... Daryl
        • ... Alexander Lyabah
          • ... Markus Holtermann
          • ... Daryl
            • ... Alexander Lyabah
              • ... John Obelenus
              • ... Alexander Lyabah
              • ... Daryl
  • Re:... Mark Bailey
    • ... Markus Holtermann
      • ... Kenneth
        • ... 'Adam Johnson' via Django developers (Contributions to Django itself)
          • ... Matthias Kestenholz

Reply via email to