Improve issues managment
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 766
- Forks
- 51
- Avg merge
- 16d 14h
- Merged PRs (30d)
- 1
Description
For these I propose the following:
- Set up issue templates for bugs, enchantments, new game support, etc.
- Improve labels.
- Create labels for each project / area.
- Ex: "Area: Loader", "Area: Updater", "Area: Configure (Legacy)", "Area: Configure (WPF)"
- Perhaps separate some of these areas to their own repo and use them as submodules in the main repo?
- Reducing the size and turning them into digestible units highly likely to improve new developer experience.
- Create labels for an estimated size of workload.
- Ex: "Size: S", "Size: M", "Size: L"
- Create labels for each project / area.
- For stale issues, if it cannot be reproduced reach out to issuer. If it cannot be worked on, close issue with "wontfix" or perhaps a "stale".
- Don't forget assignments exist!
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 repository's GitHub issue settings, existing templates, labels, open issues, and assignment practices. Define a bounded set of workflow changes and acceptance criteria for templates, area and size labels, stale-issue handling, and assignments; completion should be verified in the repository settings and issue list.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100