Assigning reviews
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
Dear all,
From now on, each PR in IC will be assigned a reviewer (by me). Reviewers may accept of decline (I will keep count of your yes and nos), but if accepted, review must proceed without delay. I will also specify a dead line for the review.
We are indeed accumulating huge TD and we need to start reducing it. Please help
Thanks to all
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 contains a review-process announcement but names no files, tests, or entry points to inspect. There is no concrete change or completion condition for a contributor to implement.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100