You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: issue-management.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,3 +68,18 @@ Many SIGs track work in the specification repo that is outside of the triage pro
68
68
These issues, which may be created by a SIG or just assigned to them, should be added to the SIG's project board and given the label `sig-issue`.
69
69
If an issue is labeled as a `sig-issue`, it is the responsibility of the SIG to prioritize
70
70
the issue appropriately, and ensure it is completed or closed as won't fix.
71
+
72
+
## Issues blocking implementation
73
+
74
+
SIGs that implement and document the specification in their respective language may run into issues with the specification,
75
+
that block their implementation, or they may want to request a specification change related to an implementation change. To
76
+
highlight issues of that kind SIG maintainers can request a `maintainer-request` label being added
77
+
to an issue, if the following conditions are met:
78
+
79
+
* the issue description or a comment by the maintainer points to at least one issue in an implementation repo, of which they are a maintainer.
80
+
* the maintainer summarizes in the issue description or in a comment to an existing issue, what is blocking them and/or what is required from their point of view to make progress.
81
+
* the maintainer tags all other maintainers of the implementation repo in the issue description or their comment (@open-telemetry/<sig>-maintainers). No action from the other maintainers is expected, except they disagree with
82
+
the request of this issue being tagged as `maintainer-request`.
83
+
* they will share the issue with all other SIGs either via the [Maintainer Meeting](https://github.com/open-telemetry/community?tab=readme-ov-file#cross-cutting-sigs) or via a message to [#otel-maintainers](https://cloud-native.slack.com/archives/C01NJ7V1KRC) on [CNCF slack](https://slack.cncf.io). This way maintainers of other implementation SIGs can comment if they have the same request.
84
+
85
+
A triager will add the `maintainer-request` label to the issue if those conditions are met.
0 commit comments