[jira] [Commented] (SLING-11741) Provide alternative terminology for inequitable terms

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

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

Carsten Ziegeler commented on SLING-11741:
------------------------------------------

This change is a little bit complex. We have the problematic language in the PID of configurations as well as in property names.
I think we have two options:
* "Duplicate" the logic and handle old configuration PIDs as well as new PIDs
* Change the code to only support the new PIDs and add a Configuration listener which converts old configurations to new configurations on the fly.

> Provide alternative terminology for inequitable terms
> -----------------------------------------------------
>
>                 Key: SLING-11741
>                 URL: https://issues.apache.org/jira/browse/SLING-11741
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Cioriia Cristian
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Apache Sling Login Admin Whitelist has occurrences of "whitelist" and "blacklist" e.g. "whitelist.bypass", "whitelist.bundles.regexp" which is considered inequitable terminology and some customers are prevented to use these terms by their git commit policies. 
> Therefore, some more acceptable equivalents should be provided for these terms. The proposal is to provide the "allowedlist.bypass" and "allowedlist.bundles.regexp" alternatives for them



--
This message was sent by Atlassian Jira
(v8.20.10#820010)