couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2248) Replace "master" and "slave" terminology
Date Wed, 28 May 2014 16:18:02 GMT


Robert Newson commented on COUCHDB-2248:

"because it is discriminatory and offensive speech."

This is your opinion but you state it like a fact. Multiple voices have expressed that they
do not agree with you. You respond by dismissing their right to express that opinion.

This thread will never end but I will try again.

To update the documentation, please just show an actual diff and we can discuss or vote on

If you intend, by this ticket, to prohibit us all from using the term "master/slave" when
referring to databases replication in the sense of article,
then please accept that it's not happening.

> 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