Merge pull request #4435 from parispittman/meetourcontrib

meet our contrib host and doc updates

2 files changed, 161 insertions, 28 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
diff --git a/mentoring/meet-our-contributors.md b/mentoring/meet-our-contributors.md
index 5fdd540c..61172ab7 100644
--- a/mentoring/meet-our-contributors.md
+++ b/mentoring/meet-our-contributors.md
@@ -1,23 +1,40 @@
 # Meet Our Contributors - Ask Us Anything!
 
-When Slack seems like it’s going too fast, and you just need a quick answer from a human...
+When Slack seems like it’s going too fast, and you just need a quick answer from
+a human...
 
-Meet Our Contributors gives you a monthly one-hour opportunity to ask questions about our upstream community, watch interviews with our contributors, and participate in peer code reviews.
+Meet Our Contributors gives you a monthly one-hour opportunity to ask questions
+about our upstream community, watch interviews with our contributors, and
+participate in peer code reviews.
 
 ## When:
-Every first Wednesday of the month at the following times. Grab a copy of the calendar to yours from [kubernetes.io/community](https://kubernetes.io/community/)
-* 02:30pm UTC [Convert to your timezone](https://www.thetimezoneconverter.com/?t=02%3A30%20pm&tz=UTC&).
-* 08:00pm UTC [Convert to your timezone](https://www.thetimezoneconverter.com/?t=08%3A00%20pm&tz=UTC&).
+Every first Wednesday of the month at the following times. Grab a copy of the
+calendar to yours from [kubernetes.io/community]
+* 03:30pm UTC [Convert to your timezone].
+
+## Where:  
+Follow along live:  
+[Kubernetes YouTube Channel](https://www.youtube.com/c/KubernetesCommunity/live)
+
+Ask questions:
+#meet-our-contributors slack channel  
+To ask anonymously, direct message the host on slack. They will ID at the start
+of the show.  
+
+Watch past recordings:  
+Playlist of [previous Meet-Our-Contributors monthly meetings]
 
-Tune into the [Kubernetes YouTube Channel](https://www.youtube.com/c/KubernetesCommunity/live) to follow along with video, check out our playlist of [previous Meet-Our-Contributors monthly meetings](https://www.youtube.com/playlist?list=PL69nYSiGNLP3QpQrhZq_sLYo77BVKv09F) and join [#meet-our-contributors](https://kubernetes.slack.com/messages/meet-our-contributors) on Slack for questions and discussion.
 
 ## What You'll Gain By Participating:
 
 * An opportunity to learn more about how to get started contributing to K8s
 * A chance to get your PRs reviewed by members of the community
-* Peer code review that can help you get more eyes on your code, or learn more about a part of the Kubernetes code that may have you struggling
-* A deeper understanding of the unique role that our contributors occupy in the Kubernetes ecosystem as a whole
-* Practical advice and hands-on tips for how you can get started as a Kubernetes contributor, become a member, or otherwise contribute to the project
+* Peer code review that can help you get more eyes on your code, or learn more
+about a part of the Kubernetes code that may have you struggling
+* A deeper understanding of the unique role that our contributors occupy in the
+Kubernetes ecosystem as a whole
+* Practical advice and hands-on tips for how you can get started as a Kubernetes
+contributor, become a member, or otherwise contribute to the project
 
 ## What’s on-topic:
 * How our contributors got started with k8s
@@ -28,13 +45,12 @@ Tune into the [Kubernetes YouTube Channel](https://www.youtube.com/c/KubernetesC
 * Testing
 
 ## What’s off-topic:
-* End-user questions (Check out [#office-hours](https://kubernetes.slack.com/messages/office-hours) on Slack and details [here](/events/office-hours.md))
+* End-user questions (Check out [#office-hours] on Slack and details [here])
 
 ## Submitting questions and/or code for review/walk through:
 ### Questions:
-* Day of on Twitter - use the hashtag [#k8smoc](https://twitter.com/hashtag/k8smoc) after your question   
-* Slack - Ask your question in [#meet-our-contributors](https://kubernetes.slack.com/messages/meet-our-contributors)
-
+* Day of on Twitter - use the hashtag [#k8smoc] after your question   
+* Slack - Ask your question in #meet-our-contributors
 
 Questions will be on a first-come, first-served basis. The first half of the discussion will be dedicated to questions for contributors and in the second half, we will pick a problem (in advance) for peer code review.
 
@@ -43,11 +59,61 @@ Questions will be on a first-come, first-served basis. The first half of the dis
 
 Problems will be chosen based on time commitment needed, the skills of the reviewer, and if a large amount are submitted, need for the project.
 
-## Call for Volunteers:
-Contributors - [sign up to answer questions!](https://goo.gl/uhEJ33)
+## Call for Mentor Panelists!
 
-Expectations of volunteers:
+Expectations of mentors:
 * Be online 5 minutes early. You can look at questions in the queue by joining the #meet-our-contributors Slack channel to give yourself some time to prepare.
 * Expect questions about the contribution process, membership, navigating the Kubernetes seas, testing, and general questions about you and your path to open source/Kubernetes. It's okay if you don't know the answer!
 * We will be using video chat (Zoom, but livestreaming through YouTube) but voice-only is fine if you are more comfortable with that.
 * Be willing to provide suggestions and feedback to make this process & experience better!
+
+
+## Host Instructions
+TODO: elaborate here and upload example comms
+
+Want to host in another timezone? Reach out to us on the #sig-contribex slack
+channel!
+0. Recruit a live streamer from sig-contribex
+1. Recruit panelists (3-4) that represent a mix of backgrounds, sigs, and experience
+levels. Look to devstats contributor dashboards for most recent releases to get
+folks who are active in the project. You don't want all of the same voice; please
+make this as diverse as possible.
+2. Send panelists the zoom link calendar invite and a prep email. Tell the panelists
+to help advertise on the mailing lists and networks.
+3. Advertise. Send a note to k-dev, request a tweet from social@cncf.io, post in
+#k-dev, #meet-our-contributors, and #sig-contribex slack channels
+4. Confirm with everyone a few days before. We always have at least one person that
+can no longer accommodate with their schedules and will need a back up or know
+that you will be one less.
+5. Tweet and get the word out in the AM (ask others to tweet for you!) of the show
+6. Have panelists meet 5 minutes early for the streamer to test audio.
+7. While testing, go over the agenda for the panelists, give them a chance to ask
+questions, also give them a heads up on questions that have already come through
+so they can think of responses a head of time.
+8. Start the show!
+9. Show agenda:
+- Welcome to x month's Meet Our Contributors!
+- Intro yourself (brief, name usually and that you are the host)
+- We have a code of conduct! ... talk about where to find it, be excellent across
+x platforms, if someone needs to report conduct@kubernetes.io
+- Go over instructions on how to ask questions and panelists can ask each other
+questions
+- State: "Our agenda today as always: intros, announcements, and q&a!"
+- Ask panelists to do introductions (no order, just call out names). They can take
+up to 5 minutes if they go into their background.
+- Converse freely with the panelists so its not boring Q&A. As host should only
+answer a question if other panelists are done or no one has a response.
+
+
+
+
+
+[kubernetes.io/community](https://kubernetes.io/community/)
+[#meet-our-contributors]: https://kubernetes.slack.com/messages/meet-our-contributors
+[Convert to your timezone](https://www.thetimezoneconverter.com/?t=02%3A30%20pm&tz=UTC&)]
+[Kubernetes YouTube Channel](https://www.youtube.com/c/KubernetesCommunity/live)
+[previous Meet-Our-Contributors monthly meetings]: (https://www.youtube.com/playlist?list=PL69nYSiGNLP3QpQrhZq_sLYo77BVKv09F)
+[#office-hours]: https://kubernetes.slack.com/messages/office-hours
+[#k8smoc]: https://twitter.com/hashtag/k8smoc
+[#meet-our-contributors]: https://kubernetes.slack.com/messages/meet-our-contributors
+[here]: /events/office-hours.md