The simple fact that we don't know how to deal with this type of discussion can say a lot about of our community. Anyway when I started this discussion I didn't imagine that I would receive so many negative feedbacks.
-- Cheers, Daniel Rodrigues. geek...@php.net https://twitter.com/geekcom2 ________________________________ De: Kalle Sommer Nielsen <ka...@php.net> Enviado: segunda-feira, 15 de junho de 2020 20:23 Para: Deleu <deleu...@gmail.com> Cc: Lynn <kja...@gmail.com>; PHP internals <internals@lists.php.net> Assunto: Re: [PHP-DEV] About the use of the terms master/slave and blacklist, proposal to replace. Den tir. 16. jun. 2020 kl. 02.12 skrev Deleu <deleu...@gmail.com>: > > > I am sorry but I do not think you understand the scale of which the > > PHP project is at. > > I'm sorry but you did not get my point. As mentioned above theres 170 places > mentioning the term blacklist. When I said "the argument of BC without > knowing the scope" I meant to express that perhaps 1, 10 or 100 of these > could be changed without any BC impact, meaning that perhaps they barely need > an RFC in the first place as it could potentially be just internal code. > Instead of being negative and dismissive of a chance at a diverse and > welcoming environment, let's see what we can easily do first and take the > first step towards making a statement in favor of a better community. So let me get this straight, you feel uneasy that internally in PHP there is something called blacklist, a variable or something that, and changing those are making a statement in favor of a better community. Well that is also a biased opinion, I am certain we can dispute what is better for the community for days without end. What purpose does it serve to change the internal variables from blacklist to blocklist when it still needs to interact with the term blacklist, why would we use two different terminologies for the same thing? I am being negative towards this change because like I have stated before that it is a change for the sake of change and I do not find the justifications presented here to be strong enough reason to break working code because you feel offended by some political propaganda that has made you believe that blacklist is a racial slur, or whatever it might be. Censoring industry terms that has correlation to racial remarks whatsoever sends a signal that "Hey the PHP project would rather allow breaking your code because it needs to be diverse", what happens when the next flavor of the month term comes that needs to be censored for whatever reason, should we then also break that? Because if that was the case we could do that nonstop. I still don't think it will make the community better by breaking already working code. To say that the current naming is not diverse and welcoming is almost disrespectful in itself. -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
