summaryrefslogtreecommitdiff
path: root/mentoring
diff options
context:
space:
mode:
Diffstat (limited to 'mentoring')
-rw-r--r--mentoring/programs/mentoring-lead.md32
1 files changed, 25 insertions, 7 deletions
diff --git a/mentoring/programs/mentoring-lead.md b/mentoring/programs/mentoring-lead.md
index 1f6c8022..906545f0 100644
--- a/mentoring/programs/mentoring-lead.md
+++ b/mentoring/programs/mentoring-lead.md
@@ -1,15 +1,25 @@
-# Mentoring Lead Handbook
+# Third Party Mentoring Lead Handbook
## Overview
-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).
+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).
-## Responsibilities
+## Role Description
+ The role lead should:
-Major responsibilities incluedes a commitment to:
+- 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
+- Coordinate all submissions and participation in each one
+- Go to sig meetings and slack channels to proactively help with scoping and planning work / job descriptions
+- Help onboard interns to the k8s specific community items like coordinate a hello for them at the k8s monthly community meeting
+- Help off board interns to the k8s specific community items like demo at monthly community meeting
-- Be proactive in information sharing regarding various mentorship cohorts
-- Be a bridge between the CNCF employees and the mentors from kubernetes project
+
+### Responsibilities
+
+Major responsibilities includes a commitment to:
+
+- Be proactive in information sharing, through the mailing list/slack channels, regarding various mentorship cohorts
+- Be a bridge between the CNCF staff, mentors, and mentees from kubernetes project
- Be an active contributor, who could identify parts of the project that could get help from mentorship programs
- Be a go-to person for all SIGs to help them with their mentorship proposals
- Be welcoming of everyone by being your unique self
@@ -37,4 +47,12 @@ Requirements:
#### Duration
-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. \ No newline at end of file
+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.
+
+### Becoming a Shadow
+
+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.
+
+#### Expectations of a Shadow
+
+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. \ No newline at end of file