Thanks Xavier! I’m +1 on this idea, and I’m glad this is the extent of what needs to be changed. I recall when I joined the project being pleased at the lack of common offensive terminology. I hadn’t considered whitelist/blacklist, but I can see the argument.
Allowlist/blocklist are kind of a mouthful, though. What do you think of just “allow” and “deny” instead? This is common terminology in ACLs for example, and it doesn’t really seem necessary to say “list” in the config name. Alternatively, looking at the actual configs, it seems like “include”, “include-only” (or “only”) and “exclude” might be more appropriate in context. I hope this doesn’t kick off a round of bikeshedding. I’m really fine either way; I doubt it matters much. I just wanted to see if we can name these configs without making up new multi-syllable words. Thanks for bringing it up! -John On Sat, Jun 20, 2020, at 09:31, Ron Dagostino wrote: > Yes. Thank you. > > > On Jun 20, 2020, at 12:20 AM, Gwen Shapira <g...@confluent.io> wrote: > > > > Thank you so much for this initiative. Small change, but it makes our > > community more inclusive. > > > > Gwen > > > >> On Fri, Jun 19, 2020, 6:02 PM Xavier Léauté <x...@apache.org> wrote: > >> > >> Hi Everyone, > >> > >> There are a number of places in our codebase that use racially charged > >> terms. I am proposing we update them to use more neutral terms. > >> > >> The KIP lists the ones I have found and proposes alternatives. If you see > >> any I missed or did not consider, please reply and I'll add them. > >> > >> > >> https://cwiki.apache.org/confluence/display/KAFKA/KIP-629%3A+Use+racially+neutral+terms+in+our+codebase > >> > >> Thank you, > >> Xavier > >> >
