Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove divisive terminology from project #645

Closed
nothingismagick opened this issue Jun 9, 2020 · 7 comments
Closed

Remove divisive terminology from project #645

nothingismagick opened this issue Jun 9, 2020 · 7 comments

Comments

@nothingismagick
Copy link
Sponsor Member

Is your feature request related to a problem? Please describe.
There are several occurrences of potentially divisive words in our projects, which are unfortunately parts of the common parlance in engineering. We have discussed this in the team chat several times, and I am now opening this issue so we can discuss resolution.

There are three locations where we are aware of this:

  • "master" branch (git structure)
  • "whitelist" (tauri.conf.json)
  • "kamikaze" (docs - pattern)

There may be more that I am overlooking.

Describe the solution you'd like
I would like to find other words that we can use in order to be more intentionally inclusive.

Suggestions

  • master => release (because this is how we are using that branch as a reflection of the code at a particular state)
  • whitelist => permitlist / denylist (remove color from quality assertion)
  • kamikaze => one-timer (remove glorification of violence / suicide)

Describe alternatives you've considered
Doing nothing and ignoring complicity is actually how fascism becomes powerful.

Additional context
I think in the global social context of the current protests and endemic societal racism, it is important to consider the words we use - and how they can internally weaponise mental states. Remaining ignorant and doing nothing about this is, in fact, in contrast with our very own Code of Conduct, and something that we should constantly be vigilant about.

Personally, I feel that GitHub and Git itself should reconsider "creating" new repositories with "Master" as the default base branch. @devonzuegel ?

@awkj

This comment has been minimized.

@rajivshah3
Copy link
Member

While I understand the rationale behind renaming these terms, I'm afraid of discrepancies between projects regarding their new terminology. For this reason, I think that whitelist/blacklist should be renamed to allowlist/denylist, as proposed for Pi-Hole. This has already been done for Rails and GitLab.

As a replacement for "kamikaze", I think "lockdown" might be a better name to advertise the high security rating of that pattern.

@nothingismagick
Copy link
Sponsor Member Author

Great suggestions @rajivshah3

@jbolda
Copy link
Member

jbolda commented Jul 4, 2020

Branch terminology has been updated in #744.

@lucasfernog
Copy link
Member

@nothingismagick we need to find a good time to rename "whitelist" to "permlist" (breaking change). Maybe right now?

@nothingismagick
Copy link
Sponsor Member Author

Yeah, now is nice and quiet.

lucasfernog added a commit that referenced this issue Jul 19, 2020
* refactor(tauri) rename `whitelist` to `allowlist`, ref #645

* chore(changes) add changefile
@nothingismagick
Copy link
Sponsor Member Author

Thanks everybody.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants