We already had this discussion before I think, and we decided for Primary/Backup
if you still want to keep the vote for that... [+1] primary/backup [-1000] Leader/Follower On Fri, May 6, 2022 at 6:57 AM Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > > Of the various things mentioned so far I would go with Primary/Backup > or Primary/Replica. > > Sticking to just the original choices in this thread only, that would be: > [+1] Primary/Backup > [-1] Leader/Follower > > On Fri, 6 May 2022 at 11:43, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > > > > On Fri, 6 May 2022 at 07:26, Tetreault, Lucas > > <tetlu...@amazon.com.invalid> wrote: > > > > > > Hey folks, > > > > > > I don’t know if I’m actually allowed to call for a vote given I’m not a > > > committer/PMC member but Michael André Pearce made it clear on Slack that > > > this was the only way to move this discussion forward and come to a final > > > conclusion on the issue so here goes nothing. If I’m not supposed to call > > > for a vote, perhaps someone could “sponsor” this request :) > > > > > > > I'd consider this more of a poll anyway given the format and responses > > so far hehe. Which seems fine, a bona fide formal vote doesnt seem > > necessary for this to me, not unless no [begrudging] agreement can be > > reached in discussion. > > > > > > > > A tweet [1] from a few days ago raised the issue of non-inclusive > > > terminology in the AWS docs related to ActiveMQ [2] and suggested that we > > > should replace “masterslave” with a more inclusive name for the network > > > connector transport. Replacing master/slave nomenclature in ActiveMQ was > > > raised as a Jira issue in July 2020 [3] and again on the mailing list in > > > November 2020 [7]. There was some initial work to rename the git branch > > > from master to main, some attempts at making some changes to the code > > > (https://github.com/apache/activemq/pull/679, > > > https://github.com/apache/activemq/pull/714, > > > https://github.com/apache/activemq/pull/788) and Matt Pavlovich drafted a > > > thorough proposal on the mailing list [6], however we have not been able > > > to come to an agreement on nomenclature so these efforts seem to have > > > stalled out. > > > > > > > > > > > > If we are able to come to an agreement on nomenclature, we can move > > > forward with removing more non-inclusive terminology on the website (I > > > will follow up with some PRs to the website), in discussions with the > > > community and of course in the codebase. This will remove barriers to > > > adoption and make ActiveMQ a more approachable and inclusive project for > > > everyone! Other Apache projects such as Solr and Kafka have moved from > > > master/slave to leader/follower. Leader/follower is also recommended by > > > the IETF [4] and inclusivenaming.org [5] which is supported by companies > > > such as Cisco, Intel, and RedHat. At AWS, we have used active/standby to > > > describe HA deployments, however from previous discussions it's clear > > > that active/standby is not a viable option for this community since > > > 'active' can be used to describe so many things. If we can agree on > > > leader/follower or some alternate we would follow the community's > > > preference and adopt leader/follower to better serve our ActiveMQ users. > > > > > > > To be more specific, Leader/follower is in the inclusivenaming.org > > 'Also acceptable' list rather than their 'Preferred' list where e.g > > Primary/replica and Primary/secondary are. > > > > > > > > > > > From all the previous discussions, I believe we have two options to > > > replace master/slave. Artemis will need to layer on a status (e.g.: > > > active/standby) but I think we can move forward on this vote without > > > deciding what those terms should be assuming people agree these options > > > will support having a status layered on top. > > > > > > > > > > > > Please submit your +1/-1 vote on the following terms and please provide > > > specific comments/alternatives if you’re -1 for both options. > > > > > > [ ] Leader/Follower > > > > > > [ ] Primary/Backup > > > > > > > > > > > > > > > > > > [1] https://twitter.com/owenblacker/status/1517156221207212032 > > > > > > [2] > > > https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors > > > > > > [3] https://issues.apache.org/jira/browse/AMQ-7514 > > > > > > [4] https://tools.ietf.org/id/draft-knodel-terminology-02.html > > > > > > [5] https://inclusivenaming.org/word-lists/tier-1/ > > > [6] https://lists.apache.org/thread/rcwogpchjo9p461hqoj6m89q9t2qpqjj > > > [7] https://lists.apache.org/thread/5ntnrbz1l92xbvno0s2jxhhf7nbs8d9c > > > > > > Lucas Tétreault > > > Software Development Manager, Amazon MQ > > > email: tetlu...@amazon.com<mailto:tetlu...@amazon.com> > > > > > > -- Clebert Suconic