Document Scope
Open
Nobody has claimed this yet.
docs
- Dominant language
- Less
- Stars
- 680
- Forks
- 442
- PR merge metrics
- No merged PRs in 30d
Description
Document the key scoping rules.
(Creating this generic ticket just to be able to redirect here all rather specific and/or too minor scoping rules tips/questions/examples.. E.g. #21, #387, #437 etc. etc.).
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
The issue names no documentation files, tests, or entry points; start by reviewing the linked scoping discussions and examples, including #21, #387, and #437. Done would mean the key scoping rules are documented and the specific or minor scoping questions can be redirected to this page.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100