Update CODEOWNERS to reflect spec sponsor role #4170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cijothomas
approved these changes
Jul 30, 2024
pellared
approved these changes
Jul 31, 2024
jmacd
approved these changes
Jul 31, 2024
trask
reviewed
Jul 31, 2024
Co-authored-by: Trask Stalnaker <[email protected]>
|
Also opened open-telemetry/opentelemetry-proto#572 to reflect role changes in the proto repository. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
PR is merged and I've completed the followup steps listed in the PR description. Need to followup with the corresponding proto PR: open-telemetry/opentelemetry-proto#572 |
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
Followup to open-telemetry/community#2070 Should be merged in lockstep with open-telemetry/opentelemetry-proto#572 Upon merging, I will: - Rename [spec-approvers](https://github.com/orgs/open-telemetry/teams/specs-approvers) to `spec-sponsors` - Add all [current sponsors](https://github.com/open-telemetry/community/blob/main/community-members.md#specifications-and-proto) to `spec-sponsors` - Delete [spec-metrics-approvers](https://github.com/orgs/open-telemetry/teams/specs-metrics-approvers), [spec-trace-approvers](https://github.com/orgs/open-telemetry/teams/specs-trace-approvers), [spec-logs-approvers](https://github.com/orgs/open-telemetry/teams/specs-logs-approvers) Note, there are still references to spec approvers in [CONTRIBUTING.md](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CONTRIBUTING.md). As discussed in open-telemetry#3821 there are a variety of issues with the spec issue management process, including consistency. I'm not trying to solve all of them in this PR - rather, I want to make incremental progress and reflect a decision that was already made about the spec sponsor role. --------- Co-authored-by: Trask Stalnaker <[email protected]> Co-authored-by: Robert Pająk <[email protected]> Co-authored-by: Cijo Thomas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Followup to open-telemetry/community#2070
Should be merged in lockstep with open-telemetry/opentelemetry-proto#572
Upon merging, I will:
spec-sponsorsspec-sponsorsNote, there are still references to spec approvers in CONTRIBUTING.md. As discussed in #3821 there are a variety of issues with the spec issue management process, including consistency. I'm not trying to solve all of them in this PR - rather, I want to make incremental progress and reflect a decision that was already made about the spec sponsor role.