couchdb-dev mailing list archives

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


Noah Slater commented on COUCHDB-2248:

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

I have never dismissed anybody's right to express their opinion.

I accept your opinion that it is not discriminatory or offensive speech. But as I said in
my previous comment, "there are people in the tech community who do. You do not need to understand
that, or even agree with it. The fact remains. As a community that values openness, inclusivity,
and diversity, this is a topic that we should take seriously."

The argument seems to be that because there are a few people on this ticket (or friends of
people on this ticket) who do not see the issue, we should not make the change. My argument
is that as a community that cares about diversity, this argument doesn't hold. We should acknowledge
that for some people this is an issue, and we should make the appropriate changes.

Acknowledging that other people have diverse perspectives is a key part of building a diverse

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

I have done, in my previous comment. I propose we change it to:

"You could use multi-master, single-master, partitioning, sharding, write-through caches,
and all sorts of other complex techniques."

(Thanks to Alexander for this suggestion!)

As for the master/slave term in general. That is beyond the scope of this ticket. We currently
do not have any need to use it in our docs or on our website. Though if we did, I would want
us to consider alternate terms. Discussing that now is unnecessary. Please let's just focus
on the one instance of "slave" we have at the moment. 

> 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