Come up with a process to champion a PR on a Typelevel project
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 4
- Avg merge
- 1h 49m
- Merged PRs (30d)
- 2
Description
We were discussing the idea of championing a PR that should be approved.
Some ideas
- That person would research, and ensure running
- Describe why it should be approved
- Perhaps pair with someone as discussed with @Koroeskohr
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 discussion in issue #207 and the three proposed ideas about researching, explaining, and pairing on a PR. Define and agree on a championing process for Typelevel PRs, including what the champion does and what completion of the process means.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100