Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Wed, 28 May 2014 21:31:04 +0000 (UTC)
From: "Alexander Shorin (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12716693.1401145418893.34245.1401312664654@arcas>
In-Reply-To: <JIRA.12716693.1401145418893@arcas>
References: <JIRA.12716693.1401145418893@arcas>
Subject: [jira] [Resolved] (COUCHDB-2248) Replace "master" and "slave"
 terminology
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Shorin resolved COUCHDB-2248.
---------------------------------------

    Resolution: Fixed
      Assignee: Alexander Shorin

Fixed in [11f726e|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=11f726e]

> 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)