[
https://issues.apache.org/jira/browse/COUCHDB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057318#comment-14057318
]
ASF subversion and git services commented on COUCHDB-2248:
----------------------------------------------------------
Commit 679af60c7abbac03fd223738407e485611cb2275 in couchdb-documentation's
branch refs/heads/import-master from [~kxepal]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-documentation.git;h=679af60
]
Use "single-master" technical term which inspired by RFC 3384
COUCHDB-2248
> 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
> Assignee: Alexander Shorin
> 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)
