couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joan Touzet (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2248) Replace "master" and "slave" terminology
Date Tue, 27 May 2014 00:21:01 GMT


Joan Touzet commented on COUCHDB-2248:

I think you underestimate the damage and confusion that changing master-master to "peer-to-peer"
replication would lead to. It inaccurately conflates the "plumbing" of replication, i.e. the
underlying network mechanism, with the "logic" of replication, i.e. whether changes can come
from one or both sides during a replication process.

Remember that "peer-to-peer" networking apps are banned at most corporate institutions. It
suggests a specific architecture that is required to make replication work, that is not at
all necessary for CouchDB. 

In Futon and Fauxton we talk about source and target already. Surely this is sufficient!

> Replace "master" and "slave" terminology
> ----------------------------------------
>                 Key: COUCHDB-2248
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Documentation
>            Reporter: Noah Slater
>            Priority: Trivial
> Inspired by the comments on this PR:
> 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

View raw message