airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kaxil Naik <kaxiln...@gmail.com>
Subject Re: Language matters - don't use the term "whitelist" in Apache Airflow
Date Mon, 08 Jun 2020 08:35:09 GMT
👏

On Mon, Jun 8, 2020, 08:28 Robin Edwards <rob@bidnamic.com> wrote:

> Nice one Ash,
>
> +1
>
> R
>
> On Mon, 8 Jun 2020 at 05:04, Jarek Potiuk <Jarek.Potiuk@polidea.com>
> wrote:
> >
> > Indeed. Thanks Ash! Much appreciated!
> >
> > J.
> >
> > On Mon, Jun 8, 2020 at 1:40 AM Kevin Yang <yrqls21@gmail.com> wrote:
> >
> > > Thank you Ash. +1 and stamped.
> > >
> > >
> > > Cheers,
> > > Kevin Y
> > >
> > > On Sun, Jun 7, 2020 at 2:46 PM Deng Xiaodong <xd.deng.r@gmail.com>
> wrote:
> > >
> > > > Appreciate your effort, Ash. And a +1 for this.
> > > >
> > > >
> > > > XD
> > > >
> > > > On Sun, Jun 7, 2020 at 23:31 Ash Berlin-Taylor <ash@apache.org>
> wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > I have just opened a PR to rename the few of the remaining
> instances of
> > > > > whitelist or blacklist in our code base. (There weren't many.)
> There
> > > are
> > > > > some we can't remove yet (because they are modules/classes/config
> from
> > > > > external modules. I have opened issues in those projects for most
> of
> > > > them)
> > > > >
> > > > > It's fairly common to say whitelisting and blacklisting to describe
> > > > > desirable and undesirable things in cyber security. Just because
> > > > > it is common doesn't mean it's right.
> > > > >
> > > > > However, there's an issue with the terminology. It only makes
> sense if
> > > > > you equate white with 'good, permitted, safe' and black with 'bad,
> > > > > dangerous, forbidden'. There are some obvious problems with this.
> > > > >
> > > > > You may not see why this matters. If you're not adversely affected
> by
> > > > > racial stereotyping yourself, then please count yourself lucky. For
> > > some
> > > > > of your friends and colleagues (and potential future colleagues),
> this
> > > > > really is a change worth making.
> > > > >
> > > > > From now on, we will use 'allow list' and 'deny list' in place of
> > > > > 'whitelist' and 'blacklist' wherever possible. Which, in fact, is
> > > > > clearer and less ambiguous. So as well as being more inclusive of
> all,
> > > > > this is a net benefit to our understandability.
> > > > >
> > > > > (Words mostly borrowed from
> > > > >
> https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white)
> > > > >
> > > > > And to reaffirm the trailer from that blog post: If you’re thinking
> > > > > about getting in touch saying "this is political correctness gone
> mad",
> > > > or
> > > > > "what's the big deal", don’t bother. If that is your view then
you
> are
> > > > > not welcome in this community.
> > > > >
> > > > > The PR is https://github.com/apache/airflow/pull/9174
> > > > >
> > > > > -ash
> > > > >
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message