[
https://issues.apache.org/jira/browse/COUCHDB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009150#comment-14009150
]
Noah Slater commented on COUCHDB-2248:
--------------------------------------
What? Nope. I'm just trying to be clear about vetos, as we've had a problem
with them historically. No vetos means that majority approval would be in
effect. Majority approval is three binding +1 votes and no binding -1 votes.
Which is interesting, because that actually gives you the power to block this
change anyway.
I really hope you will not block the change. Considering how icky these terms
make people feel, and considering that we have non-problematic replacements for
them, I really see no reason to block the change.
> Replace "master" and "slave" terminology
> ----------------------------------------
>
> Key: COUCHDB-2248
> URL: https://issues.apache.org/jira/browse/COUCHDB-2248
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Documentation
> Reporter: Noah Slater
> Priority: Trivial
>
> Inspired by the comments on this PR:
> https://github.com/django/django/pull/2692
> Summary is: `master` and `slave` are racially charged terms, and it would be
> good to avoid them. Django have gone for `primary` and `replica`. But we also
> have to deal with what we now call multi-master setups. I propose "peer to
> peer" as a replacement, or just "peer" if you're describing one node.
> As far as I can tell, the primary work here is the docs. The wiki and any
> supporting material can be updated after.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
