I'm working on blacklist/whitelist in Cloudsstack (nearly there); But master/slave is a tough one because we're orchestrating components that themselves use master/slave terminology...
CTO paul.an...@shapeblue.com www.shapeblue.com -----Original Message----- From: Mark Thomas <ma...@apache.org> Sent: 07 June 2020 19:37 To: diversity@apache.org Subject: Re: Blacklist/whitelist On 06/06/2020 22:58, Rich Bowen wrote: > I imagine it is a significantly larger challenge there. If a project > that prominently relies on these types of lists can do it we all can. Thanks for the nudge Rich. I didn't recall seeing those terms in the Tomcat codebase but your mail prompted me to go and look and I did find an instance in the docs that I have now changed. Mark > Rich > > > On Sat, Jun 6, 2020, 16:56 Kevin A. McGrail <kmcgr...@apache.org> wrote: > >> The spamassassin project has been working towards this same goal for >> a few months now too. >> >> On Sat, Jun 6, 2020, 16:29 Rich Bowen <rbo...@rcbowen.com> wrote: >> >>> I just made a few commits which removed all occurrences of "blacklist" >> from >>> the Apache httpd documentation. It took just a few minutes. >>> >>> I encourage each of you to take a few minutes to do the same for >>> your project(s). >>> >>> Please note that I have zero interest in debating whether this is >> necessary >>> or beneficial or offensive or whatever. Instead ask yourself this >> question: >>> >>> If I can make a tiny change to my software which makes JUST ONE >>> black contributor feel more welcome and has no negative impact on >>> the functionality, why wouldn't I? >>> >>> More thoughts on word choice here: >>> https://lethargy.org/~jesus/writes/a-guide-to-nomenclature-selection >>> / >>> >>> >>> Rich >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: diversity-unsubscr...@apache.org For additional commands, e-mail: diversity-h...@apache.org
