[
https://issues.apache.org/jira/browse/SLING-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650900#comment-17650900
]
Robert Munteanu commented on SLING-11741:
-----------------------------------------
Thanks for the report [~cioriia]. For context, we had some discussion already
at
https://cwiki.apache.org/confluence/display/SLING/Removal+of+problematic+language
. Something that is quite important is to maintain backwards compatibility, so
the impact of each change must be judged individually.
As an example, it is safe to support a new configuration property named
"allowlist.bypass", but it is not safe to remove support for "whitelist.bypass".
> 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
>
> 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)
