[ADMIN] CONTRIBUTORS WELCOME

[marcalff]

This issue lists areas that are good entry points to start contributing to opentelemetry-cpp.

For each issue, see the issue comments for details.

Functional

Typically, features touching a functional area requires to dive into the code, but do not need changes in the infrastructure, like CI, workflows, compilers, platforms, makefiles ...
This is a good opportunity to learn the C++ code itself. The size of the code affected varies by feature.

All signals

Typically, changes affecting all signals at once are using the same pattern, applied everywhere.
The change is limited in scope, but touches multiple parts.
This is a good opportunity to learn how to apply design or coding pattern to an existing code base.

• [SDK] Add simple scope configuration to Tracer, Meter, Logger #2641

Metrics signal

Typically, changes affecting the metrics signal are more involved on the functional part (time series, aggregation).
This is a good opportunity to understand in depth a component, with clear boundaries.

• [Metrics SDK] Add support for Exponential Histogram Aggregation #1391

Specific areas

Typically, features touching a specific area do not require to understand the whole code base, but only a well defined subset.
This is a good opportunity to learn the development process (git, PR, review, merge) as well as the affected code.

• [EXPORTER] optimize OTLP HTTP compression #2570
• Log SSL Connection Information #2250
• Support handling Retryable error for OTLP exporter (OTLP/gRPC and OTLP/HTTP) #2049
• W3C TraceContext compliance #74
• [BUILD] Enable SSL for curl in bazel build environment #2489
• [SDK] Support OTEL_SDK_DISABLED environment variable #1631

Code health

This area requires to change CI/CD scripts to improve the build process.
This is a very good opportunity to learn the github CI workflow, to implement new tooling.

Include-what-you-use

Iterative changes, to expand coverage to the entire code base.

• [Code health] include-what-you-use cleanup #2054

Clang-tidy

Iterative changes, to expand coverage to the entire code base.

• [Code health] clang-tidy cleanup #2053

Cpp-check

• [CI] Add a C++ static code analyser in the build #2297

Doxygen

• [CI] Add a doxygen build #1647

Test coverage

This area is a very good opportunity to learn docker to execute tests in a container environment.

• [TEST] Functional tests for OTLP GRPC MTLS export #2208
• Test example code in CI #454

Too late

Fixed already:

• [EXPORTER] exporter endpoint doesn't support ipv6 #3073
• [EXPORTER] Add optional configuration for prometheus exporter #2453
• ElasticSearch Exporter does not follow ECS guidelines and logging reference #3091

[github-actions]

This issue is available for anyone to work on. Make sure to reference this issue in your pull request.
✨ Thank you for your contribution! ✨

[brown-eric]

Hey, how can I help on this issue?

[ThomsonTan]

Hey, how can I help on this issue?

Could you please add comments on which issue you are interested? We can assign it to you to look into.

[brown-eric]

Which do you recommend? I'm new to this and would like to contribute for the first time! I have an assignment to do so and would love to be able to help this project #a little bit