InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Using inclusive language in our patterns to make sure that everybody feels welcome
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
I saw in another project that they were automatically checking the writing for inclusive language using the in-solidarity-bot.
That seems like a great idea, and something that we should apply to our patterns to, in order to make sure that everybody feels welcome and motivated to contribute.
I don't know exactly how these work but this is what I found in the other project:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the in-solidarity-bot repository and the linked SAP project check example to understand the proposed workflow. Then identify how this repository stores and validates its patterns; done means the patterns are covered by an agreed automated inclusive-language check.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100