python / python/docs-community
Having a "fast path" for documentation contributions
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 55
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
This came up in the Python 3.10 release stream -- https://youtu.be/AHT2l3hcIJg?t=5700 for the exact timestamp of when this was proposed in the stream and discussed briefly -- and I noticed that no issue has been filed for this yet so... I'm doing it myself. 😅
I wasn't the person who proposed this, so... there's no bullet list items of what exactly this would be. :)
Contributor guide
No contributing guide indexed for this repository
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 watching the linked Python 3.10 release stream at the referenced timestamp and review the issue discussion. The proposal has no defined file, entry point, requirements, or completion criteria, so the first step is to clarify the intended fast path before implementation can be scoped.
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
- 20/100