-
Notifications
You must be signed in to change notification settings - Fork 244
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
REQUEST: New opentelemetry-docs-examples repository #1474
Comments
cc @carlosalberto can someone on the TC with permissions take a look at this? |
cc @open-telemetry/technical-committee |
Would it work if we start by having these examples in a dedicated branch under the same (github.com/open-telemetry/opentelemetry.io) repo? |
We wanted to have a clean separation of docs & the example codes to not mix workflows, etc. I don't think that a dedicated branch is helping with that. |
@svrnm this fell through the cracks. Is it is still actual? |
I think right now we are following a different approach, let me close that issue |
Affected Repository
https://github.com/open-telemetry/opentelemetry-docs-examples
Requested changes
Request to add new repository with proposed name
opentelemetry-docs-examples
Purpose
During the last Comms SIG call we talked about our current effort to standardize the "Getting Started" across languages using the "same application" (see open-telemetry/opentelemetry.io#2623). Eventually this sample should be used across all the docs. We want to make the source code of these applications (uninstrumented & instrumented) available outside of the docs markdown files for a few reasons:
We have discussed a few alternatives to the above but agreed that a separate repository provides the best option:
examples/
folder, so hosting the app there would be possible. Doing that creates a need of the SIG maintainers to go through all the changes, creates a need to distinguish that sample app from others, we spread out common logic across multiple repositories (building the containers, CI checks, ...)Expected Duration
Potentially permanent
Repository Maintainers
cc @cartermp @austinlparker @chalin
The text was updated successfully, but these errors were encountered: