You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2023/03/03 16:39:00 UTC

[jira] [Closed] (ARTEMIS-3548) Deprecate offensive terms and add new terms

     [ https://issues.apache.org/jira/browse/ARTEMIS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram closed ARTEMIS-3548.
-----------------------------------
    Resolution: Duplicate

> Deprecate offensive terms and add new terms
> -------------------------------------------
>
>                 Key: ARTEMIS-3548
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3548
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>            Reporter: Clebert Suconic
>            Priority: Major
>              Labels: easy
>
> We should deprecate old terms in the whole codebase and add new terms.
> this is an easy task in complexity, however I believe it's a long task in terms of number of changes.
> Terms like:
> master should become primary
> slave should become backup
> white-list: allow-list
>  black-list: deny-list
> In terms of documentation we should just remove any reference to the deprecated terms.
> We should allow (for now at least) older configuration to work fine. (perhaps with a big warn in the logs).
> if these terms are used in external method names, they should be deprecated... (management for instance)
> in internal methods, they can just be renamed.
> also on parameters, they can just be renamed of course.. although I'm not aware of any parameter using offensive words.. most likely they will be XSD and method names.



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