Skip to content

Commit 325d181

Browse files
authored
Create annual-report-2020
1 parent d3ae637 commit 325d181

File tree

1 file changed

+85
-0
lines changed

1 file changed

+85
-0
lines changed

sig-windows/annual-report-2020

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# Kubernetes Community Group Annual Reports Template
2+
3+
Checklist
4+
[ ] Read about the process here (https://git.k8s.io/community/committee-steering/governance/annual-reports.md#reporting-process)
5+
[x] Copy this template into a new document and share with your mailing list/slack channel/meeting on whatever platform (gdocs, hackmd, etc.) that the team prefers.
6+
[x] Remove sections that are not applicable (example: if you are a working group, delete the special interest group questions)
7+
[ ] Pick graphs from Devstats to pull supporting data for your responses.
8+
[ ] Schedule a time with your Steering liaison and other Chairs, TLs, and Organizers of your group to check-in on your roles as Chair or Working Group Organizer. If anyone would rather meet 1:1, please have them reach out to the liaison directly, we are happy to. We’d like to talk about: challenges, wins, things you didn’t know before but wish you did, want to continue in the role or help finding a replacement; and lastly any feedback you have for us as a body and how we can help you succeed and feel comfortable in these leadership roles.
9+
[ ] PR this document into your community group directory in kubernetes/community (example: sig-architecture/)
10+
[ ] by March 8th, 2021
11+
[ ] titled: annual-report-YEAR.md
12+
[ ] are there any responses that you’d like to share privately first? [email protected] or tag your liaison in for discussion.
13+
14+
# Special Interest Groups:
15+
(do not copy if you are responding for a working group)
16+
17+
18+
# Instructions for this section:
19+
[ ] each response should have supporting documentation, linked KEPs, graphs, data
20+
[ ] err on the side of being descriptive with your responses. End users and others that read this might not know our upstream acronyms, shorthand, or where to find a reference.
21+
Operational
22+
23+
How are you doing with operational tasks in sig-governance.md?
24+
Is your README accurate?have a CONTRIBUTING.md file?
25+
Yes / Yes - README.md is up to date, CONTRIBUTING.md is still accurate but could use some updates.
26+
27+
All subprojects correctly mapped and listed in sigs.yaml?
28+
Yes
29+
30+
What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?
31+
Meetings have decent attendance but few active participants.
32+
Meeting notes are used during the meetings are up to date.
33+
Recordings are up to date but few views
34+
35+
How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?
36+
Owners files are up to date. Existing subprojects are mostly in maintenance mode. We would like to try starting one or two subprojects to gather more interest / new participation in SIG-Windows.
37+
Same question as above but for working groups.
38+
N/A
39+
40+
When was your last monthly community-wide update? (provide link to deck and/or recording)
41+
Sept 17 Slides recording
42+
Membership
43+
44+
Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?
45+
Yes
46+
47+
How do you measure membership? By mailing list members, OWNERs, or something else?
48+
We don’t measure membership.
49+
50+
How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?
51+
We are blocked on reviewer/approver bandwidth from other SIGs much more often than reviewer/approver bandwidth in our SIG.
52+
Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?
53+
We want to focus on this in the next few months. Some ideas we have are pairing with folks and establishing one or two new focused subprojects that will encourage new participants.
54+
55+
What programs do you participate in for new contributors? We’re wanting to groom long-term/dedicated contributors. Are there programs to help with this? Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?
56+
Yes, we have contributors from many companies. Current initiatives and project health
57+
58+
[ ] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members.
59+
60+
What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?
61+
62+
Containerd support
63+
Network policy support
64+
Cluster API support
65+
Privileged containers
66+
67+
Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?
68+
69+
Alpha / going alpha
70+
Privileged containers
71+
Node log viewer
72+
Beta / going beta
73+
DSR support
74+
Stable / going stable
75+
CSI proxy
76+
77+
What areas and/or subprojects does the group need the most help with?
78+
79+
E2e tests / coverage / keeping things green
80+
Testgrid
81+
Cross-SIG collaboration
82+
What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?
83+
Average open days for PR is long - mainly due to requiring reviews/approvals from multiple SIGs most of the time.
84+
85+

0 commit comments

Comments
 (0)