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
* Add highlighted work and membership count
* Update annual report draft
Co-authored-by: Bob Killen <[email protected]>
* Made changes based on feedback
* Updates
* Updates
Co-authored-by: name <[email protected]>
* Add statistics for unique approvers and reviewers
* Updates from feedback
* Add more detail around k-dev migration
* Minor edits
Link out to new membership co-ordinators
Changed phrasing in L120
* Fix spelling
* update new member coordinator url
Co-authored-by: Bob Killen <[email protected]>
Co-authored-by: name <[email protected]>
1. What work did the SIG do this year that should be highlighted?
6
6
7
-
-
8
-
-
9
-
-
7
+
- Continuing to provide critical services to enable the work of over 75,000+ contributors
8
+
-[Migrating K-Dev to a managed kubernetes.io account](https://github.com/kubernetes/community/issues/5877)
9
+
- We encountered a problem with the k-dev mailing list where we couldn't send out community-wide meeting invites, due to restrictions on public google groups.
10
+
- In order to overcome this issue, we migrated to Google Workspace.
11
+
- It took over 80+ hours across the Contribex team to complete this migration.
12
+
- Steering Election with Elekto
13
+
- Elekto was created by Manish Sahani as part of an LFX internship. It allows us to run Elections on our own infrastructure.
14
+
- Voters can login using their github credentials and vote from the election site.
15
+
- The previous method of holding elections was prone to issues when it came to the following:
16
+
- Obtaining the list of elegible voters from 75,000+ contributors
17
+
- Sending ballots out via email
18
+
- Elekto automated the process of obtaining the list of elegible voters
19
+
- Ballots are no longer sent out via email, and instead contributors log in to the elections site to submit their ballots.
20
+
- More information can be found in [community issue #5096](https://github.com/kubernetes/community/issues/5096)
- The CLA service provided to us by the Linux Foundation was being deprecated.
24
+
- We needed to migrate to EasyCLA2 to ensure continuity of service for our 75,000+ active committers.
25
+
- Contributor Summit North America
26
+
- Contributor Celebration
27
+
- Restaffed teams
28
+
- Moderation
29
+
- Youtube Admin
30
+
- Ran three group mentoring cohorts to grow contributors in named roles (50% graduation rate) for contribex, docs, and a 'chair' cohort for multiple SIGs
31
+
- Grew @k8scontributors twitter account to 5,700 followers
32
+
- Created documentation geared towards Chairs and Tech Leads to help grow and support their roles and groups operations
33
+
- Curated and ran 8 months of Leads meetings (16 meetings total)
10
34
11
35
2. What initiatives are you working on that aren't being tracked in KEPs?
12
36
13
-
-
14
-
-
15
-
-
16
-
17
-
3. KEP work in 2021 (1.x, 1.y, 1.z):
18
-
19
-
<!--
20
-
In future, this will be generated from kubernetes/enhancements kep.yaml files
21
-
1. with SIG as owning-sig or in participating-sigs
22
-
2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
|[Community Management](https://git.k8s.io/community/sig-contributor-experience#community-management)|[discuss.k8s.io End User Forum Admin](https://discuss.k8s.io)|
45
+
|[Community Management](https://git.k8s.io/community/sig-contributor-experience#community-management)|[Mailing List Admin](https://k8s.dev/docs/comms/moderation/)|
|[Contributor Comms](https://git.k8s.io/community/sig-contributor-experience#contributor-comms)|[Stewardship of k8scontributors twitter](https://twitter.com/k8scontributors)|
|[GitHub Management](https://git.k8s.io/community/sig-contributor-experience#github-management)|[GitHub Master -> Main rename](https://github.com/kubernetes/org/issues/2222)|
63
+
|[GitHub Management](https://git.k8s.io/community/sig-contributor-experience#github-management)|[GitHub New Membership Coordinator](https://git.k8s.io/community/github-management/README.md#other-roles)|
1. What areas and/or subprojects does your group need the most help with?
40
80
Any areas with 2 or fewer OWNERs? (link to more details)
41
-
42
-
-
43
-
-
44
-
-
81
+
82
+
- GitHub Admin Subproject
83
+
- We need to bring on more [new membership coordinators](https://git.k8s.io/community/github-management#new-membership-coordinator).
84
+
- New Membership Coordinators are current contributors to the Kubernetes project that help serve as a friendly face to newer, prospective community members, guiding them through the process to request membership to a Kubernetes GitHub organization.
85
+
- Community Management Automation
86
+
-[Zoom to Youtube](https://github.com/kubernetes/community/issues/5201)
- We need a [Group Mentoring Coordinator](https://github.com/kubernetes/community/issues/6517)
93
+
- We need a [3rd Party Mentoring Coordinator](https://github.com/kubernetes/community/issues/6471)
45
94
46
95
2. What metrics/community health stats does your group care about and/or measure?
47
96
48
-
-
49
-
-
50
-
-
97
+
- Issue Velocity
98
+
-[We are a service orientated sig, Issues are the main form of how we track work.](https://k8s.devstats.cncf.io/d/73/inactive-issues-by-sig?orgId=1&var-sigs=%22contributor-experience%22&from=1609459200000&to=1640995199000)
99
+
51
100
52
101
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
102
to activities or programs that provide useful context or allow easy participation?
54
103
55
-
-
104
+
- We don't have a CONTRIBUTING.md as our SIG's contributing process does not differ from the process in the Contributor Guide.
56
105
57
106
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
107
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
108
60
-
-
109
+
- N/A
61
110
62
111
5. Does the group have contributors from multiple companies/affiliations?
63
112
64
-
-
113
+
- Yes. [25+ Different groups](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Contributor%20Experience&var-repo_name=kubernetes%2Fkubernetes&var-companies=All&from=1577854800000&to=1640926800000&viewPanel=1)
65
114
66
115
6. Are there ways end users/companies can contribute that they currently are not?
67
116
If one of those ways is more full time support, what would they work on and why?
68
117
69
-
-
70
-
-
118
+
- A full time community manager who can maintain several subprojects and help with the overall direction of the group
119
+
- More full time support for the items under bullet point 1.
120
+
- This work will reduce toil for contributor experience and all groups in the project.
71
121
72
122
## Membership
73
123
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 -->
124
+
Statistics were retrieved on 2022-01-30
125
+
126
+
- Primary slack channel member count: 1895
127
+
- Primary mailing list member count: 366
128
+
- Primary meeting attendee count (estimated, if needed): 10-15
129
+
- Primary meeting participant count (estimated, if needed): 5
130
+
- Unique reviewers for SIG-owned packages: 20
131
+
- Unique approvers for SIG-owned packages: 28
80
132
81
133
Include any other ways you measure group membership
82
134
@@ -87,17 +139,32 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
87
139
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
Owns and manages overall community repo, including community group documentation and operations.
151
+
- community-management
152
+
Manages operations and policy for upstream community group communication platforms.
153
+
- contributor-comms
154
+
Contributor Communications focuses on amplifying the success of Kubernetes contributors through marketing.
155
+
- contributors-documentation
156
+
writes and maintains documentation around contributing to Kubernetes, including the Contributor's Guide, Developer's Guide, and contributor website.
157
+
- devstats
158
+
Maintains and updates https://k8s.devstats.cncf.io, including taking requests for new charts.
159
+
- events
160
+
Creates and runs contributor-focused events, such as the Contributor Summit. Event Teams are part of this subproject.
161
+
- github-management
162
+
Manages and controls Github permissions, repos, and groups, including Org Membership.
163
+
- mentoring
164
+
Oversees and develops programs for helping contributors ascend the contributor ladder, including the New Contributor Workshops, Meet Our Contributors, and other programs.
165
+
- slack-infra
166
+
Creates and maintains tools and automation for Kubernetes Slack.
167
+
<!-- BEGIN CUSTOM CONTENT -->
101
168
102
169
## Working groups
103
170
@@ -106,32 +173,28 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
106
173
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
0 commit comments