more mentoring folder restructure

7 files changed, 144 insertions, 125 deletions

diff --git a/mentoring/group-mentee-guide.md b/mentoring/group-mentee-guide.md
index bbf7c648..c8ddab4a 100644
--- a/mentoring/group-mentee-guide.md
+++ b/mentoring/group-mentee-guide.md
@@ -2,81 +2,87 @@
 This doc is a work in progress
 
 ## Welcome and Summary
-Welcome prospective mentee! 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, and interact with active contributors who may on the same path as you and our experienced Kubernetes developers. 
-
-During the three month period, you will work on a path to the next level of membership which will take some work along with peers who have the same goal. This cohort will include mentors who are at least the level that you are targeting with ample experience in the project. These mentors will counsel but not provide answers to the problem or the solution itself. Think of them as true pilots of the sea - navigational experts - only to our codebase. At the end of the three month period, with open communication, the decision to accept or not proceed with the advancement should not be a surprise. 
-
-Familiarize yourself with the [community membership requirements doc](/community-membership.md) including the requirements needed for your specific journey. You’ll receive sponsorship from the mentors and other people you've worked on issues/PRs with upon successful completion of the program. 
-
-## Expectations    
-* You understand the requirements to become $member_role (ex: member->reviewer) 
+Welcome prospective mentee! 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, and interact with active contributors who may on the
+same path as you and our experienced Kubernetes developers.
+
+During the three month period, you will work on a path to the next level of
+membership which will take some work along with peers who have the same goal.
+This cohort will include mentors who are at least the level that you are
+targeting with ample experience in the project. These mentors will counsel but
+not provide answers to the problem or the solution itself. Think of them as true
+pilots of the sea - navigational experts - only to our codebase. At the end of
+the three month period, you'll have conversations with the mentors about getting
+into the OWNERs file.
+
+Familiarize yourself with the [community membership requirements doc]including
+the requirements needed for your specific journey. You’ll receive sponsorship
+from the mentors and other people you've worked on issues/PRs with upon
+successful completion of the program.
+
+## Expectations  
+* You understand the requirements to become $member_role (ex: member->reviewer)
 * Good standing throughout the program and uphold our code of conduct
-* Attend two bi-weekly standups/workshops a month (1 hour each)
-* The program is at your pace but these meetings will discuss your wins and blocks
-* These meetings will also cover development area topics, suggested activities, and groomed issues
+* Check-in during a designated day on slack for a "stand-up". Mentors will be
+there that day, too, and guaranteed feedback.
 * Be helpful to your peers in the cohort
 * Give back and be a mentor in a future cohort
 * Mutual respect from mentors and peers who are in the cohort with you
