You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+49Lines changed: 49 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -231,6 +231,55 @@ In addition, when a change is complex or a reviewer is unfamiliar with the code,
231
231
the reviewer may seek additional reviews from people more familiar with the
232
232
change before merging a PR.
233
233
234
+
## Component Ownership
235
+
236
+
This repository contains many components which are maintained by more than the typical set of ruby-contrib maintainers and approvers.
237
+
Each component in this repository SHOULD have a component owner who is responsible for maintaining it.
238
+
The README.md for each component SHOULD contain its owner, but the source of truth for component ownership is in [.github/component_owners.yml](.github/component_owners.yml).
239
+
240
+
Component owners are generally given authority to make decisions relating to implementation and feature requests for their components,
241
+
provided they follow the best practices set out by the maintainers and the [mission, vision and values](https://github.com/open-telemetry/community/blob/main/mission-vision-values.md)
242
+
of the OpenTelemetry Project. To facilitate independent triage of issues pertaining to the owned component, component owners are assigned
Component owners MUST do their best to maintain a high level of quality, security, performance, and specification compliance within their components.
246
+
Maintainers may override the decisions of component owners, but should only do so when they feel one or more of these traits is compromised.
247
+
248
+
### Becoming a Component Owner
249
+
250
+
To become a component owner, contributors MUST be a [member](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#member) of the OpenTelemetry GitHub organization.
251
+
To become a member, follow the steps in the [community guidelines for membership requirements](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#requirements).
252
+
253
+
To become a component owner, contributors SHOULD demonstrate prior knowledge of the instrumented package or the concepts therein.
254
+
255
+
Ways do to so may be by providing proof of:
256
+
257
+
- current or prior involvement with the community that develops the upstream package
258
+
-**Example:** A person working on MongoDB requesting ownership over a MongoDB instrumentation
259
+
- current or prior involvement with a community that develops systems with similar concepts
260
+
-**Example:** A person previously working on MySQL requesting ownership of a instrumentation package that instruments another database client library instrumentation.
261
+
- current or prior extensive use of the instrumented package in other project they are involved in
262
+
-**Example:** A person working at a company that makes extensive use of the `koala` library requesting ownership of the `opentelemetry-instrumentation-koala` package.
263
+
- a vested interest in the telemetry being emitted from that instrumentation
264
+
-**Example:** A person employed at an observability vendor that relies on the continued maintenance of the instrumentation
265
+
266
+
**Examples of proof may include but are not limited to:**
267
+
268
+
- Links to issues/PRs they worked on
269
+
- Links to blog posts authored by them on behalf of the organization developing that system
270
+
- Membership in GitHub teams/organizations that are associated with the development of the upstream package
271
+
272
+
Aspiring Component Owners MUST agree to uphold the [mission, vision and values](https://github.com/open-telemetry/community/blob/main/mission-vision-values.md) of the OpenTelemetry project.
273
+
Further, aspiring component owners are expected to have knowledge of the [OpenTelemetry Semantic Conventions](https://github.com/open-telemetry/semantic-conventions)
274
+
and MUST agree to adhere to the rules set out therein.
275
+
276
+
If all these conditions are met, aspiring component owners are encouraged to self-nominate by opening an issue.
277
+
@open-telemetry/ruby-contrib-maintainers will then engage on the issue, may ask questions, and will then - based on the
278
+
information provided on the issue - either approve or deny the ownership request. If the ownership request has been
279
+
approved, the new component owner opens a PR to add themselves to the list of owners ([.github/component_owners.yml](.github/component_owners.yml))
280
+
for that package.
281
+
@open-telemetry/ruby-contrib-maintainers will add the component owner to @open-telemetry/ruby-contrib-triagers.
282
+
234
283
## Releases
235
284
236
285
This repository includes a set of tools for releasing gems. Only maintainers
0 commit comments