Node.js Bug Tracker Project
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Github has a Projects feature, utilized by Node.js for managing feature requests, yet it can also serve for tracking bugs.
I made a demonstration at https://github.com/orgs/nodejs/projects/10/views/1. If adopted, the process would look like:
- Creation of an issue using the Bug Report template -> Automatically assigned to 'Unconfirmed Bug'
- Confirmation of the bug's existence by a Project Member -> Manual relocation to 'Confirmed Bug' (instead of applying the
confirmed-buglabel) - Resolution of the bug by a Project Member, followed by relocation to 'fixed' within the project -> Automatic closure of the Bug
- In case of bug recurrence, a Project Member reopens the issue -> Bug is reverted to 'Confirmed Bug' (Automatically)
Among others. This feature intends to simplify the process of organizing issue status in multiple dimensions. Currently, the project groups by status (Columns) and priority (Rows).
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 the linked GitHub Projects documentation and the Node.js project 10 demonstration, then review the Bug Report template and the current confirmed-bug workflow. Done means agreeing on and implementing the proposed status transitions, including confirmation, automatic closure when fixed, and reopening behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100