Project-MONAI / Project-MONAI/MONAILabel
Clarify the process how we want to work/prioritize with the issues
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 891
- Forks
- 269
- Avg merge
- 15h 41m
- Merged PRs (30d)
- 1
Description
Every body can come up with ideas. It can be very concrete bugs/task but also vague ideas the need further discussion and clarification in the community. Aim is not to prefilter the problem space or solution space to early.
Open ideas/questions:
- How do we determin and then also encode, which issues is scheduled when or its importance/priority? Are we e.g. looking each WG meeting at new uncategorized issues?
- Do we have something like a commenting phase or adopt a lean version of process other projects do for framework or language evolvement?
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 reading the issue's two open questions and reviewing how WG meetings currently handle uncategorized issues. Compare that practice with the proposed commenting or lightweight process, then document an agreed prioritization workflow and ownership.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100