-* Adhere to the Kubernetes Community Guidelines
-
-## Development Areas & Activities
-These topics will be covered during bi-weekly standups/workshops. The suggested activities will be covered in the mentee's normal day to day. Know something that should be added? Start a convo/add a PR - your comments are appreciated.
-
-### Current Member Cohort Topics
-* Effective communication in our ecosystem
-* Kubernetes Governance 101 (what's a SIG?, OWNERS files, steering committee, etc.)
-* Identifying & understanding issue backlog and prioritization
-* Contributing to testing (how to run tests and create new ones)
-* [need 3-4 more]
-
-Suggested Activity
-* Scrub XS and typo fixes into branches they maintain for occasional quick bulk review/approval with mentors
-* Help review docs
-* Setup feature and run tests or examples and fix documentation if needed
-* Create new content in community based on feedback from wider community
 
-
-### Current Reviewer Cohort
+### Member to Reviewer Cohort
+Topics that are good for discussion during that time period:
 * Code Reviews the Kubernetes Way (i.e. best practices)
-* How to groom issues for new members
-* Communicating effectively as a leader (on GH and throughout project)
-* The value in / how to tech review docs
+* How to groom issues for new members/contributors
+* Communicating effectively (on GH and throughout project)
+* Technical documentation
 * Kubernetes Governance 201 (SIG deep dive, proposals)
-* Testing (what should be an e2e test, how to write S, M, L, tests) 
+* Testing (what should be an e2e test, how to write S, M, L, tests)
+* Kubernetes Governance 101 (keps, subprojects, OWNERS files, steering committee,
+etc.)
+* Identifying & understanding issue backlog and prioritization
+* Contributing to testing (how to run tests and create new ones)
 
 Suggested Activity
-* Be a tech reviewer for docs 
+* Be a tech reviewer for docs
 * Write an E2E test
+* Help out in #pr-reviews
 
 ### Current Approver Cohort
 * Communicating effectively as a leader (on GH and throughout project)
 * How to write better docs (release notes, etc.)
 * How to propose a new feature (features, design proposals)
+TODO: add more here
 
 ### Other Help Resources
 - slack
 	- #kubernetes-dev
-	- your respective sig or other sigs that could help 
-		- [SIG List](/sig-list.md) 
+	- your respective sig or other sigs that could help
+		- [SIG List]
 		- #sig-contribex
-	- #kubernetes-teachers
+	- #meet-our-contributors
+	- #pr-reviews
 - mailing lists
 	- kubernetes-dev@googlegroups.com
 	- your respective sig (ie - kubernetes-sig-cli@googlegroups.com)
 - contributor office hours
-	- Kubernetes Community Office Hours (need to create page; will update with link)
+	- Kubernetes Community Office Hours
 	- #office-hours on slack
 - the docs
-	- k/community is your friend for upstream workflows, processes, and information around contributing
-	- This repo includes the community/devel folder which will be extra helpful that includes docs such as:
-    - [Code Review Expectations](/contributors/guide/expectations.md)
-    - [Collaboration on k8s](/contributors/guide/collab.md)
-
-
-### Test Cohort Special Circumstances & Notes  
-* This is a group of current members working towards reviewership. If you are a current member and would like to participate, reach out to Paris on slack.
-* Since this is a predetermined group, the program may last two months instead of three. Expected completion date: end of February   
-
-
-Thank you to both mentees and mentors for taking on this new, unchartered territory! We will be building documentation around you and appreciate your guidance as a founding member of this program!
-
+	- kubernetes/community is your friend for upstream workflows, processes, and
+	information around contributing
+	- This repo includes the community/contributors/devel folder which will be
+	extra helpful that includes docs such as:
+    - [Code Review Expectations]
+    - [Collaboration on k8s]
+
+Thank you to both mentees and mentors for taking on this new, unchartered
+territory! We will be building documentation around you and appreciate your
+guidance as a founding member of this program!
+
+[community membership requirements doc]: /community-membership.md
+[SIG List]: /sig-list.md
+[Code Review Expectations]: /contributors/guide/expectations.md
+[Collaboration on k8s]: /contributors/guide/collab.md
diff --git a/mentoring/group-mentoring.md b/mentoring/group-mentoring.md
index 0126091f..7ee1c616 100644
--- a/mentoring/group-mentoring.md
+++ b/mentoring/group-mentoring.md
@@ -44,25 +44,7 @@ that cohort members need to check in with a predetermined status update
 * Exposure to multiple areas of the project making well-rounded contributors  
 * Mentors share time commitments and responsibilities  
 * Exposure to multiple mentors in an open and collaborative environment
-
-## Logistics
-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  
diff --git a/mentoring/meet-our-contributors.md b/mentoring/meet-our-contributors.md
index 61172ab7..0bc18fce 100644
--- a/mentoring/meet-our-contributors.md
+++ b/mentoring/meet-our-contributors.md
@@ -14,7 +14,7 @@ calendar to yours from [kubernetes.io/community]
 
 ## Where:  
 Follow along live:  
-[Kubernetes YouTube Channel](https://www.youtube.com/c/KubernetesCommunity/live)
+[Kubernetes YouTube Channel]
 
 Ask questions:
 #meet-our-contributors slack channel  
@@ -52,67 +52,37 @@ contributor, become a member, or otherwise contribute to the project
 * 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.
+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.
 
-### Code snip / PR for peer code review / Suggestion for part of codebase walk through:
+### Code snip / PR for peer code review / Suggestion for part of codebase walk
+through:
 * At least 24 hours before the session to Slack channel (#meet-our-contributors)
 
-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.
+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 Mentor Panelists!
 
 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/)
+* 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!
+
+
+
+[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)
+[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
diff --git a/mentoring/processes/README.md b/mentoring/processes/README.md
new file mode 100644
index 00000000..3460ac13
--- /dev/null
+++ b/mentoring/processes/README.md
@@ -0,0 +1 @@
+future home of all mentoring process documentation
diff --git a/mentoring/processes/group-mentoring.md b/mentoring/processes/group-mentoring.md
new file mode 100644
index 00000000..a6597990
--- /dev/null
+++ b/mentoring/processes/group-mentoring.md
@@ -0,0 +1,23 @@
+group-mentoring.md may have some other process info baked into the program info.
+
+## Logistics
+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.
diff --git a/mentoring/processes/hosting-moc.md b/mentoring/processes/hosting-moc.md
new file mode 100644
index 00000000..5a3dfd57
--- /dev/null
+++ b/mentoring/processes/hosting-moc.md
@@ -0,0 +1,35 @@
+## 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.
diff --git a/mentoring/programs/README.md b/mentoring/programs/README.md
new file mode 100644
index 00000000..bf954c8f
--- /dev/null
+++ b/mentoring/programs/README.md
@@ -0,0 +1,2 @@
+future home of mentoring programs, how to get involved, and other info for
+all contributors.