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
-[2831 - Kubelet OpenTelemetry Tracing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2831-kubelet-tracing) - alpha in 1.24
36
36
37
37
## Project health
38
38
39
39
1. What areas and/or subprojects does your group need the most help with?
40
40
Any areas with 2 or fewer OWNERs? (link to more details)
41
41
42
-
-
43
-
-
44
-
-
42
+
-[kubernetes-sigs/prometheus-adapter](https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/OWNERS_ALIASES) has 1 active approver
45
43
46
44
2. What metrics/community health stats does your group care about and/or measure?
47
45
48
-
-
49
-
-
50
-
-
46
+
- Devstats
47
+
-[Review Load](https://k8s.devstats.cncf.io/d/80/pr-workload-per-sig-and-repository-chart?orgId=1&var-sigs=%22instrumentation%22&var-repo_name=kubernetes%2Fkubernetes&var-repo=kuberneteskubernetes&from=now-1y&to=now) has been relatively level over the year
48
+
-[Time to Approve and Merge](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=d7&var-repogroup_name=SIG%20Instrumentation&var-repo_name=kubernetes%2Fkubernetes&var-apichange=All&var-size_name=All&var-kind_name=All) has been relatively low over the last year.
49
+
- Meeting attendance
50
+
- Meeting attendance is ~10 each week
51
+
- Triage attendance is ~5 each week
52
+
- Enhancement velocity
53
+
- 7 Active enhancements over the year
51
54
52
55
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
56
to activities or programs that provide useful context or allow easy participation?
54
57
55
-
-
58
+
- We don't have our own CONTRIBUTING.md as the overall one is suitable for our SIG. However, we have [filed an issue](https://github.com/kubernetes/community/issues/6462) to create one to better document how to get involved with our subprojects.
56
59
57
60
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
61
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
62
60
-
-
63
+
- N/A, we don't have special training or requirements
61
64
62
65
5. Does the group have contributors from multiple companies/affiliations?
63
66
64
-
-
67
+
- Yes: Google, Red Hat, Sony, VMware, Intel, independent contributors, and more
65
68
66
69
6. Are there ways end users/companies can contribute that they currently are not?
67
70
If one of those ways is more full time support, what would they work on and why?
68
71
69
-
-
70
-
-
72
+
SIG leads performed a [staffing and gap analysis](https://docs.google.com/document/d/1qeoP6i7GBTVJuJE1AGY5iU9dqmAOxrjqkfNQ2-rBeyI/edit#heading=h.849b7ydpl7ip) for the SIG's projects. We definitely can use more help, and need more part-time/full-time contributors.
73
+
74
+
### Summary
75
+
76
+
-**KTLO:** 4 leads at 5%, 2 maintainers at 10% for core, 9-10 maintainers at 5% for 5 subprojects (can have overlap between roles, but need a minimum of 3-4 part-time contributors at 25%)
77
+
-**Feature work:** needs significant ongoing additional investment, minimum of 2-3 FT devs or features will continue to slip
78
+
79
+
### Details
80
+
81
+
-**KTLO:** Requires two experienced part-time maintainers at 10% (e.g. 2x4h = 8h/wk) in addition to the SIG leadership (chairs/TLs @ minimum of 2h/wk)
82
+
- Chairs/TLs currently perform the bulk of this work but even amongst the four of them, **do not** have 8h total weekly allocated
83
+
-**Feature work:** requires significantly more investment from development and review time.
84
+
- E.g. Structured logging initiative requires a minimum of 2 FT staff for the duration of feature development from beta -> GA
85
+
- Additional metric stability classes and graduation: 1PT maintainer at 25% for the duration of feature development
86
+
- SIG currently owns a number of KEPs stuck in alpha/beta due to lack of dev resources:
- Subprojects are currently mature/stable and mainly have KTLO needs
94
+
- kube-state-metrics: 2-3 experienced maintainers at 5%, currently staffed
95
+
- Metrics-server: 2 experienced maintainers at 5%, currently staffed
96
+
- Custom-metrics-apiserver: 1 experienced maintainer at 5%, currently staffed
97
+
- Klog: 2 experienced maintainers at 5%, has **no current staffing**
98
+
- Prometheus-adapter: 2 experienced maintainers at 5%, has **no current staffing**
71
99
72
100
## Membership
73
101
74
-
- Primary slack channel member count:
75
-
- Primary mailing list member count:
76
-
- Primary meeting attendee count (estimated, if needed):
77
-
- Primary meeting participant count (estimated, if needed):
78
-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
79
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
102
+
- Primary slack channel member count: 1,740
103
+
- Primary mailing list member count: 324
104
+
- Primary meeting attendee count (estimated, if needed): 8-12
105
+
- Primary meeting participant count (estimated, if needed): 4-6
106
+
- Unique reviewers for SIG-owned packages: 24 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
107
+
- Unique approvers for SIG-owned packages: 22 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
80
108
81
109
Include any other ways you measure group membership
82
110
111
+
- We track active members in the SIG primarily based on devstats and meeting participation, and maintain an up-to-date roster of members in [kubernetes/org](https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml). These teams also serve as aliases for GitHub pings.
112
+
83
113
## Subprojects
84
114
85
115
<!--
86
116
In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
87
117
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
0 commit comments