You are viewing a plain text version of this content. The canonical link for it is here.
Posted to diversity@apache.org by Rich Bowen <rb...@rcbowen.com> on 2020/06/06 20:29:32 UTC
Blacklist/whitelist
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
Re: Blacklist/whitelist
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
This may be useful to find and track usage over time:
https://github.com/search?q=org%3Aapache+blacklist&type=Code
https://github.com/search?q=org%3Aapache+whitelist&type=Code
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscribe@apache.org
For additional commands, e-mail: diversity-help@apache.org
Re: Blacklist/whitelist
Posted by Aizhamal Nurmamat kyzy <ai...@apache.org>.
We did the same in Apache Airflow
https://twitter.com/AshBerlin/status/1269916465563607040
On Tue, Jun 9, 2020 at 12:43 PM Naomi Slater <ap...@tumbolia.org> wrote:
> FYI :)
>
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/COUCHDB-2248
>
>
> Sent from my iPhone
>
> > On 9. Jun 2020, at 10:27, Myrle Krantz <my...@apache.org> wrote:
> >
> > Hey Rich, this is pretty awesome. But you're preaching to the choir
> here.
> > Members@ might reach more projects who just haven't thought about it
> yet.
> >
> > But given that several projects *are* working on this, maybe we can get a
> > "Success at Apache" blog post going about it?
> >
> > Best,
> > Myrle
> >
> >> On Sat, Jun 6, 2020 at 10:29 PM Rich Bowen <rb...@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
> >>
>
Re: Blacklist/whitelist
Posted by Naomi Slater <ap...@tumbolia.org>.
FYI :)
https://issues.apache.org/jira/plugins/servlet/mobile#issue/COUCHDB-2248
Sent from my iPhone
> On 9. Jun 2020, at 10:27, Myrle Krantz <my...@apache.org> wrote:
>
> Hey Rich, this is pretty awesome. But you're preaching to the choir here.
> Members@ might reach more projects who just haven't thought about it yet.
>
> But given that several projects *are* working on this, maybe we can get a
> "Success at Apache" blog post going about it?
>
> Best,
> Myrle
>
>> On Sat, Jun 6, 2020 at 10:29 PM Rich Bowen <rb...@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
>>
Re: Blacklist/whitelist
Posted by Trevor Grant <tr...@gmail.com>.
Mahout is up now too. And thank you for the reminder- its such a simple
thing, but totally slipped my mind to do it.
On Tue, Jun 9, 2020 at 7:09 AM Rich Bowen <rb...@rcbowen.com> wrote:
> Having an example if several projects doing this - which I now do - will
> make that message stronger.
>
> I'll write something to members@
>
> Rich
>
>
> On Tue, Jun 9, 2020, 04:27 Myrle Krantz <my...@apache.org> wrote:
>
> > Hey Rich, this is pretty awesome. But you're preaching to the choir
> here.
> > Members@ might reach more projects who just haven't thought about it
> yet.
> >
> > But given that several projects *are* working on this, maybe we can get a
> > "Success at Apache" blog post going about it?
> >
> > Best,
> > Myrle
> >
> > On Sat, Jun 6, 2020 at 10:29 PM Rich Bowen <rb...@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
> > >
> >
>
Re: Blacklist/whitelist
Posted by Rich Bowen <rb...@rcbowen.com>.
Having an example if several projects doing this - which I now do - will
make that message stronger.
I'll write something to members@
Rich
On Tue, Jun 9, 2020, 04:27 Myrle Krantz <my...@apache.org> wrote:
> Hey Rich, this is pretty awesome. But you're preaching to the choir here.
> Members@ might reach more projects who just haven't thought about it yet.
>
> But given that several projects *are* working on this, maybe we can get a
> "Success at Apache" blog post going about it?
>
> Best,
> Myrle
>
> On Sat, Jun 6, 2020 at 10:29 PM Rich Bowen <rb...@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
> >
>
Re: Blacklist/whitelist
Posted by Myrle Krantz <my...@apache.org>.
Hey Rich, this is pretty awesome. But you're preaching to the choir here.
Members@ might reach more projects who just haven't thought about it yet.
But given that several projects *are* working on this, maybe we can get a
"Success at Apache" blog post going about it?
Best,
Myrle
On Sat, Jun 6, 2020 at 10:29 PM Rich Bowen <rb...@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
>
Re: Blacklist/whitelist
Posted by Craig Russell <ap...@gmail.com>.
Hi Paul,
> On Jun 8, 2020, at 1:28 AM, Paul Angus <pa...@shapeblue.com> wrote:
>
> 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...
It would help me understand better if you gave some examples of the challenges you face.
I'm thinking that in "our" documentation and APIs "we" use terminology like primary/replica. In "external" documentation and APIs "they" use the master/slave terminology.
Could "we" still use the primary/replica terminology but call the APIs whatever they are, for example still refer to "our" action as synchronize the replica from the primary while calling the "external" APIs?
A specific example where there is this clash of terminology would really help.
Thanks,
Craig
>
>
> CTO
> paul.angus@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 <km...@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 <rb...@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-unsubscribe@apache.org For additional commands, e-mail: diversity-help@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: diversity-unsubscribe@apache.org
> For additional commands, e-mail: diversity-help@apache.org
>
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscribe@apache.org
For additional commands, e-mail: diversity-help@apache.org
RE: Blacklist/whitelist
Posted by Paul Angus <pa...@shapeblue.com>.
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.angus@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 <km...@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 <rb...@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-unsubscribe@apache.org For additional commands, e-mail: diversity-help@apache.org
Re: Blacklist/whitelist
Posted by Mark Thomas <ma...@apache.org>.
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 <km...@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 <rb...@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-unsubscribe@apache.org
For additional commands, e-mail: diversity-help@apache.org
Re: Blacklist/whitelist
Posted by Matt Sicker <bo...@gmail.com>.
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 <rb...@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 <km...@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 <rb...@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 <bo...@gmail.com>
Re: Blacklist/whitelist
Posted by Rich Bowen <rb...@rcbowen.com>.
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 <km...@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 <rb...@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
> >
>
Re: Blacklist/whitelist
Posted by "Kevin A. McGrail" <km...@apache.org>.
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 <rb...@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
>