#22667: Replace occurrences of master/slave terminology with leader/follower
-------------------------------------+-------------------------------------
     Reporter:  fcurella             |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |                  Version:  1.6
    Component:  Documentation        |               Resolution:  fixed
     Severity:  Normal               |             Triage Stage:
     Keywords:                       |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by erikr):

 I can definitely see the point of this ticket, but I'm worried that this
 particular change significantly reduces the readability of the
 documentation, especially for those less familiar with database
 terminology or not native English. Personally, I had never heard of
 leader/follower in the context of SQL replication before, and I'm not sure
 how fast I would have figured out, if I had not seen this ticket. In
 addition, we've also replaced all references to master in the multi-db
 support, where it does not seem to be used in master/slave context.

 [[http://www.postgresql.org/docs/9.1/static/high-
 availability.html|PostgreSQL]] uses master/slave or primary/standby, and
 [[http://dev.mysql.com/doc/refman/5.7/en/replication.html|MySQL]] only
 uses master/slave. [[https://devcenter.heroku.com/articles/heroku-
 postgres-follower-databases|Heroku]] mixes follower and slave. I've also
 heard replica in the past, which is my favourite (standby suggests cold to
 me).

 Suggestion: use the terminology master and replica. On the first use of
 replica in each document, add: "(referred to as slave or standby by some
 databases)". That seems like a good middle ground to me between avoiding
 problematic historical associations and keeping our documentation readable
 and understandable, even by those new to development or not being native
 English speakers.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22667#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.6455deed5b10e082903e623b5310e492%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to