Expected content of contributions for regional locales
Open
Nobody has claimed this yet.
community
feature
P3
- Dominant language
- JavaScript
- Stars
- 18.3k
- Forks
- 2k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 28
Description
Follow-up on #2991
Was there ever a conclusion reached on this topic? If I were to make a PR for a regional locale, should I make it a full locale or should it only include the necessary differences from the parent?
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 prior discussion in #2991 and the repository's current guidance for adding regional locales. Document the settled expectation for full locales versus parent-locale differences, with a clear rule contributors can follow.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, localization
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100