Skip to content

Commit b69d557

Browse files
k8s-ci-robotk8s-ci-robot
authored
Merge pull request #5573 from mrbobbytables/report
SIG ContribEx: Add 2021 Annual Report
2 parents 672d300 + 094e566 commit b69d557

File tree

1 file changed

+141
-0
lines changed

1 file changed

+141
-0
lines changed

‎sig-contributor-experience/annual-report-2020.md

Lines changed: 141 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,141 @@
1+
# Special Interest Groups: Contributor Experience
2+
3+
#### Operational
4+
5+
- How are you doing with operational tasks in [SIG]-governance.md?
6+
- Is your README accurate? have a CONTRIBUTING.md file?
7+
- The README is up to date and accurate, we do not have a
8+
CONTRIBUTING.md file.
9+
- All subprojects correctly mapped and listed in sigs.yaml?
10+
- Yes
11+
- What’s your meeting culture? Large/small, active/quiet, learnings? Meeting
12+
notes up to date? Are you keeping recordings up to date/trends in community
13+
members watching recordings?
14+
- We have biweekly zoom meetings. It is small, but active.
15+
- The APAC-friendly zoom meeting was poorly attended so we are
16+
discontinuing it.
17+
- We are also hosting biweekly asynchronous meetings on slack, which has
18+
made it easier for members from APAC regions to participate.
19+
- Meeting notes are up to date, recordings of the meetings are published.
20+
The YouTube recordings often have <10 views with jumps to 30~ when they
21+
are featured on the front page of the channel. Collectively during 2020
22+
the SIG ContribEx playlist had 167 views with an average watch time of
23+
00:03:55. Compared to the previous year, this was an increase in views,
24+
but a decrease in average watch time.
25+
- How does the group get updates, reports, or feedback from subprojects? Are
26+
there any springing up or being retired? Are OWNERS.md files up to date in
27+
these areas?
28+
- The weekly meeting (zoom or in slack) serves as a subproject status update.
29+
The notes are then sent to the mailing list.
30+
- A [subproject owner audit][audit] was completed in the first half of 2020
31+
- Some processes/meetings have been retired or retooled to reduce administrative
32+
overhead and become more async friendly.
33+
- Same question as above but for working groups.
34+
- There is no formal reporting mechanism from the working groups. The updates
35+
largely come from issues or discussions that bubble up into the SIG.
36+
- SIG Contributor Experience TLs also participate in WG Infra directly, so we haven't
37+
found the need for a formal reporting process.
38+
- When was your last public community-wide update? (provide link to deck and/or
39+
recording)
40+
- August 2020 at KubeCon Europe Virtual - [link] to the session.
41+
A similar Contribex session is also planned for KubeCon Europe 2021.
42+
- July 2020 in the community meeting. Links to [updates] are added to the SIG ContribEx README.
43+
44+
[link]: https://kccnceu20.sched.com/event/c9yh/intro-contributor-experience-sig-jorge-castro-vmware-bob-killen-university-of-michigan
45+
[audit]: https://github.com/kubernetes/community/issues/4585
46+
[updates]: https://github.com/kubernetes/community/tree/master/sig-contributor-experience#current-status
47+
48+
49+
#### Membership
50+
51+
- Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?
52+
- No, there are several subproject owners that have become inactive and should
53+
be moved to emeritus status. An audit is planned for 2021.
54+
- How do you measure membership? By mailing list members, OWNERs, or something
55+
else?
56+
- Those that are actively engaged with meetings
57+
- How does the group measure reviewer and approver bandwidth? Do you need help
58+
in any area now? What are you doing about it?
59+
- We do not actively monitor reviewer/approver bandwidth in a formalized way.
60+
However, our [relative PR velocity][vel] is in a good state. We could use more
61+
reviewers/approvers to help reduce risk and improve long-term sustainability.
62+
- Is there a healthy onboarding and growth path for contributors in your SIG?
63+
What are some activities that the group does to encourage this? What programs
64+
are you participating in to grow contributors throughout the contributor ladder?
65+
- We have lost many contributors over the past year. General calls for help did
66+
not attract many new contributors, but with some additional outreach and
67+
raising the problem areas in an [easier to see way][pr] has attracted new folk.
68+
- We are actively applying the `good-first-issue` and `help-wanted` labels to issues
69+
and are closely mentoring new contributors who pick up these issues.
70+
- What programs do you participate in for new contributors?
71+
- We have previously participated with Outreachy and Season of Docs.
72+
- Does the group have contributors from multiple companies/affiliations? Can end
73+
users/companies contribute in some way that they currently are not?
74+
- Yes, we have multiple avenues for contributing for both code and non-code
75+
projects alike.
76+
77+
78+
#### Current initiatives and project health
79+
80+
- What are initiatives that should be highlighted, lauded, shout outs, that
81+
your group is proud of? Currently underway? What are some of the longer tail
82+
projects that your group is working on?
83+
- The contributor website (https://k8s.dev)
84+
- Triage process improvements
85+
- The 2020 Contributor Celebration
86+
- Retired the Kubernetes-Incubator Org
87+
- In Progress: Migrating the default branch on GitHub from `master` to `main`
88+
- In Progress: Revamping the prow approval plugin to support granual approvals
89+
- Year to date KEP work:
90+
- [KEP-1553: Issue Triage Workflow and Automation][kep]
91+
- In Progress: KEP for revamping the prow approval plugin
92+
- What initiatives are you working on that aren't being tracked in KEPs?
93+
94+
| Subproject | Initiative / Program |
95+
|:-------------------------:|:--------------------------------------:|
96+
| Community | Community Repo Stewardship |
97+
| Community Management | Annual Contributor Survey |
98+
| Community Management | Calendar Admin |
99+
| Community Management | Chair and TL Meetings + Docs |
100+
| Community Management | Discuss Admin |
101+
| Community Management | Mailing List Admin |
102+
| Community Management | Slack Admin |
103+
| Community Management | Zoom / YouTube Admin |
104+
| Community Management | Zoom / YouTube Automation (zapier) |
105+
| Contributor Documentation | Contributor Guide Stewardship |
106+
| Contributor Documentation | Contributor Site |
107+
| Contributor Documentation | Developer Guide Audit |
108+
| Contributor Documentation | Developer Guide Stewardship |
109+
| Contributor Documentation | Season of Docs |
110+
| Contributors Comms | Contributor / SIG Profiling |
111+
| Contributors Comms | Stewardship of k8scontributors twitter |
112+
| Devstats | Devstats Dashboard Update |
113+
| Events | Monthly Community Meeting |
114+
| Events | Office Hours |
115+
| GitHub Management | GitHub Admin / Moderation |
116+
| GitHub Management | GitHub Master -> Main rename |
117+
| GitHub Management | GitHub New Membership Coordinator |
118+
| Mentoring | 1:1 Hour |
119+
| Mentoring | Google Summer of Code |
120+
| Mentoring | Group Mentoring |
121+
| Mentoring | LFX Mentor Program |
122+
| Mentoring | Meet our Contributors |
123+
| Mentoring | New Contributor Workshop |
124+
| Mentoring | Outreachy |
125+
| Slack Infra | slack-infra |
126+
127+
**source:** [ContribEx Initatives and Prioritization spreadsheet][pr]
128+
129+
- What areas and/or subprojects does the group need the most help with?
130+
- Many need help. These are being tracked separately in the
131+
[ContribEx Initatives and Prioritization spreadsheet][pr].
132+
- What metrics/community health stats does your group care about and/or measure?
133+
- The only dashboard we use at this point in time is the
134+
[PR workloads table][vel] in devstats.
135+
136+
137+
138+
[vel]: https://k8s.devstats.cncf.io/d/34/pr-workload-per-sig-table?orgId=1&var-period_name=Last%20year
139+
[kep]: https://git.k8s.io/enhancements/keps/sig-contributor-experience/1553-issue-triage
140+
[pr]: https://docs.google.com/spreadsheets/d/1glhdFcUdqYAByW16hujxK1X_0k9mt_nrkCO4POeDNbs/edit#gid=0
141+

0 commit comments

Comments
 (0)