|
1 |
| -# Mentoring Lead Handbook |
| 1 | +# Third Party Mentoring Lead Handbook |
2 | 2 |
|
3 | 3 | ## Overview
|
4 | 4 |
|
5 |
| -The Mentoring Lead role is created to help upstream Kubernetes contributors to participates in various mentorship programs like [GSoC](mentoring/programs/google-summer-of-code.md), [GSoD](mentoring/programs/google-season-of-docs.md), [LFX Mentorship](mentoring/programs/lfx-mentorship.md) and many more as an independent organisation or under Cloud Native Computing Foundation(CNCF). |
| 5 | +The Mentoring Lead role is created to help upstream Kubernetes contributors to participates in various mentorship programs like [GSoC](https://github.com/kubernetes/community/blob/master/mentoring/programs/google-summer-of-code.md), [GSoD](https://github.com/kubernetes/community/blob/master/mentoring/programs/google-season-of-docs.md), [LFX Mentorship](https://github.com/kubernetes/community/blob/master/mentoring/programs/lfx-mentorship.md) and many more as an independent organisation or under Cloud Native Computing Foundation(CNCF). |
6 | 6 |
|
7 |
| -## Responsibilities |
| 7 | +## Role Description |
| 8 | + The role lead should: |
8 | 9 |
|
9 |
| -Major responsibilities incluedes a commitment to: |
| 10 | +- Keep a calendar of dates for each program (when to submit our project name, when to submit the project scope, when selecting period is, etc) throughout the year and |
| 11 | +- Coordinate all submissions and participation in each one |
| 12 | +- Go to sig meetings and slack channels to proactively help with scoping and planning work / job descriptions |
| 13 | +- Help onboard interns to the k8s specific community items like coordinate a hello for them at the k8s monthly community meeting |
| 14 | +- Help off board interns to the k8s specific community items like demo at monthly community meeting |
10 | 15 |
|
11 |
| -- Be proactive in information sharing regarding various mentorship cohorts |
12 |
| -- Be a bridge between the CNCF employees and the mentors from kubernetes project |
| 16 | + |
| 17 | +### Responsibilities |
| 18 | + |
| 19 | +Major responsibilities includes a commitment to: |
| 20 | + |
| 21 | +- Be proactive in information sharing, through the mailing list/slack channels, regarding various mentorship cohorts |
| 22 | +- Be a bridge between the CNCF staff, mentors, and mentees from kubernetes project |
13 | 23 | - Be an active contributor, who could identify parts of the project that could get help from mentorship programs
|
14 | 24 | - Be a go-to person for all SIGs to help them with their mentorship proposals
|
15 | 25 | - Be welcoming of everyone by being your unique self
|
@@ -37,4 +47,12 @@ Requirements:
|
37 | 47 |
|
38 | 48 | #### Duration
|
39 | 49 |
|
40 |
| -Ideally, no lead should be in the same position indefinitely. With that in mind,the project would like to see new leadership every 24 months to keep a fresh perspective. |
| 50 | +Ideally, no lead should be in the same position indefinitely. With that in mind,the project would like to see new leadership every 24 months to keep a fresh perspective. |
| 51 | + |
| 52 | +### Becoming a Shadow |
| 53 | + |
| 54 | +Any regular contributor to mentoring subproject can put forward their interest to the mentoring lead to become a shadow. If accepted, the objective of the council members is to nurture that shadow into a leadership position in the next 12 months. |
| 55 | + |
| 56 | +#### Expectations of a Shadow |
| 57 | + |
| 58 | +Consistently communicate and collaborate closely with the lead. The objective is to get you, as the shadown, to be a confident leader of the above responsibilities. Be ready to backfill for them when they are unable to attend a meeting or represent the subproject. |
0 commit comments