[
https://issues.apache.org/jira/browse/COUCHDB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009783#comment-14009783
]
Alexander Shorin commented on COUCHDB-2248:
-------------------------------------------
If you're going to introduce new term in place of common one ("replica" instead
of "slave") please describe it in glossary (worth to finally establish it in
our docs) to remove any confusion and unclear understanding it meaning. Your
actions would have much more weight if you can provide any references to
existed Authoritative sources where the same/similar term is used in the
same/similar context with the same/similar meaning. Please take care about
localization since your proposed replacement may not have direct qualified
analogue in other languages and may only case chain reaction of terminology
confusion.
If you're going to refuse from usage some English words in CouchDB
docs/posts/papers/stuff, please setup wiki page as about words to abuse with
reasons why and recommended replacements to help technical communicators avoid
them in writing docs, posts, running talks and so on.
> 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)
