-
Notifications
You must be signed in to change notification settings - Fork 213
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.
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
Roadmap project: OpenTelemetry Collector v1 #1887
base: main
Are you sure you want to change the base?
Conversation
Closes open-telemetry#1861 Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a few copyedits, see inline comments.
* @open-telemetry/docs-maintainers | ||
* @open-telemetry/docs-approvers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doc approvers include maintainers, so I don't think that we need to specify both (/cc @svrnm):
* @open-telemetry/docs-maintainers | |
* @open-telemetry/docs-approvers | |
* @open-telemetry/docs-approvers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd still list them both, to make the intention explicit.
@open-telemetry/docs-approvers @austinlparker - we run into the topic of visibility / discoverability. I'd love to see these forward-looking pages hosted on the website, possibly under https://opentelemetry.io/community: |
Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Closes #1971
Signed-off-by: Juraci Paixão Kröhling juraci@kroehling.de