Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Triage Process] Allow SIG maintainers to express their requirements #4229

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

[Triage Process] Allow SIG maintainers to express their requirements #4229

Changes from 6 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
d8dabfc
[Triage Process] Allow SIG maintainers to express their requirements
svrnm Sep 26, 2024
302de2d
Update issue-management.md
svrnm Oct 10, 2024
e0fed9f
Merge branch 'main' into triage-process-maintainer-requirements
svrnm Oct 10, 2024
20cef8e
apply suggested changes
svrnm Oct 10, 2024
6407e72
Update issue-management.md
svrnm Oct 18, 2024
709a298
add line break to end of file
svrnm Oct 23, 2024
3cc1b69
Merge branch 'main' into triage-process-maintainer-requirements
svrnm Nov 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions issue-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,3 +59,18 @@ Many SIGs track work in the specification repo that is outside of the triage pro
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`.
If an issue is labeled as a `sig-issue`, it is the responsibility of the SIG to prioritize
the issue appropriately, and ensure it is completed or closed as won't fix.

## Issues blocking implementation

SIGs that implement and document the specification in their respective language may run into issues with the specification,
that block their implementation, or they may want to request a specification change related to an implementation change. To
highlight issues of that kind SIG maintainers can request a `maintainer-request` label being added
jack-berg marked this conversation as resolved.
Show resolved Hide resolved
to an issue, if the following conditions are met:

* 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.
svrnm marked this conversation as resolved.
Show resolved Hide resolved
* 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.
* 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
the request of this issue being tagged as `maintainer-request`.
* 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.

A triager will add the `maintainer-request` label to the issue if those conditions are met.
Loading