updated process info

1 files changed, 79 insertions, 12 deletions

diff --git a/mentoring/group-mentoring.md b/mentoring/group-mentoring.md
index f5600e01..0126091f 100644
--- a/mentoring/group-mentoring.md
+++ b/mentoring/group-mentoring.md
@@ -1,35 +1,102 @@
 # Group Mentoring for Contributor Ladder Growth
 *This is a work in progress*
 
+
 ## Summary
-This is an experimental group mentoring program where individuals will work self-paced in a semi-structured learning environment over the course of three months. Want to get `/lgtm` rights? Be a decision maker in an OWNERS file? This could be a great way to get the knowledge you need, some accountability to do it.  Through this program you will get the opportunity to interact with active contributors who may be on the same path as you as well very experienced Kubernetes contributors (Pilots). 
+This is an experimental group mentoring program where individuals will work
+self-paced in a semi-structured learning environment over the course of three
+months. Want to get `/lgtm` rights? Be a decision maker in an OWNERS file? This
+could be a great way to get the knowledge you need, and some accountability to
+do it. Through this program you will get the opportunity to interact with active
+contributors who may be on the same path as you as well very experienced
+Kubernetes contributors.
 
 ## How This Works
-This program is built around our [community membership guidelines](/community-membership.md). This doc shows how you can grow through the project in different roles and provides the requirements to get to each level on our ladder.
+Foundation:  
+This program is built around our [community membership guidelines].
+This doc shows how you can grow through the project in different roles and
+provides the requirements to get to each level on our ladder. Building trust is
+the key to this document.
+
+## Cohorts
+Contributors will form small cohorts of no more than 10 (8-10 is great) all aiming
+to achieve the same goal - the next stage on the contributor ladder - with the
+help of active contributors (1 mentor to 3 mentees). For example, our first test
+cohort was Member -> Reviewer in SIG Apps, SIG Cluster Lifecycle, and SIG AWS.  
+
+Each cohort will last 2-3 months based on the time requirement in the community
+membership guidelines per level. This time requirement is pretty flexible and not
+a hard line because as noted above, this is about building trust and skills. Folks
+want to know you are dependable and understand the domain.
 
-A cohort will consist of 8-10 individuals aiming to achieve the same goal - the next stage on the contributor ladder - with the help of 3 Pilots representing 3 different projects. For example, our first test cohort is Member -> Reviewer in SIG Apps, SIG Cluster Lifecycle, and SIG AWS. The semi-structured learning element will happen in bi-weekly standups/workshops over zoom with various development areas targeted. 
+The cohort gathers on slack in a private room that one of the mentors or sig-contribex
+will PR into the slack config files on the k/community repo.
+TODO: make the self service aspect here solid for faster onboarding
 
-Each cohort will last 2-3 months based on the time requirement in the community membership guidelines per level.
+Mentors can rotate facilitating once a week for slack standups with the expectation
+that cohort members need to check in with a predetermined status update
+(accomplishments, challenges, etc)  
 
 ## Benefits of a Cohort
 * Peer mentoring  
 * Clear goals, objectives, and timelines  
 * Each mentee is working toward the same goal, cohort has an end date/timeframe  
 * Exposure to multiple areas of the project making well-rounded contributors  
-* Pilots share time commitments and responsibilities  
+* Mentors share time commitments and responsibilities  
 * Exposure to multiple mentors in an open and collaborative environment
 
 ## Logistics
-SIGs and other parts of the project will reach out to SIG Contributor Experience with requests for additional roles and provide a Pilot that is not the lead but at the same level they are targeting.
+1. SIG/WG determines need
+2. Consults with sig-contribex; contribex sets up infra (slack channel; TODO build this out)
+3. Posts a note to their mailing list and k-dev that they are looking for more reviewers/
+approvers/x_role and would like to form a group to mentor who are already in the
+role below it. (example: already a member and they need more reviewers)
+4. Sets a start date and end date; schedule a kick off meeting so everyone can meet
+over video/audio (1 and only unless the group establishes other comms). Also set
+the weekly slack standup days so they are consistent.
+5. Program begins
+6. If the mentors think certain skills will need to be taught/learned, they should
+be done upfront. (We scattered them for the first cohort and there were things
+  that would be been more valuable to learn in the beginning of the journey)  
+6. Feedback is continuous*
+7. Mentors start PRs for those who graduated  
+
+*Feedback is continuous but will have a half way check in point. The goal is that
+mentees should not be surprised by the outcome of the program.  
+
+## Mentor requirements  
+TODO  
 
-Mentees will fill out the [Mentoring/Contributor Info Form](https://goo.gl/forms/SHWAiZ9Ih1qwuJbs1) which will eventually be posted to kubernetes.io and included in PR template. Based on responses, mentees will be matched with future cohorts.
+## First Cohort Success Rates
+5/10 graduated into OWNERs files from members to reviewers.   
+TODO check how many are still active  
 
-Feedback is continuous but will have a half way check in point. The goal is that mentees should not be surprised by the outcome of the program.
+## FAQs
+I'm a SIG Chair/TL/Subproject Owner and have a need for more members, reviewers,
+approvers, how can we form a cohort?  
+TODO  
+
+I'm a contributor looking for a cohort, where do I go?  
+TODO  
+
+I'm not a chair, tech lead, or subproject owner but I'm a reviewer or approver,
+how can I help?  
+TODO  
 
-## First Cohort
-Our founding cohort is a predetermined set of mentees and Pilots. Our main goal with this cohort is to establish that group mentoring is viable for our workflow and culture. They will begin in mid-December and end around the end of February. 
 
 ## Important Links
-[Mentor Guide]  - to be updated  
-[Mentee Guide](/mentoring/group-mentee-guide.md)
+[Mentor Guide]  
+[Mentee Guide]
+
+
+## Open ended questions
+how can mentors organize the tasks, issues, prs, that they give to the mentees?   
+should they be high priority items to help with backlog and mentor at the same time?  
+should we include a list of topics that should be covered by role?  
+- example: for member to reviewer we focused on - live how to code review, how to review [better] docs, communicating with empathy, advanced testing/ci, general community/governance  
+
 
+[Mentee Guide]: /mentoring/group-mentee-guide.md
+[Mentoring/Contributor Info Form]: https://goo.gl/forms/SHWAiZ9Ih1qwuJbs1
+[Mentor Guide]: /mentoring/mentor-guide.md
+[community membership guidelines]: /community-membership.md