Issue cleanup
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
I've been slowly tagging and cleaning up the issues in the past few days. You might have noticed the issue count has gone down from ~900 to <800. I'm mostly going from oldest to newest and closing stale issues that either have a solution, have no response, are not issues or are obviously too old to be relevant.
I've tagged a bunch issues with the out of life branch labels, that might not always have an immediate resolution:
Feel free check them (and your own old issues) and resolve them 🦭
I suppose the same thing is needed for PRs.
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 stale-issue search and review the release branch labels for 24.10 and older branches. The issue describes tagging and closing stale or resolved issues, but it does not define a bounded set of issues or a clear completion condition.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100