1
1
# Kubernetes Community Group Annual Reports
2
2
3
- This document outlines the bootstrap process for an annual reporting and
4
- communication structure for Special Interest Groups (SIGs), Working Groups (WGs)
5
- , User Groups (UGs), and Committees
3
+ This document outlines the process for an annual reporting and
4
+ communication structure for Special Interest Groups (SIGs), Working Groups (WGs),
5
+ User Groups (UGs), and Committees.
6
6
All policy updates will be in their respective [ SIG] , [ WG] , and [ UG]
7
7
governance docs as well as the general [ governance] guidance.
8
8
@@ -26,7 +26,6 @@ to make this an agenda item of topic to discuss together. Chairs and Organizers
26
26
ensure that reports are complete, accurate, and submitted to the Steering
27
27
Committee.
28
28
29
- ### 2021 and on:
30
29
1 . Steering Committee liaison reaches out to group leads to kick off
31
30
2 . Chairs/Organizers will:
32
31
- share with their groups (see tips below) and begin to
@@ -56,27 +55,6 @@ We'd like to hear about the following:
56
55
- any feedback you have for us as a body and how we can help Chairs and
57
56
Organizers succeed and feel comfortable in your role.
58
57
59
- ### 2020:
60
- Due to playing catch up with 37 community groups, we will have a slightly
61
- modified timeline bootstrap process this year and then will follow the process
62
- outlined for 2021. Working Groups, due to their temporary nature, will be the
63
- only group to submit for 2020.
64
-
65
- 1 . Steering Committee will assign one member as a liaison to each community
66
- group for kick off, help, or guidance needed throughout the process during the
67
- first week of July
68
- 2 . Working Group Organizers create one report and send it to/share it with
69
- [email protected] for review; reports should take
~ 30 days to
70
- complete (work with your liaison on timeline)
71
- 3 . Steering will schedule private meetings to follow up on anything denoted as
72
- a private matter on the report; reports are not made public until all private
73
- comments have been addressed
74
- 4 . Once reviewed and follow ups are completed, the liaison will ask the
75
- organizer(s) of the group to submit a pull request to that groups documentation
76
- in the community repo
77
- 5 . The Steering Committee liaison will work directly with groups that have
78
- follow up items and update Steering during regular monthly meetings.
79
-
80
58
### Tips for Chairs and Working Group Organizers:
81
59
- Work together with your groups roles and community members to complete;
82
60
suggestion: schedule a dedicated meeting or intentional agenda item to go over
0 commit comments