Open Bug 1643799 Opened 2 months ago Updated 5 days ago

[meta] No derogatory language: Remove references to grandfather


(Firefox :: General, task)





(Reporter: jbauman, Assigned: jbauman)


(Depends on 1 open bug, Blocks 1 open bug)


(Keywords: meta)

In accordance with the "Derogatory Language" section of the Mozilla Community Participation Guidelines, instances of grandfather in the sense of the grandfather clause should be removed due to the term's racist origins and associations:

  1. The Racial History Of The 'Grandfather Clause'
  2. Words Matter: Why We Should Put an End to “Grandfathering”

This issue serves to identify the various places this terminology appears in our code/documentation/UX and will be blocked by whatever sub-issues are needed to address them and once complete prevent its reintroduction via automation.

Assignee: nobody → jbauman

Thanks for your attention to this!

The post above suggest "legacy" as a replacement. I wonder if "backwards-compatible" would be more appropriate for some of our usages?

Edit: I realized "grandfathered" describes the object while "backwards-compatible" describes the subject, so sentences would need to be reworded for that replacement to work. For variables that are named "grandfathered" e.g. referring to a CSS spec, "legacy" may work better, though it's a bit more vague.

Note that many instances of grandfather in mozilla-central are in third party code.

Good point, Mike. My initial thinking was to create individual dependent bugs to explore the possibility of getting those changed upstream if possible so that we're doing out best to eliminate all sources of harmful language without having it function as an impediment to making the changes to code we have sole authority over.

I think the first step is classifying all the instances that show up in this search:

Currently, of the 183 results (updated to account for the work in bug 1649312)

Third-party sources:

  1. intl/icu: 42 results
  2. gfx/harfbuzz: 13 results
  3. toolkit/crashreporter/google-breakpad: 2 results

Internal sources:

  3. (note added)
  4. js/src/builtin: 27 results
  5. mobile/android: 9 results
  6. security/ct: 3 results
  7. File names under js/src/tests: 8 results
  8. js/src/tests/non262: 8 results
  9. js/src/tests/test262: 58 results
  11. toolkit/components/extensions/test/xpcshell/test_ext_incognito.js: 5 results

"Grandfather", but not in the "grandfather clause" sense:

  8. testing/condprofile/condprof/scenarii/words.txt: 3 results

I'll start working my way through the internal sources and when I'm done with that will file issues with the external ones to see if they'd accept a patch. The usages that will likely be hardest to change are the references to the attribute defined for language tags here: In those cases I'd suggest adding a link back to this issue for context.

Hopefully the usages that aren't in the sense of the grandfather clause are self-explanatory and don't require any change. For the most part these are just word lists, but some are describing relative relationships of nodes. Those could be replaced with non-gendered language, but I'd say that belongs as part of a separate bug if we want to do that.

Depends on: 1649312
Depends on: 1658400
You need to log in before you can comment on or make changes to this bug.