Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usage of blacklist/whitelist terms #970

Closed
suryag10 opened this issue May 18, 2021 · 3 comments
Closed

Usage of blacklist/whitelist terms #970

suryag10 opened this issue May 18, 2021 · 3 comments

Comments

@suryag10
Copy link

I see that the terms whitelist is being used a lot in the enterprise-gateway. There has been discussion in the opensource community to use the alternative terms for the same. For example: https://news.ycombinator.com/item?id=23801134 , kubernetes/website#6525. Is there any similar approach being taken here as well to change the terms?

@kevin-bates
Copy link
Member

Hi @suryag10 - thank you for bringing this up. Yes, this is something I've thought about for a while and has been discussed in this repository (see #957 (comment)). I'm not sure how @telamonian is coming along with things, but it's on our radar. I've also proposed a similar change for the kernelspec.whitelist trait in jupyter_client.

As you might imagine, navigating configuration property name changes can be a bit disruptive, so its not always straightforward.

@suryag10
Copy link
Author

Thx Kevin.

@kevin-bates
Copy link
Member

Since this is being addressed in #1000, I'm going to close this issue (see also #957).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants