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: .github/ISSUE_TEMPLATE/instrumentation_request.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,7 @@ labels: instrumentation-request
5
5
---
6
6
7
7
<!--
8
-
**NB:** Before opening an instrumentation request against this repo, consider whether the instrumentation should/could be implemented in the [other OpenTelemetry client libraries](https://github.com/open-telemetry/). If so, please [open an issue on opentelemetry-specification](https://github.com/open-telemetry/opentelemetry-specification/issues/new) first.
9
-
10
-
You are welcome to try to build your own instrumentation. If you do, please let us know if you have any questions/feedback.
8
+
**NB:** Before opening an instrumentation request against this repo, please read [the contributing guidelines for new instrumentation](../../CONTRIBUTING.md#new-instrumentation).
11
9
-->
12
10
13
11
### Is your instrumentation request related to a problem? Please describe
@@ -20,11 +18,22 @@ A clear and concise description of what the problem is. Ex. I'm always frustrate
20
18
21
19
22
20
### Do you expect this instrumentation to be commonly used?
21
+
23
22
Weekly Downloads:
24
23
25
24
### What version of instrumentation are you interested in using?
25
+
26
26
Versions:
27
27
28
+
### Code Owners
29
+
30
+
<!--
31
+
New Instrumentation requests need at least 2 code-owners that will maintain the instrumentation long-term.
32
+
-->
33
+
34
+
- Owner 1
35
+
- Owner 2
36
+
28
37
### Additional context
29
38
<!--
30
39
Add any other context or screenshots about the instrumentation request here. Is there a reference you could point for the well-defined lifecycle methods?
about: Request yourself being added as a component owner for a component in this repository
4
+
labels: type:ownership-request
5
+
---
6
+
7
+
<!--
8
+
**NB:** Before opening a component ownership request against this repo, please read [CONTRIBUTING.md](../../CONTRIBUTING.md#component-ownership) and its subsections first.
9
+
-->
10
+
11
+
### Which component are you requesting ownership of?
12
+
13
+
<!--
14
+
Put a link to the component here.
15
+
-->
16
+
17
+
### Related Work and Qualifications
18
+
19
+
<!--
20
+
List here why you're qualified to take ownership of the component, see [CONTRIBUTING.md](../../CONTRIBUTING.md#becoming-a-component-owner) for details.
21
+
22
+
Examples:
23
+
- I am working on <related open-source-project> and have deep knowledge of the instrumented package.
24
+
- I am using the instrumented package on a regular basis and have deep knowledge of the instrumented package.
25
+
- I am working on <similar package or system> and have deep knowledge of the concepts of the instrumented package.
26
+
- I am an engineer at an observability vendor we would like to sponsor this component.
27
+
-->
28
+
29
+
### Checklist
30
+
31
+
-[ ] I have read [CONTRIBUTING.md](../../CONTRIBUTING.md) and understand the responsibilities of a component owner.
32
+
-[ ] I agree to follow and uphold the [mission, vision and values](https://github.com/open-telemetry/community/blob/main/mission-vision-values.md) of the OpenTelemetry project
33
+
-[ ] I understand that the component I'm requesting ownership of may be subject to the [OpenTelemetry Semantic Conventions](https://github.com/open-telemetry/semantic-conventions) and agree to follow the rules set out therein.
34
+
35
+
### Additional context
36
+
37
+
<!--
38
+
Add any other context that does not fit any of the above sections
Copy file name to clipboardExpand all lines: .github/workflows/close-stale.yml
+25-1Lines changed: 25 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
name: 'Close stale issues and PRs'
2
2
on:
3
3
schedule:
4
-
- cron: '30 6 * * 1'
4
+
- cron: '30 6 * * *'
5
5
6
6
jobs:
7
7
stale:
@@ -20,3 +20,27 @@ jobs:
20
20
exempt-issue-labels: never-stale
21
21
exempt-pr-labels: never-stale
22
22
any-of-labels: information-requested
23
+
- uses: actions/stale@v9
24
+
with:
25
+
days-before-issue-stale: 0
26
+
days-before-issue-close: 14
27
+
stale-issue-message: 'This package does not have an assigned [component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#component-ownership) and is considered [unmaintained](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#unmaintained). As such this package is in feature-freeze and this issue will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
28
+
29
+
Are you familiar with this package? Consider [becoming a component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#becoming-a-component-owner).'
30
+
close-issue-message: 'This issue was closed because no owner or sponsor has been found after 14 days'
stale-pr-message: 'This package does not have an assigned [component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#component-ownership) and is considered [unmaintained](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#unmaintained). As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
40
+
41
+
Are you familiar with this package? Consider [becoming a component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#becoming-a-component-owner).'
42
+
close-pr-message: 'This issue was closed because no owner or sponsor has been found after 14 days'
0 commit comments