Rename extension-pkg-whitelist to extension-pkg-allow-list

[ashb]

Language matters. I'd like to remove all references in Apache Airflow to white list or black list and I found an occurance in our pylintrc file.

The recent global events have made this even more relevant, Here is a well written article for why I think it matters

https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white

It's fairly common to say whitelisting and blacklisting to describe desirable and undesirable things in cyber security.

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 our colleagues and users (and potential future colleagues), this really is a change worth making.

It is possible to make this change in a backwards-compatible fashion (update the docs to use new string, have code look at new and old string when reading rc file) and is clearer too.

[illume]

Hellos 👋

Will a PR for this be accepted? Happy to help :)

I guess we would need to support extension-pkg-whitelist for backwards compatibility?

[pkolbus]

I'd really appreciate seeing this as well. Fostering a welcoming environment matters, and this is one way to help that. And aside from the racial stereotypes, I'll second the notion that clearer terms make it easier for everyone to understand, including those for whom English is not a first language.

I would also note:

• There is also use of the term "blacklist" in the description of ignore and ignore-patterns.
• Master/slave is another pair of terms that also has racial connotations, especially because of United States history -- master is at least a pylintrc section name, so this would also need backwards compatibility work. Perhaps main or global is better here?

I'm also happy to help make this happen.