opentelemetry-dotnet-instru.../docs/CONTRIBUTING.md

3.3 KiB

<p align="center"> <strong> <a href="https://github.com/open-telemetry/community#net-auto-instrumentation">Getting Involved<a/>   •   <a href="https://gitter.im/open-telemetry/opentelemetry-dotnet-auto-instr">Getting In Touch<a/> </strong> </p>

Getting Involved   •   Getting In Touch

Contributing Guide

We'd love your help!

The OpenTelemetry .NET Instrumentation special interest group (SIG) meets regularly. See the OpenTelemetry community repo for information on this and other SIGs.

See the public meeting notes for a summary description of past meetings. Join the meeting or get in touch on Gitter.

Even though, anybody can contribute, there are benefits of being a member of our community. See to the community membership document on how to become a Member, Approver and Maintainer.

Report a bug or requesting feature

Reporting bugs is an important contribution. Please make sure to include:

  • Expected and actual behavior
  • OpenTelemetry, OS, and .NET versions you are using
  • If possible, steps to reproduce

How to contribute

Before you start

Please read the contribution guide and the code of conduct. for general practices of the OpenTelemetry project.

Select a good issue from the links below (ordered by difficulty/complexity):

Comment on the issue that you want to work on so we can assign it to you and clarify anything related to it.

If you would like to work on something that is not listed as an issue (e.g. a new feature or enhancement) please first read our vision and roadmap to make sure your proposal aligns with the goals of the project, then create an issue and describe your proposal. It is best to do this in advance so that maintainers can decide if the proposal is a good fit for this repository. This will help avoid situations when you spend significant time on something that maintainers may decide this repo is not the right place for.