[chore] diagram defining different states for issues #36975
Conversation
Co-authored-by: Ziqi Zhao <[email protected]>
|
Add a screenshot for current version in case other approvers have interest in this. |
|
ping @open-telemetry/collector-contrib-approvers for review |
| n6 -- Yes --> n7["Valid issue and to be fixed <br>by a codeowner"] | ||
| n6 -- No --> n8 | ||
| n7 --> n9 | ||
| n8 --> n9 |
There was a problem hiding this comment.
There should be some step between help-wanted and closed
| n2 -- Yes --> n3 | ||
| n2 -- No/Need more details --> n4 | ||
| n2 -- Invalid configuration/alternative available --> n9 | ||
| n3 -- Invalid Issue --> n9 |
There was a problem hiding this comment.
may be worth giving some examples on invalid issues
|
|
||
| ```mermaid | ||
| flowchart TD | ||
| subgraph graph1["**needs-triage**"] |
There was a problem hiding this comment.
I don't feel like the subgraph adds a lot to it, I think probably removing it would make the diagram a bit less intimidating. What do you think? Is there anything we would lose without it?
| n2 -- No/Need more details --> n4 | ||
| n2 -- Invalid configuration/alternative available --> n9 | ||
| n3 -- Invalid Issue --> n9 | ||
| n3 -- Valid Issue --> n6["Codeowner has time<br>to fix it?"] |
There was a problem hiding this comment.
I feel like the criteria here would be something more like "issue is suitable for non-codeowners"? My expectation is that for bugs at least, if someone signs up as a code owner is because they have time to fix the bug
Description
See #36677
Closes #36677