Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore] Add "Code Owners" field to new component template #23780

Merged
merged 1 commit into from
Jul 26, 2023
Merged

[chore] Add "Code Owners" field to new component template #23780

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions .github/ISSUE_TEMPLATE/new_component.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,11 +27,21 @@ body:
description: A vendor-specific component directly interfaces with a vendor-specific API and is expected to be maintained by a representative of the same vendor.
options:
- label: This is a vendor-specific component
- label: If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.
- label: If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.
- type: input
attributes:
label: Code Owner(s)
description: A code owner is responsible for supporting the component, including triaging issues, reviewing PRs, and submitting bug fixes.
Please list one or more members or aspiring members of the OpenTelemetry project who will serve as code owners.
For vendor-specific components, the code owner is required and must be a representative of the vendor.
For non-vendor components, having a code owner is strongly recommended. However, you may use the issue to try to find a code owner for your component.
- type: input
attributes:
label: Sponsor (optional)
description: "A sponsor is an approver who will be in charge of being the official reviewer of the code. For vendor-specific components, it's good to have a volunteer sponsor. If you can't find one, we'll assign one in a round-robin fashion. For non-vendor components, having a sponsor means that your use-case has been validated. If there are no sponsors yet for the component, it's fine: use the issue as a means to try to find a sponsor for your component."
description: "A sponsor is an approver who will be in charge of being the official reviewer of the code.
For vendor-specific components, it's good to have a volunteer sponsor. If you can't find one, we'll assign one in a round-robin fashion.
For non-vendor components, having a sponsor means that your use-case has been validated.
If there are no sponsors yet for the component, it's fine: use the issue as a means to try to find a sponsor for your component."
- type: textarea
attributes:
label: Additional context
Expand Down