New PEP Editors?
Open
Nobody has claimed this yet.
meta
- Dominant language
- reStructuredText
- Stars
- 5k
- Forks
- 1.8k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 25
Description
Some PEPs aren't being reviewed as quickly as we'd like and can sit waiting for review before merge for too long. This holds up PEP discussion, which can be challenging enough for authors.
@StanFromIreland and @ZeroIntensity have volunteered to join the PEP Editor team.
What do @python/pep-editors think?
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 with issue #5080 and the PEP Editor team’s discussion about the proposed volunteers. Review how PEP editor membership is handled in this repository, if documented in the surrounding project materials. Done means the team has reached and recorded a decision about the proposed additions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100