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/03 09:23:00 UTC
[jira] [Commented] (SLING-11742) Provide alternative equitable terminology for properties
[ https://issues.apache.org/jira/browse/SLING-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728943#comment-17728943 ]
Carsten Ziegeler commented on SLING-11742:
------------------------------------------
In order to incorporate all our comments and change requests, I created a new PR based on [~cioriia] good work:
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/97
> Provide alternative equitable terminology for properties
> --------------------------------------------------------
>
> Key: SLING-11742
> URL: https://issues.apache.org/jira/browse/SLING-11742
> Project: Sling
> Issue Type: Improvement
> Reporter: Cioriia Cristian
> Assignee: Cioriia Cristian
> Priority: Major
> Fix For: Resource Resolver 1.10.2
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The "resource.resolver.vanitypath.blacklist" and "resource.resolver.vanitypath.whitelist" proeprties contain terms which are 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 "resource.resolver.vanitypath.deniedlist" and "resource.resolver.vanitypath.allowedlist" alternatives for them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)