Re: Diversity and offensive terminology in RFCs

[[e-mail]]

first they came for the semi-colons,
and I did not complain,
for I was not a semi-colon


python has absolutely no problem favouring and promoting whitespace, which is racist as.
whitespace is so important it gets to come first in the queue on the line. because it's white.


and it's a class-based language, and all the classes are selfish


_this_ is the language you're starting social justice programming in?


Lloyd [e-mail]

On Thursday, September 20, 2018, 7:25 pm, Niels ten Oever <[e-mail]> wrote:

Hi all,

On the hrpc-list [0] there has been an intense conversation which was
spurred by the news that the Python community removed Master/Slave
terminology from its programming language [1].

In the discussion that followed it was remarked that in RFCs terms like
Master/Slave, blacklist/whitelist, man-in-middle, and other terminology
that is offensive to some people and groups is quite common.

This is not a discussion that can be resolved in hrpc, but rather should
be dealt with in the IETF community (because hrpc doesn't make policy
for terminology in the IETF), which is why I am posting this here.

If people find the discussion worthwhile, we might also be just in time
to request a BoF on this topic.

Looking forward to discuss.

Best,

Niels


[0] https://mailarchive.ietf.org/arch/browse/hrpc/
[1]
https://motherboard.vice.com/en_us/article/8x7akv/masterslave-terminology-was-removed-from-python-programming-language


-- 
Niels ten Oever
Researcher and PhD Candidate
Datactive Research Group
University of Amsterdam

PGP fingerprint      2458 0B70 5C4A FD8A 9488
                  643A 0ED8 3F3A 468A C8B3