[DOC] Review guidelines: When to resolve comments
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Locate the review guidelines documentation and read the surrounding process guidance first. Update it to explain when comments should be resolved and who resolves them; the work is done when both questions are answered clearly.
Written by the indexing model from the issue text.
Description
We need to provide a bit more info on the process:
- When to resolve?
- Who resolves?
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from pyfar/gallery
-
maintenance
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Add documentation on GitHub tokens and secrets to contribution guidelinesMay be free again @hoyer-a claimed this 45 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
AI Coding AgentsPossibly taken @hoyer-a claimed this 1 day ago. Open
-
Integrate Github Apps as a longterm replacement for Personal Access TokensMay be free again @hoyer-a claimed this 45 days ago, and no pull request is open. OpenCI enhancement
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
cal-itp/data-infra#5887 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ranacseruet/vaice#139 ·
Maintainers usually reply within 1 day
-
numpy.bytes_ attributes are recorded as a truncated repr instead of their contentPossibly taken @JoeyTan21 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
batocera-linux/batocera.linux#17423 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100