[ 
https://issues.apache.org/jira/browse/COUCHDB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009717#comment-14009717
 ] 

Noah Slater commented on COUCHDB-2248:
--------------------------------------

When it comes to American culture, it is impossible to disentangle slavery and 
racism. The effects of slavery reach so far into the American psyche that I 
expect it is an ever-present reality for most POCs. It really is not our place 
as (mostly, on this thread) white Europeans to be deciding (based on logic) 
what is and isn't a legitimate complaint. We lack the necessary lived 
experience. The best we could hope for is to ask American POCs how they feel 
about it. (Such a comment from an American POC is precisely what motivated the 
original ticket, by the way.)

I am more sympathetic to the notion that a nomenclature change my introduce 
confusion. But again, to talk about "established" terms in an industry which is 
only a few decades old is clearly absurd. We are in the unique position of 
being able to influence the world and leave it slightly better than when we 
found it. I have no patience for feigned defeatism.



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

Reply via email to