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: sig-architecture/annual-report-2021.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,12 @@
15
15
16
16
**Is your README accurate? have a CONTRIBUTING.md file?**
17
17
18
+
Yes, our README is accurate. We do not have a CONTRIBUTING.md file, and so will add one.
19
+
18
20
**All subprojects correctly mapped and listed in sigs.yaml?**
19
21
22
+
Yes.
23
+
20
24
**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?**
21
25
22
26
Our bi-weekly meeting is normally well attended, with approximately 20 individuals on a typical day, though it varies from a handful of folks to 40 or 50.
@@ -33,6 +37,8 @@ We have not been getting updates from the working groups on any regular cadence.
33
37
34
38
**When was your last monthly community-wide update? (provide link to deck and/or recording)**
35
39
40
+
[December, 2020](https://youtu.be/rnNqcUeCD8E) at KubeCon NA, published on YouTube.
41
+
36
42
## Membership
37
43
38
44
**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?**
@@ -47,21 +53,25 @@ For the enhancements subproject, all owners are all active.
47
53
48
54
For the API review subproject... [@dims or @liggitt please update]
49
55
50
-
For the code organization subproject...[@dims or @liggitt please update]
56
+
For the code organization subproject, @dims and @liggitt run regular meetings and review PRs and issues, pulling
57
+
in other owners as needed.
51
58
52
59
**How do you measure membership? By mailing list members, OWNERs, or something else?**
53
60
54
61
Mailing list members, though based on bounces during calendar updates, there are quite a few out-of-date memberships.
55
62
56
63
**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?**
57
64
65
+
SIG Architecture owns very little code. The API review and Production Readiness Review projects do have reviewers and approvers
66
+
for those specialized purposes. Each of those programs has a documented shadow program to add new reviewers and approvers.
67
+
58
68
**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?**
59
69
60
70
**What programs do you participate in for new contributors?**
61
71
62
72
**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?**
63
73
64
-
Yes. Our chairs are from three different companies. We have many participants have many participants and subproject owners from those same companies and others.
74
+
Yes. Our chairs are from three different companies. We have many participants and subproject owners from those same companies and others.
0 commit comments