Closed
Bug 947823
Opened 11 years ago
Closed 11 years ago
Replace gender-specific pronouns with gender-neutral pronouns
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Bugzilla
Bugzilla-General
Tracking
()
RESOLVED
FIXED
Bugzilla 5.0
People
(Reporter: charlie, Assigned: charlie)
Details
Attachments
(1 file, 1 obsolete file)
33.16 KB,
patch
|
gerv
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
Steps to reproduce:
Downloaded BugZilla source, opened show_bug.cgi.
Actual results:
Noticed the use of 'he' to refer to the user, noticed other examples of gender specific pronouns in internal and external documentation throughout the codebase.
Expected results:
Internal and external documentation should only use gender-neutral pronouns.
Updated•11 years ago
|
Attachment #8344505 -
Attachment is patch: true
Attachment #8344505 -
Attachment mime type: text/x-patch → text/plain
Attachment #8344505 -
Flags: review?(gerv)
Comment 1•11 years ago
|
||
Comment on attachment 8344505 [details] [diff] [review]
bugzilla-pronouns.diff
Hi Charlie,
I'm interested: did you make this patch manually, or do you have a script of some sort? If a script, how does it know what pronoun is appropriate in what instance?
If we are going to make this change, consistency is valuable. Did you attempt to change every instance, or just a selection?
I have no objection to using gender-neutral language where no meaning is lost; however, we are currently attempting to rejig our docs into a new format in bug 912064 (the wheels of review are grinding slowly...), so now is not a great moment for anyone to be patching them.
The same issue doesn't apply to the code, so if you were to make a patch for only code files (that's everything outside the docs directory) that would not get held up for that reason.
Gerv
Attachment #8344505 -
Flags: review?(gerv) → review-
Assignee | ||
Comment 2•11 years ago
|
||
Gerv: I'll admit I created this patch by hand. I attempted to change every instance of he, him, his, she, and her I could find.
I'm happy to revise the patch to only change code if you're not in a position to take documentation patches at the moment. It would be great to see the documentation eventually changed to use gender-neutral pronouns though.
Assignee | ||
Comment 3•11 years ago
|
||
Comment 4•11 years ago
|
||
Comment on attachment 8345691 [details] [diff] [review]
bugzilla-pronouns-v2.diff
r=gerv.
Gerv
Attachment #8345691 -
Flags: review+
Updated•11 years ago
|
Flags: approval?
![]() |
||
Updated•11 years ago
|
Flags: approval? → approval+
![]() |
||
Updated•11 years ago
|
Attachment #8344505 -
Attachment is obsolete: true
![]() |
||
Updated•11 years ago
|
Assignee: general → charlie
Target Milestone: --- → Bugzilla 5.0
![]() |
||
Updated•11 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 5•11 years ago
|
||
I've started a discussion on the Bugzilla developers list (mozilla.dev.apps.bugzilla) about the policy implications of this patch.
Gerv
Updated•11 years ago
|
Flags: approval+
Just an opinion, using singular "they" can in some instances be ambiguous as to if it is referring to the singular person or multiple people. (I seem to recall getting corrected by a grade school grammar teacher for using "they" too, maybe that is the basis of my opinion. :-) )
Instead, I prefer myself to use "his or her" or "the person's".
For example, the following statement:
> Logs out the specified user (invalidating all their sessions), taking a
could also be written:
> Logs out the specified user (invalidating all the user's sessions), taking a
or:
> Logs out the specified user (invalidating all the person's sessions), taking a
Or even:
> Logs out the specified user (invalidating all his or her sessions), taking a
As a preference, I like to recognize that the masculine pronouns have been used for centuries to refer to all people, regardless of gender. Unfortunately though, when used in legal documents, exclusionist types have used the ambiguity to exclude the other gender. Good thing Bugzilla Docs don't represent any legal guidelines or rules.
![]() |
||
Comment 7•11 years ago
|
||
(In reply to Gervase Markham [:gerv] from comment #5)
> I've started a discussion on the Bugzilla developers list
> (mozilla.dev.apps.bugzilla) about the policy implications of this patch.
I haven't seen any objection on the mailing list about this. Time to commit it?
Flags: needinfo?(gerv)
Comment 8•11 years ago
|
||
Sorry; busy over the holidays. Will address this bug tomorrow.
Gerv
Flags: needinfo?(gerv)
Comment 9•11 years ago
|
||
I believe we need commit approval. (If not, someone point me at the current tree rules.)
Gerv
Flags: approval?
Comment 10•11 years ago
|
||
Go for it. Technically "he" and "his" are gender neutral, but since there is no specific masculine pronoun to complement it in English and there IS a feminine one, it gets treated as if it were masculine most places these days.
It doesn't help that everyone teaches their kids "girls are her, boys are him" when they're little, so it gets cemented in really early.
In the interest of gender-neutralness probably best to avoid the ambiguity. :)
Flags: approval? → approval+
Comment 11•11 years ago
|
||
Comment on attachment 8345691 [details] [diff] [review]
bugzilla-pronouns-v2.diff
Actually, this patch is stale and no longer commits cleanly. The fixes should be obvious (some of the surrounding html got modified since this was posted), so approval stands, commit as soon as it's cleaned up.
Comment 12•11 years ago
|
||
Charlie: could you do a patch refresh?
Thanks,
Gerv
![]() |
||
Comment 13•11 years ago
|
||
Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/trunk/
modified Bugzilla.pm
modified buglist.cgi
modified describecomponents.cgi
modified editflagtypes.cgi
modified importxml.pl
modified request.cgi
modified show_bug.cgi
modified token.cgi
modified userprefs.cgi
modified Bugzilla/Attachment.pm
modified Bugzilla/Auth.pm
modified Bugzilla/Bug.pm
modified Bugzilla/Constants.pm
modified Bugzilla/Flag.pm
modified Bugzilla/Hook.pm
modified Bugzilla/Migrate.pm
modified Bugzilla/Product.pm
modified Bugzilla/Search.pm
modified Bugzilla/Token.pm
modified Bugzilla/User.pm
modified Bugzilla/Util.pm
modified Bugzilla/Auth/Verify/LDAP.pm
modified Bugzilla/Install/DB.pm
modified Bugzilla/Search/Quicksearch.pm
modified Bugzilla/WebService/Bug.pm
modified Bugzilla/WebService/User.pm
modified extensions/Example/Extension.pm
modified template/en/default/welcome-admin.html.tmpl
modified template/en/default/admin/confirm-action.html.tmpl
modified template/en/default/admin/params/auth.html.tmpl
modified template/en/default/admin/params/query.html.tmpl
modified template/en/default/bug/process/confirm-duplicate.html.tmpl
modified template/en/default/pages/quicksearch.html.tmpl
modified template/en/default/pages/release-notes.html.tmpl
modified template/en/default/pages/release-notes3.html.tmpl
Committed revision 8936.
Severity: normal → enhancement
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•