# sig apps and sig cli reviewer group mentoring structure

each cohort will be separate. ie - 1 apps, 1 cli
every other week is a zoom meeting with special guest/mentor talk; opposite week is a slack stand up on [insert day of sig meeting]

contribex and sig:
- assign weeks to each bullet and guest speakers
- what do reviewers in each group need to be successful that we aren't hitting with the below structure?
- ID activities associated with each session
- examples:
- flaky tests
- developer guide updates
- contributor guide (sig) updates
- no session weeks will have expectations of 2-4 reviews

*Reviewer*
AUGUST 3RD
- reviewer qualifications to land in an OWNERs file
- first session

AUGUST 10TH
slack stand up

AUGUST 17TH
Mentors: Maciej,..
KUBECTL DEEP DIVE
- ideally a code walk through an then an example review walk through
- who owns what and why things are done the way they are
- pitfalls and challenges of current reviewers in that area

24TH
slack stand up

31ST
- Enhancements and Overview of Release Cycle
- guest speaker?
- timing - should this go first? whats the placement in the session schedule?

SEPT 7TH

- Reviewing code detailed walk thrus
- zoom weeks with no special guest - the mentor is the guest! youll go through your review backlog and talk out a live review via walk thrus for 30 minutes and do Q&A

- Triage
- understanding prow
- tools that are helpful
- working with new contributors
- words of wisdom from experienced maintainers

- API Changes
- do we need a special guest for this?

- Testing
- flaky tests are not fun
- fixing flaky tests should be

- Code Freeze and Cherry-Picks/Branch Management
- guest speaker?
- timing - should this go first? whats the placement in the session schedule?
- does this need to be separate from release overview?

SIG-CLI
Group subprojects
- kubectl
- kustomize
- cli-sdk
- cli-utils
- cli-experimental
- krew-index
- krm-functions
- kui (no active owners)

SIG-APPS
Topics to focus on:
- Controllers

Kick off template

1 - Thanks and Intros
- thank you so much for helping to grow the project in this way and to take on this responsibility! this is net positive for us AND you as we learn together.
- everyone should intro: where they work, why they are interested, the skills in the area that they have, hobbys, and anything else they would like to share

2 - Disclosures
- Understand that this is not a formally structured program but an esclated learning path.
- This is on you to complete and we are here to guide you. If there is a large foundational skill that you need to learn we will send you learning materials but may not be able to help past that
- You all are coming from different backgrounds and skill sets. You have a common goal though which is to be a reviewer. The most important part of the program is helping each other. Reviewers in Kubernetes are helpful people who guide new and current contributors so get used to it :)
- If at any point you can no longer do the work, feel free to drop out. This is not a school and you will not get a grade. Plenty of folks who have dropped out in the past still contribute on their own time.
- we will keep the private room open for 1-2 weeks post 3 months so you can gather any materials that you want to keep before we close the room and you move on to only public channels.

3 - Reviewership
Do you understand the requirements needed to be a reviewer? (pinned to slack; also - community membership doc)
- Go over requirements and pull up membership doc

4 - our governance
at reviewer level, you should start to learn more about how things work around here from a governance side - that is, how we make decisions and how the people aspect is managed. governance docs can be found in the community repo and steering committee repo. read up and ask us questions. if you would like a deep dive on something, ask us.
- the community repo is your friend and ally. read it and use it. communications.md is extremely important.

4 - Stand ups/Meetings/Logistics
- You are expected to go to SIG meetings and participate heavily in the SIG itself over the next few months.
- Standups will happen every Wednesday either in person on zoom or on slack. it will rotate and check the calendar and slack messages for reminders.
- We will have guests and mentors counsel on a subject/topic throughout the 3 months
- the group will not have its own email but you will participate on SIG mailing lists and dev@ lists as a regular contributor
- some meetings might be recorded if consent of all parties is there but will not be publicly distributed; only in the slack channel

6 - We have a code of conduct. This applies to all of us.
Should any issues arise, please reach out to [e-mail] or the contribex coordinator to talk further

7 - Open Q&A

8 - Suggestions/Feedback/Discussion