couchdb-dev mailing list archives

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


Noah Slater updated COUCHDB-2248:

    Comment: was deleted

(was: Are we seriously going to let politics affect functionality? Just because a few overly
sensitive people think that someone might get offended a tiny bit by the terminology used
we have to change it all because "God forbid anyone ever get offended". If you go out of your
way to make everything so politically correct that you think it's okay to replace a well known
standard with something obscure just in case anyone gets offended, you are just plain wrong.
If you get offended by this grow up. The world isn't a nice place, it has no obligation to
be. While unrighteous, prejudiced discrimination is something we should try our best to get
rid of. You don't make any progress by going out of your way to alter very minor potential
'triggers' while disrupting the workflow of huge projects. I'm a guy who hears racist jokes
about his race regularly, and while a lot of them are offensive, and some of them may not
even be funny, you don't see me crying about things like this. When something obviously has
no negative connotation, you can't just fill in the blanks and say that it should be changed.
This is only going to fuel the cause of everyone who does support these bad things since now
they'll just see movements seeking equality as a bunch of whiners. By making a huge fuss about
something as minor as this you basically devalue all the actual problems.)

> 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