1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
# Running a Contributor Ladder Growth Program
There are differences in curriculum for reviewer and Chair and/or Tech Lead
groups but the foundation of each are mostly the same unless otherwise noted
below in the set up instructions. This difference is also reflected in our
[community membership guidelines].
## Discovery of Needs
Cadence:
ContribEx sets an issue in k/community requesting SIGs to participate preceding
the next release by one month.
Rolling:
SIGs can approach ContribEx at anytime to start a group; file an issue in
kubernetes/community or talk with us in #sig-contribex.
## Curriculum Building
While not a fully structured program, some light planning is needed to make sure
the curriculum being taught is relevant for the group. Here are our base
suggestions:
*Reviewer*
- Enhancements
- Overview of Release Cycle
- Overview of SIGs subprojects
- Development
- Triage
- Reviews - detailed walk thrus
- API Changes
- Testing
- Code Freeze
- Cherry-Picks/Branch Management
*Chair*
- Enhancement Planning
- Meetings and Organization
- Responsibilities and governance overview
- Consensus-building
- Cross-project communication
*Chair/TL combo*
Chair + Reviewer
- All of the above
- [Sample curriculum](../programs/leads-curriculum.md)
One of the best strategies is to have everyone work on something together,
Examples:
- reviewing guidelines for the SIG if there are none/updating guide
- CONTRIBUTING.md for the SIG if there isn't one/updating guide
- mid-size project
- a release cycle of features for the SIG, establishing better processes
## Setup and Outreach
0. Need is established and SIG provides a mentor*
1. ContribEx kicks off two issues, sets a target start and end date, and selects
a coordinator
- issue #1: outreach issue to collect folks who are interested and set up
infra, issue will close when there are the max participants needed
example: https://github.com/kubernetes/community/issues/5962
key bits of info: target, start/end date, sign up and requirements, slack info,
mentors, coordinators
- issue #2: structure of sessions and assign guest speakers
start with a hackmd to coordinate with mentors and then set issue
1. ContribEx Coordinator(s) posts issue #1 to the following places:
- SIG list first and then k-dev mailing lists with timeboxes for responses
- #diversity, #kubernetes-contributors, #sig-[name], and other slack channels
3. Slack stand ups happen on the day of the SIG meetings but the 30-min
bi-weekly meetings will need to be arranged. Coorindator should send out a
doodle to the selected group with a few times that work for the mentors.
4. Coorindator and mentors work together on the three-month plan template.
Coordinator will schedule the speakers and create a calendar for the group.
example here: https://hackmd.io/1aAIaMChR8Gfi31aOKBHlA
5. Mentor creates template that serves as a reference guide for the group. See
a sig-node example here: https://hackmd.io/8i8prErgSOamUmEZDDZPWA
6. Program begins at the kick off meeting
- [TODO add kick off template]
7. Feedback is continuous as you stand up weekly; however, the ContribEx
Coorindator will set a mid program check-in. In this check-in, members of the
group will start their application process for their roles and any group members
who have not had the time.
- [TODO add community membership template]
8. By this point, folks should know where they stand. At the end of the program,
mentors and/or individuals will start the PR process in OWNERS files or
sigs.yaml for leadership roles for those who are ready
[community membership guidelines]: community-membership.md
|
