I'd argue that since Django is an international framework, we should strive to set an international standard. If a certain word is off-putting or problematic to individuals in our community, and if it does not convey an accurate and least astonishing meaning to a non-native English speaker, then we should definitely change it.
On Fri, Jun 19, 2020 at 2:54 PM Alexander Lyabah <a.lya...@checkio.org> wrote: > > Django in international framework, not US-framework. You should not change > variable names just because meaning of some words have been changed in US > recently. Those words have been used in source-code for years, and nobody > put racism in those word when this framework was founded and nobody puts > any racism in when one is using for creation something big and meaningful. > > What I'm encourage you to do, is to thing farther than what is going on > right now. > > If Django Foundation really want to help in this revolution - add a banner > on that landing page. Feel free to choose > > https://eji.org/ > https://org2.salsalabs.com/o/6857/p/salsa/donation/common/public/ > > And this kind of contribution will work much better. > > Thank you, for this opportunity to share my opinion. > > On Monday, June 15, 2020 at 7:28:23 PM UTC+3, 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/1c9178a3-cb80-428c-bacb-e8904695f6b6o%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/1c9178a3-cb80-428c-bacb-e8904695f6b6o%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/CAJNa-uOOWNRmAnDhiydQC-MrEsRDyED%2B_PJzFDu5gU6GjqSs1A%40mail.gmail.com.
