[
https://issues.apache.org/jira/browse/AMQ-7514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377869#comment-17377869
]
Michael Andre Pearce edited comment on AMQ-7514 at 7/9/21, 7:15 AM:
--------------------------------------------------------------------
But the point is there is that history and also your rephrase for artemis is a
bit of a WTF still. Simply lets just avoid the issue, by using different
terminology, theres plenty of available replacement words......
As noted both [~ehossack] and [~tetlucas] i understand per comment on the PR
you raised [~ehossack] you both work at AWS and active is used to replace
master at AWS, but i really dont want a specific vendor's preference to naming
their services dictate what an Apache project gets to call their, especially
when there history to the existing terminology, it is an Apache project NOT an
AWS one..
You have to remember that we are supporting user transitioning from Classic to
Artemis, as such yes terminology alignment is important! Which does mean we
need to cater holistically as a project, that means catering for both Classic
and Artemis
was (Author: michael.andre.pearce):
But the point is there is that history and also your rephrase for artemis is a
bit of a WTF still. Simply lets just avoid the issue, by using different
terminology, theres plenty of available replacement words......
As noted both [~ehossack] and [~tetlucas] i understand per comment on the PR
you raised [~ehossack] you both work at AWS and active is used to replace
master at AWS, but i really dont want a specific vendor's preference to naming
their services dictate what an Apache project gets to call their, especially
when there history to the existing terminology, it is an Apache project NOT an
AWS one..
You have to remember that we are supporting user transitioning from Classic to
Artemis, as such yes Terminology Alignment is important!
> Replace racially charged terms throughout source code, comments and
> documentation
> ---------------------------------------------------------------------------------
>
> Key: AMQ-7514
> URL: https://issues.apache.org/jira/browse/AMQ-7514
> Project: ActiveMQ
> Issue Type: Task
> Reporter: Bruce Snyder
> Priority: Major
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Given the racial charged nature of certain terms in today's world, we must
> pull together to create a plan for changing any such terms throughout all the
> ActiveMQ projects and in the git repos themselves.
>
> Example: [https://activemq.apache.org/masterslave.html]
>
> Here are just a few terms that should be changed: * The following terms are
> being targeted for change:
> *
> ** 'master' and 'slave' should be replaced with the terms 'live' and 'backup'
> ** 'whitelist' and 'blacklist' should be replaced with the terms 'allowlist'
> and 'denylist'
> * Rename all the git 'master' branches to the term 'main'
> Proposal notes from activemq-dev mailing list
> Phase 1:
> 1. Deprecate terms such as ‘master’ and ’slave
> 2. log.warn any configuration change notifications
> 3. Provide compatibility under the covers for deprecated terms
> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> 5. Notify users in an announcement and provide a conversion HOWTO
> Phase 2:
> 1. Remove terminology as part of a major or minor release (SEMVER where ‘y’
> in ‘x.y.z’ is minor version number)
> New terms:
> a. For shared storage: ‘active’ and ’standby’
> b. For replication: ‘primary’ and ‘replica'
> c. For 'white list' and 'blacklist': 'allow list' and 'deny list'
> For example:
> ‘master’ -> ‘active’
> ’slave’ -> ’standby'
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
