|
1 | | -group-mentoring.md may have some other process info baked into the program info. |
2 | | - |
3 | | -## Logistics |
4 | | -1. SIG/WG determines need |
5 | | -2. Consults with sig-contribex; contribex sets up infra (slack channel; TODO build this out) |
6 | | -3. Posts a note to their mailing list and k-dev that they are looking for more |
7 | | -reviewers/approvers/x_role and would like to form a group to mentor who are |
8 | | -already in the role below it. (example: already a member and they need more |
9 | | - reviewers) |
10 | | -4. Sets a start date and end date; schedule a kick off meeting so everyone can |
11 | | -meet |
12 | | -over video/audio (1 and only unless the group establishes other comms). Also set |
13 | | -the weekly slack standup days so they are consistent. |
14 | | -5. Program begins |
15 | | -6. If the mentors think certain skills will need to be taught/learned, they |
16 | | -should be done upfront. (We scattered them for the first cohort and there were |
17 | | - things that would be been more valuable to learn in the beginning of the |
18 | | - journey) |
19 | | -6. Feedback is continuous* |
20 | | -7. Mentors start PRs for those who graduated |
21 | | - |
22 | | -*Feedback is continuous but will have a half way check in point. The goal is that |
23 | | -mentees should not be surprised by the outcome of the program. |
| 1 | +# Running a Contributor Ladder Growth Program |
| 2 | + |
| 3 | +There are differences in curriculum for reviewer and Chair and/or Tech Lead |
| 4 | +groups but the foundation of each are mostly the same unless otherwise noted |
| 5 | +below in the set up instructions. This difference is also reflected in our |
| 6 | +[community membership guidelines]. |
| 7 | + |
| 8 | +## Discovery of Needs |
| 9 | + |
| 10 | +Cadence: |
| 11 | +ContribEx sets an issue in k/community requesting SIGs to participate preceding |
| 12 | +the next release by one month. |
| 13 | + |
| 14 | +Rolling: |
| 15 | +SIGs can approach ContribEx at anytime to start a group; file an issue in |
| 16 | +kubernetes/community or talk with us in #sig-contribex. |
| 17 | + |
| 18 | +## Curriculum Building |
| 19 | +While not a fully structured program, some light planning is needed to make sure |
| 20 | +the curriculum being taught is relevant for the group. Here are our base |
| 21 | +suggestions: |
| 22 | + |
| 23 | +*Reviewer* |
| 24 | +- Enhancements |
| 25 | +- Overview of Release Cycle |
| 26 | +- Development |
| 27 | + - Triage |
| 28 | + - Reviews |
| 29 | + - API Changes |
| 30 | + - Testing |
| 31 | +- Code Freeze |
| 32 | +- Cherry-Picks/Branch Management |
| 33 | + |
| 34 | +*Chair* |
| 35 | +- Enhancement Planning |
| 36 | +- Meetings and Organization |
| 37 | +- Responsibilities and governance overview |
| 38 | +- Consensus-building |
| 39 | +- Cross-project communication |
| 40 | + |
| 41 | +*Chair/TL combo* |
| 42 | +Chair + Reviewer |
| 43 | +- All of the above |
| 44 | + |
| 45 | +One of the best strategies is to have everyone work on something together, |
| 46 | +Examples: |
| 47 | +- reviewing guidelines for the SIG if there are none/updating guide |
| 48 | +- CONTRIBUTING.md for the SIG if there isn't one/updating guide |
| 49 | +- mid-size project |
| 50 | +- a release cycle of features for the SIG, establishing better processes |
| 51 | + |
| 52 | +## Setup and Outreach |
| 53 | +0. Need is established and SIG provides a mentor* |
| 54 | +1. ContribEx kicks off two issues, sets a target start and end date, and selects |
| 55 | +a coordinator |
| 56 | + - issue #1: outreach issue to collect folks who are interested, issue will |
| 57 | + close when there are the max participants needed |
| 58 | + - issue #2 setting up infra - template here: [TODO link to example] |
| 59 | +2. ContribEx or SIG member posts the issue to the following places: |
| 60 | + - SIG and k-dev mailing lists |
| 61 | + - #diversity, #kubernetes-contributors, #sig-[name], and other slack channels |
| 62 | +3. Coordinator arranges a doodle for the kick off meeting and days/times that |
| 63 | +would be best for the mentor and group for slack standups and touch points. Once conscensus is reached, coordinator schedules it. |
| 64 | +4. Mentor creates template that serves as a reference guide for the group. See |
| 65 | +a sig-node example here: https://hackmd.io/8i8prErgSOamUmEZDDZPWA |
| 66 | +5. Program begins at the kick off meeting |
| 67 | + - [TODO add kick off template] |
| 68 | +6. Feedback is continuous as you stand up weekly; however, the ContribEx |
| 69 | +Coorindator will set a mid program check-in. In this check-in, members of the |
| 70 | +group will start their application process for their roles and any group members |
| 71 | + who have not had the time. |
| 72 | + - [TODO add community membership template] |
| 73 | +7. By this point, folks should know where they stand. At the end of the program, |
| 74 | + mentors and/or individuals will start the PR process in OWNERS files or |
| 75 | + sigs.yaml for leadership roles for those who are ready |
| 76 | + |
| 77 | + |
| 78 | +[community membership guidelines]: community-membership.md |
0 commit comments