You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/06/04 08:31:00 UTC

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

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

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

@cristic83 Thanks for your great work on this PR; I've decided to create a new branch based on your code with a few modifications that were suggested as part of this review and some additional improvements at #11

> 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
>             Fix For: JCR Base 3.1.16
>
>          Time Spent: 2h 10m
>  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)