[jira] [Commented] (HBASE-24576) Changing "whitelist" and "blacklist" in our docs and project.

["Sean Busbey (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-24576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138059#comment-17138059 ] 

Sean Busbey commented on HBASE-24576:
-------------------------------------

bq. Creating this jira just to start the conversation. Please chip in with ideas.

Conversations go on the dev@hbase list and should have a subject that starts with [DISCUSS]. Please start a thread there.

Feel free to put a PR up against this jira that takes an opinionated approach to the questions you've listed and reference it in the dev list. Generally discussions go much faster if there is a practical example to go with them.

bq. 1. If these words are part of config property name then all customers needs to make the change.

This can be mitigated by using the config property deprecation mechanisms we already have to allow use of the old config name for a version.

bq. 2. There might be some client-server compatibility if we change server side variables/method names.

This kind of thing in particular needs a practical example. Otherwise we get mired in what-if edge case discussions.

> Changing "whitelist" and "blacklist" in our docs and project.
> -------------------------------------------------------------
>
>                 Key: HBASE-24576
>                 URL: https://issues.apache.org/jira/browse/HBASE-24576
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Rushabh Shah
>            Priority: Minor
>
> Replace instances of “whitelist” and “blacklist” in our project, trails, documentation and UI text. 
> We can replace  blacklist with blocklist, blocklisted, or block  and whitelist with allowlist, allowlisted, or allow.
> In my current workplace they are suggesting us to make this change. Also Google has an exhaustive list to write inclusive documentation: https://developers.google.com/style/inclusive-documentation
> There might be few issues while making the change.
> 1. If these words are part of config property name then all customers needs to make the change.
> 2. There might be some client-server compatibility if we change server side variables/method names.
> Creating this jira just to start the conversation. Please chip in with ideas.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)