{"id":13631274,"url":"https://github.com/s0/eradicate-exclusive-tech-terminology","last_synced_at":"2026-02-16T15:03:50.923Z","repository":{"id":72164655,"uuid":"271910274","full_name":"s0/eradicate-exclusive-tech-terminology","owner":"s0","description":"Let's Eradicate Exclusive Terminology in Tech! :fist_raised:","archived":false,"fork":false,"pushed_at":"2020-07-23T17:41:17.000Z","size":42,"stargazers_count":39,"open_issues_count":4,"forks_count":10,"subscribers_count":4,"default_branch":"main","last_synced_at":"2026-01-15T12:42:13.863Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/s0.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":null,"code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-06-12T23:56:06.000Z","updated_at":"2025-10-13T19:14:45.000Z","dependencies_parsed_at":null,"dependency_job_id":"a0537c25-fd36-43a6-b0d3-c891a55fd05f","html_url":"https://github.com/s0/eradicate-exclusive-tech-terminology","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/s0/eradicate-exclusive-tech-terminology","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/s0%2Feradicate-exclusive-tech-terminology","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/s0%2Feradicate-exclusive-tech-terminology/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/s0%2Feradicate-exclusive-tech-terminology/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/s0%2Feradicate-exclusive-tech-terminology/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/s0","download_url":"https://codeload.github.com/s0/eradicate-exclusive-tech-terminology/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/s0%2Feradicate-exclusive-tech-terminology/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29510525,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-16T09:05:14.864Z","status":"ssl_error","status_checked_at":"2026-02-16T08:55:59.364Z","response_time":115,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-01T22:02:18.672Z","updated_at":"2026-02-16T15:03:50.906Z","avatar_url":"https://github.com/s0.png","language":null,"funding_links":[],"categories":["Others"],"sub_categories":[],"readme":"# Let's Eradicate Exclusive Terminology in Tech! :fist:\n\n[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg)](CODE_OF_CONDUCT.md)\n\n\u003c!-- PLEASE USE SEMANTIC LINE BREAKS IN THIS DOCUMENT: https://sembr.org/ --\u003e\n\nThere are a number of words that we use\nin software, hardware, engineering etc...\nthat can be interpreted with racist, sexist, violent or bigoted undertones.\nAnd even if the original intent of these words are a completely different story,\nencountering these terms without further context\ncan be harmful, offensive or triggering,\nand have a negative impact on minorities\nand other people with negative associations with the terms.\n\nIf we wish to be truly inclusive as an industry,\nand let's face it, we know we've struggled...\nwe should do everything we can to change these terms everywhere we use them.\n\nAs Clockwork say [in their blog post](https://www.clockwork.com/news/creating-inclusive-naming-conventions-in-technology/):\n\n\u003e It’s not hard to see that associating positive things with “white”\n\u003e (like whitelisted) and negative things with “black” (like blacklisted) is,\n\u003e at worst, deeply offensive and at best entirely unnecessary.\n\u003e So let’s change it.\n\n## [Pledge](PLEDGE.md)\n\nIf you would like to publically indicate your support of this initiative,\nand take a pledge to commit to replacing exclusive terminology wherever you can,\nplease feel free to submit a pull request\nadding yourself to [this document](PLEDGE.md).\n\nAny contributions are subject to our [Contributing document](CONTRIBUTING.md).\n\n## Terms\n\n### `master`\n\nUsed as the default branch in Git along with many other\n\n**Alternatives:**\n\n* `primary`\n* `main`\n* `default`\n* `develop` (git)\n* `trunk` (git)\n* `stable` (git)\n\n**Where are these changes happening?**\n\n* **Git:**\n  There is movement within the Git ecosystem\n  to replace the default branch name `master` with alternatives.\n  There is an [open issue on GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/221164),\n  and [Nat Friedman has said on twitter](https://twitter.com/natfriedman/status/1271253144442253312)\n  that GitHub is working on renaming the default branch.\n  See the [github/renaming](https://github.com/github/renaming) repository for more info.\n\n\nBeyond this, it is already possible for you to change the default branch\nof your repostories on GitHub\n(and most other Git platforms).\nSimply push a branch with the new name you would like,\nand change repository settings.\nIf you have a lot of GitHub repositories to deal with,\n[here is a tool to do it automatically using the API](https://github.com/lf-/splice_graft).\n\n### `master` / `slave`\n\n**Alternatives:**\n\nMany of these alternatives provide an even clearer\nand more accurate representation\nof the relationship between different entities in a system:\n\n* `primary` / `secondary`\n* `leader` / `follower`\n* `active` / `standby`, `failover`\n* `primary` / `replica`\n* `writer` / `reader`\n* `coordinator`, `conductor`, `manager` / `worker`, `helper`\n* `parent` / `child`, `helper`\n\n**Where are these changes happening?**\n\n* [Python](https://bugs.python.org/issue34605)\n* [Go](https://go-review.googlesource.com/c/go/+/236857/)\n\n### `master` / `detail` (UI Pattern)\n\n**Alternatives:**\n`index` / `detail`\n\n### `male` / `female` (connectors, fasteners)\n\n**Alternatives:**\n`plug` / `socket`\n`plug` / `jack`\n\n### `blacklist` / `whitelist`\n\n**Alternatives:**\n\n* `blocklist`, `denylist` / `allowlist`, `permitlist`\n\n**Where are these changes happening?**\n\n* [Ruby on Rails](https://github.com/rails/rails/issues/33677)\n* [Go](https://go-review.googlesource.com/c/go/+/236857/)\n* [Angular](https://github.com/angular/angular/pull/28529)\n* [Chromium](https://bugs.chromium.org/p/chromium/issues/detail?id=981129)\n\n### `man in the middle`\n\n**Alternatives:**\n\n* `meddler in the middle`, `monster in the middle`\n\n## FAQ\n\n### Does this really matter?\n\nIf you care about inclusivity... Yes.\n\n### But the origin of these terms aren't racist?\n\nThe original intent of the terms does not change the impact it has on someone\nwhen they see it without that context.\n\n### What about breaking changes?\n\nThat's what [Semantic Versioning](https://semver.org/) is for!\n\nIf you have an API that uses these terms in it,\nthen to fully adopt these changes,\nyou'll need to change your API.\nLike any breaking change,\nyou can depricate the old terms / symbols / parameters / etc...\nand then remove them in the next major version bump!\n\nWe've been known to bump major versions of software\nfor smaller changes than this,\nand this is totally worth it!\n\n## Resources / Posts\n\nYou may find the following resources useful,\nsome of them have helped inspire this document:\n\n* [IETF - Terminology, Power and Oppressive Language](https://tools.ietf.org/id/draft-knodel-terminology-00.html)\n* [Clockwork - Creating inclusive naming conventions in technology](https://www.clockwork.com/news/creating-inclusive-naming-conventions-in-technology/)\n\n## Social Media Posts\n\n* [Aug 2018 - @andrestaltz](https://twitter.com/andrestaltz/status/1030200563802230786)\n* [June 2020 - @leahculver](https://twitter.com/leahculver/status/1269109776983547904)\n\n## Contributions\n\nWe welcome Pull Requests that:\n\n* Sign the [pledge](PLEDGE.md).\n* Add additional terms that should be avoided, with alternatives offered.\n* Add examples of technical\n  (software, hardware, engineering, etc...)\n  projects or products\n  that have decided to make these changes.\n* Expand the FAQ or any other textual elements.\n\nPlease note that this project is released with a\n[Contributor Code of Conduct](CODE_OF_CONDUCT.md).\nBy participating in this project you agree to abide by its terms.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fs0%2Feradicate-exclusive-tech-terminology","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fs0%2Feradicate-exclusive-tech-terminology","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fs0%2Feradicate-exclusive-tech-terminology/lists"}