Skip to content

Commit 27f5c66

Browse files
authored
docs: display the component-owner role more prominently in README.md (#2800)
1 parent f6bc4cc commit 27f5c66

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

README.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@
3838

3939
# OpenTelemetry JavaScript Contrib
4040

41-
A repository for OpenTelemetry JavaScript contributions that are not part of the [core repository](https://github.com/open-telemetry/opentelemetry-js) and core distribution of the API and the SDK.
41+
A repository for community-maintained OpenTelemetry JavaScript contributions that are not part of the [core repository](https://github.com/open-telemetry/opentelemetry-js) and core distribution of the API and the SDK.
4242

4343
This project includes:
4444

@@ -52,6 +52,19 @@ Please read the [contributing guidelines on adding new instrumentation](CONTRIBU
5252

5353
**Resource Detectors**: OpenTelemetry can collect resource attributes of the entity that producing telemetry. For example, a process producing telemetry that is running in a container on Kubernetes has a Pod name, it is in a namespace and possibly is part of a Deployment which also has a name. All three of these attributes can be included in the `Resource`.
5454

55+
## Component Ownership
56+
57+
This repository includes various components, each maintained by one or more designated component owners. Unless
58+
necessary to resolve disagreements, [@open-telemetry/javascript-maintainers](https://github.com/orgs/open-telemetry/teams/javascript-maintainers)
59+
take a more passive role when it comes to Maintaining these components.
60+
61+
Component owners have the authority to make decisions on implementation and feature requests, following the best practices
62+
and the [mission, vision and values](https://github.com/open-telemetry/community/blob/main/mission-vision-values.md) of the OpenTelemetry Project. They are also assigned the Triager role to manage issues
63+
related to their components, and are the primary contact for conducting PR reviews for their components.
64+
65+
Component owners are automatically assigned to pull requests as reviewers. The source of truth for component ownership
66+
is [.github/component_owners.yml](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/.github/component_owners.yml).
67+
5568
## Stability levels
5669

5770
Stability level for components in this repository follow the definitions in [CONTRIBUTING.md](./CONTRIBUTING.md).

0 commit comments

Comments
 (0)