# OpenTelemetry Specification

[![Slack](https://img.shields.io/badge/slack-@cncf/otel--specification-brightgreen.svg?logo=slack)](https://cloud-native.slack.com/archives/C01N7PP1THC)
[![Release](https://img.shields.io/github/v/release/open-telemetry/opentelemetry-specification)](https://github.com/open-telemetry/opentelemetry-specification/releases/)
[![OpenSSF Scorecard for opentelemetry-specification](https://api.scorecard.dev/projects/github.com/open-telemetry/opentelemetry-specification/badge)](https://scorecard.dev/viewer/?uri=github.com/open-telemetry/opentelemetry-specification)
[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/11058/badge)](https://www.bestpractices.dev/projects/11058)

![OpenTelemetry Logo](https://opentelemetry.io/img/logos/opentelemetry-horizontal-color.png)

The **[OpenTelemetry][] specification** describes the cross-language
requirements and expectations for all OpenTelemetry implementations.

- The [latest release][] is hosted at
  [opentelemetry.io/docs/specs/otel][]
- Markdown sources are under [specification](./specification/README.md)

## Change / contribution process

For details, see [CONTRIBUTING.md](CONTRIBUTING.md), in particular read
[Proposing a change](CONTRIBUTING.md#proposing-a-change) before submitting a PR.

## Questions

New to CNCF Slack? [Create an account](https://slack.cncf.io/) first, then join
the
[`#otel-specification`](https://cloud-native.slack.com/archives/C01N7PP1THC)
channel for questions and discussion.

Questions that need additional attention can be brought to the regular
specifications meeting. EU and US timezone friendly meeting is held every
Tuesday at 8 AM Pacific time. Meeting notes are held in the [Google
doc](https://docs.google.com/document/d/1pdvPeKjA8v8w_fGKAN68JjWBmVJtPCpqdi9IZrd6eEo/edit).
APAC timezone friendly meetings are held on request. See
[OpenTelemetry calendar](https://github.com/open-telemetry/community#calendar).

Escalations to technical committee may be made over the
[email](https://github.com/open-telemetry/community/blob/main/README.md#mailing-lists).
Technical committee holds regular meetings, notes are held
[here](https://docs.google.com/document/d/1hOHPCu5TGenqTeWPB9qQB_qd33uITZBcvK1FnWxYJAw/edit?usp=sharing).

## Specification compliance matrix by language

See [Compliance of Implementations with
Specification](./spec-compliance-matrix.md).

## Project Timeline

The current project status as well as information on notable past releases is found at
[the OpenTelemetry project page](https://opentelemetry.io/status/).

Information about current work and future development plans is found at the
[specification development milestones](https://github.com/open-telemetry/opentelemetry-specification/milestones).

## Versioning the Specification

Changes to the [specification](./specification/overview.md) are versioned according to [Semantic Versioning 2.0](https://semver.org/spec/v2.0.0.html) and described in [CHANGELOG.md](CHANGELOG.md). Layout changes are not versioned. Specific implementations of the specification should specify which version they implement.

Changes to the change process itself are not currently versioned but may be independently versioned in the future.

## License

By contributing to OpenTelemetry Specification repository, you agree that your contributions will be licensed under its [Apache 2.0 License](LICENSE).

[OpenTelemetry]: https://opentelemetry.io
[latest release]: https://github.com/open-telemetry/opentelemetry-specification/releases/latest
[opentelemetry.io/docs/specs/otel]: https://opentelemetry.io/docs/specs/otel/

## Maintainers

The maintainers of the specification are a superset of the Technical Committee.

- [OpenTelemetry Technical Committee](https://github.com/open-telemetry/community/blob/main/community-members.md#technical-committee)
- [Josh Suereth](https://github.com/jsuereth), Google
- [Robert Pająk](https://github.com/pellared), Splunk

For more information about the maintainer role, see the [community repository](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#maintainer).

## Approvers

[Specification sponsors](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#specification-sponsor) represent the approver role for the specification, along with additional responsibilities and privileges.

- [Alex Boten](https://github.com/codeboten), Grafana Labs
- [Christian Neumüller](https://github.com/Oberon00), Dynatrace
- [Cijo Thomas](https://github.com/cijothomas), Microsoft
- [Daniel Dyla](https://github.com/dyladan), Dynatrace
- [Josh Suereth](https://github.com/jsuereth), Google
- [Juraci Paixão Kröhling](https://github.com/jpkrohling), OllyGarden
- [Leighton Chen](https://github.com/lzchen), Microsoft
- [Marc Alff](https://github.com/marcalff), Oracle
- [Severin Neumann](https://github.com/svrnm), Independent
- [Ted Young](https://github.com/tedsuo), Grafana Labs
- [Tristan Sloughter](https://github.com/tsloughter), MyDecisiveAI
- [Tyler Yahn](https://github.com/MrAlias), Splunk

For more information about the approver role, see the [community repository](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#approver).

## Triagers

- [OpenTelemetry Governance Committee](https://github.com/open-telemetry/community/blob/main/community-members.md#governance-committee)

For more information about the triager role, see the [community repository](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#triager).

## Emeritus

- [Christian Beedgen](https://github.com/kumoroku), Approver
- [Daniel Jaglowski](https://github.com/djaglowski), Approver
- [David Poncelow](https://github.com/zenmoto), Approver
- [Nikita Salnikov-Tarnovski](https://github.com/iNikem), Approver