InnerSourceCommons / InnerSourceCommons/InnerSourceLearningPath
Adding references to further Patterns
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 47
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 5
Description
If there are other places in the learning path where it could we helpful to link to Patterns, how could one go about adding those? Is it that I would start with the English version, and if those changes get approved+merged, they are slowly ported into the translations over time?
Originally posted by @spier in https://github.com/InnerSourceCommons/InnerSourceLearningPath/issues/373#issuecomment-788122792
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 learning-path source and the existing English-to-translation workflow; the issue names no files or tests to use. Done would be clear contributor guidance on where to add Pattern references and how approved English changes reach translations.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100