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

In-Progress: Inclusive Naming Checklist #395

Closed
5 tasks
Nebrethar opened this issue Jan 18, 2022 · 17 comments
Closed
5 tasks

In-Progress: Inclusive Naming Checklist #395

Nebrethar opened this issue Jan 18, 2022 · 17 comments
Labels
I: contributor experience Quality-of-life improvements or changes to project contribution processes or resources I: good first issue Good for newcomers I: help wanted Extra attention is needed T: improvement Improves on something that already exists T: revising metric Previously released metric that is being revisited and updated

Comments

@Nebrethar
Copy link
Contributor

This list was informed by the Inclusive Naming Initiative to improve the language used in our metrics and documentation. It can be used to assess any documentation for inclusive naming in the CHAOSS GitHub organization.

Hey folks! Here is the first draft of some naming to review in our metrics and documentation. Will discuss in 1/18/2022 community call. I will try to keep up with any new terms added to the Inclusive Naming lists. Please check the links for additional context.

Each checkbox indicates a term that we may find and will want to replace. Please check the box only if the presented word is no longer present in the document.

@jwflory jwflory added I: contributor experience Quality-of-life improvements or changes to project contribution processes or resources I: help wanted Extra attention is needed T: revising metric Previously released metric that is being revisited and updated T: improvement Improves on something that already exists labels Feb 2, 2022
@Nebrethar
Copy link
Contributor Author

From DEI WG: This would be a great GSoC Idea

@germonprez
Copy link
Contributor

germonprez commented Mar 2, 2022

Now this is a great idea for GSoD. @sgoggins is doing the org app. for GSoD --> Due by March 25th.

@germonprez
Copy link
Contributor

@Nebrethar is this related to your other issue?

@germonprez
Copy link
Contributor

germonprez commented Jun 1, 2022

Could be part of the review and revisions process -- Proposal: include in the checklist.

@Nebrethar Nebrethar added the I: good first issue Good for newcomers label Jun 1, 2022
@germonprez
Copy link
Contributor

Also, the list could provide a good first issue for people looking to help with improving CHAOSS documentation.

@ElizabethN
Copy link
Member

We discussed this in today's community meeting - we have some thoughts on next steps for incorporating this more into the CHAOSS metrics, which we will bring to the community meeting.

@ElizabethN
Copy link
Member

@germonprez do you think we could add the consideration for inclusive naming into our new issue template as just a bullet point for folks to be mindful of when releasing a new metric?

@germonprez
Copy link
Contributor

@ElizabethN
Copy link
Member

Website checked today during the DEI working group call (yay!) 🎉
Still to be checked: software (augur, grimoirelab, slackbots, badging bots)

@sgoggins
Copy link
Member

Augur is updated.

@germonprez
Copy link
Contributor

Quick check on bots and okay

@germonprez
Copy link
Contributor

There are some issues when the term is a programming keyword (e.g., abort).

@germonprez
Copy link
Contributor

If people have an interest, please help out by identifying where these Tier 1 words may be present in the CHAOSS project.

@peculiaruc
Copy link
Contributor

peculiaruc commented Jul 25, 2024

Tier 1 Words

  1. abort
  2. blackhat
  3. cripple
  4. master
  5. master-slave
  6. Tribe
  7. whitelist

@ElizabethN
Copy link
Member

@peculiaruc just doing a little cleanup on some repos today, and I'm wondering if I can close this issue. I think we made all the changes we could that were straightforward. I think the rest of them will require quite a bit of work and discussion. is it ok if I close this issue?

@peculiaruc
Copy link
Contributor

Yes, we can close it now.

@ElizabethN
Copy link
Member

Thank you so much @peculiaruc for your work on this! 🌟

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: contributor experience Quality-of-life improvements or changes to project contribution processes or resources I: good first issue Good for newcomers I: help wanted Extra attention is needed T: improvement Improves on something that already exists T: revising metric Previously released metric that is being revisited and updated
Projects
None yet
Development

No branches or pull requests

6 participants