Strategy to improve `Service Attention` issues management
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 115
Description
Currently the language repos have issues opened and classified as `Service Attention`. In some cases this issues don't get the neccesary traction. What will be the best way to improve this?
- Should issues be moved to the REST API repo? open an ICM?
- How will the service team will be notified about them?
- Should the service team resolve them or have a target in order to be able to publish their next RESt API version?
- etc...
Contributor guide
Research direction
The issue does not name files, tests, or an implementation entry point. Start by reviewing how Service Attention issues are classified in the language repositories, then compare the REST API repository and ICM paths mentioned here. Done means documenting an agreed ownership, notification, and release-target workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100