#22707: Database-related terminology in docs is misleading
--------------------------------------+--------------------
Reporter: Meira | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
All occurences of "master/slave" were recently replaced with
"leader/follower" (https://github.com/django/django/pull/2692), then with
"primary/replica"
(https://github.com/django/django/commit/beec05686ccc3bee8461f9a5a02c607a02352ae1).
This new terminology is vague, ill-advised, and '''very misleading.'''
Django is a server-side framework with the goal of making Pythonistas'
life sweet. By no means this requires reforming old and widely accepted
database terminology, or feeding fat internet trolls like Feminist
Software Foundation.
Let's look at the famous Zen of Python:
* Special cases aren't special enough to break the rules.
* Although practicality beats purity.
* There should be one-- and preferably only one --obvious way to do it.
And, above all:
* '''Explicit is better than implicit.'''
Here are four reasons, baked in the core of the language, as well as in
the core or the developers' hearts, for why changing this '''clear,
concise and immediately recognized''' terminology is a bad idea.
This terminology has been used for a long time, and by no means those
purely technical terms carry racially charged meanings to users, neither
are they offending in any other way.
This patch replaces all occurrences of "primary/replica" with the good old
"master/slave" together with now unnecessary comments like "referred to as
master/slave by some databases".
--
Ticket URL: <https://code.djangoproject.com/ticket/22707>
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/048.9e6d0ae182d65422ea08fedaca6c524c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
