Newbie: Doc correction and contribution questions #3010
Unanswered
topher1120
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hi @topher1120 . You don't need to create an issue for a documentation PR, unless you think that issue will probably end up encompassing more than a single PR. That being said, you are totally free to create the issue if you think it will help foster discussion before the changes are made. There is no one dedicated to documentation. We would love contributions that make the documentation easier to understand, navigate, etc. Thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I'm pretty new to OpenTelemetry and it's been a very long time since I've contributed to open source. I'm hoping to help out, especially in documentation for the near future and would appreciate help understanding the day-to-day processes so I can help effectively.
To that end, I've found a correction in the existing documentation around the
sdk-extensions/autoconfigure
submodule that I'm hoping to make as my first contribution. Specifically, the description on the property otel.exporter.otlp.headers says multiple headers should be separated via semicolons. My OpenTelemetry vendor uses headers to pass information related to my account when traces are collected. In trying to configure this property, I realized that headers should actually be separated by commas. I've traced the source code to verify. (You can see usage inSpanExporterConfiguration
andMetricExporterConfiguration
.)Here's the set of process questions. I'm familiar with Git, but shaky on practical experience of PRs. First, should I create an issue for this item before submitting a PR? If I create an issue, how do I associate the PR with it? What's the general rule for this kind of thing?
Finally, as I work through setting up my application to use OpenTelemetry, I see a few areas within the Java projects that were initially confusing and I would like to work on clarifying those pages. Is there someone in the community more dedicated to documentation that I should chat with to understand the overall goals, style and plans for the documentation?
Thanks,
Chris
Beta Was this translation helpful? Give feedback.
All reactions