[
https://issues.apache.org/jira/browse/SLING-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690331#comment-17690331
]
Carsten Ziegeler commented on SLING-11741:
------------------------------------------
This is a comment from [[email protected]] (who is having trouble
with Jira):
{quote}> Change the code to only support the new PIDs and add a Configuration
listener which converts old configurations to new configurations on the fly.
This has my strong preference. Providing a Configuration plugin that users can
tweak at will sounds much better than starting to make backwards-incompatible
changes to our code - or introducing "configuration names bridging" code
everywhere{quote}.
> Provide alternative terminology for inequitable terms
> -----------------------------------------------------
>
> Key: SLING-11741
> URL: https://issues.apache.org/jira/browse/SLING-11741
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Base 3.1.12
> 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)
