It’s been a years long effort, but we’re almost fully past the old “slave” term in Jenkins. These efforts have certainly been positive, and despite the effort, I think it’s been worth it. It’s neat to see more terminology being considered in more detail. Naming things is one of the hardest things programmers do after all!
On Sat, Jun 6, 2020 at 16:59 Rich Bowen <rbo...@rcbowen.com> 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. > > 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 > > > > > > -- Matt Sicker <boa...@gmail.com>
