On Sun, Jul 05, 2020 at 09:39:29AM +1000, Dave Airlie wrote: > I don't totally agree on that, because like the CoC discussion, people > need concrete examples. People need reasons, saying simply "be > inclusive" doesn't work. > > You say "be inclusive" people don't think about it, they just go "I'm > inclusive" and proceed, never questioning what it means to be > inclusive, they normalise inclusivity to their self image and within > their lives where they might never confront anything like this. > > I don't doubt we get the American/Ottoman/Barbery coast people and the > correct answer to those people is to tell them to examine why they > suddenly care about Barbery slavery now when they have never even > heard or worried about it before. Why haven't they submitted patches > removing slavery terminology from the kernel before?
Right; this part of the patch provides a temporal explanation for "but why now?" and acts as an internal reference, instead of pointing to external[1] sources, which lack the Linux-specific contextualization. Additionally, I think it provides rebuttals to many of the specious arguments against inclusive terminology (and it could perhaps gain more, as we've already seen in this thread, against slippery slope arguments). It also attempts to acknowledge what this change in the kernel processes provides to the world in general: it's a fairly local change to make our development community less disruptive to those that would seek to join it -- it does not, and cannot, solve global racism (though that would be nice). [1] https://tools.ietf.org/id/draft-knodel-terminology-01.html -- Kees Cook
