InnerSourceCommons / InnerSourceCommons/InnerSourceLearningPath
Create a glossary for common InnerSource terms
Open
Nobody has claimed this yet.
Meta
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 47
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 5
Description
We should have a list of words with their definitions that we commonly use when talking about InnerSource. This glossary should come with translations to languages that we would like to translate to (read: where we have volunteers to do the translation)
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
Review the repository's existing learning-path content and any terminology or translation conventions before choosing where the glossary belongs. Define the terms, identify languages with available volunteers, and verify that the glossary includes definitions and translations for the selected languages.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, internationalization, localization
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100