sig cli & sig apps group contributor ladder cohort - reviewers

[parispittman]

this is not a group for new contributors - sorry y'all!
we are full as of July 12th. feel free to comment in case we have openings come up.

Timelines:

• selection: done
• kick off: maybe august 1st or 3rd
• weekly slack standup day: Monday (Apps) and Wednesday (CLI). Mentees must check-in during these days and mentors will be available to answer questions.
• session dates/times TBD [same as above]

Capacity:
6-10 for each group (12-20 total)
Mentee names:
sign up by providing your interest in below comments; acknowledge that you've read the requirements for mentees and understand the program guidelines] below.
-CLI-

• @iamNoah1
• @mpuckett159
• @mehabhalodiya
• @CIPHERTron
• @deejross
• @harshitasao
• @parul5sahoo
• @meghanajangi
• @AvineshTripathi
• @ardaguclu

-APPS-

• @atiratree
• @pravarag
• @valaparthvi
• @FillZpp
• @Namanl2001
• @helayoty
• @chetak123
• @feloy
• @Divya063
• @droslean

Mentors:
apps and/or cli: @soltysh @eddiezane @brianpursley
apps: @kow3ns @krmayankk
Contribex Coordinator(s): @Atharva-Shinde (cli) @PurneswarPrasad (apps) (@parispittman to advise)

Slack channel: created but not invited

Requirements for mentees:

• SIG-APPS: https://www.youtube.com/watch?v=AUNPLQVxvmw ,
  Basic knowledge about controllers(how to use and write controllers)
• SIG-CLI: https://www.youtube.com/watch?v=eZeCFRh2uGg&t=540s ,
  Basic knowledge about cli commands(how to use and write them)
• 2-3 hours a week
• commitment to stick around with us for at least 1 year post group training program (we're happy to have you - please stay longer!)
• GitHub org membership first step of contributor ladder
• member of SIGs slack channels, mailing lists, and attend meetings
• desire to work and learn in a group setting and help out peers on a similar journey; this is not a competition, we can take all of you if you make it through the program and have the support of current OWNERs

[parispittman]

/sig cli
/sig apps
/sig contributor-experience
/area mentorship-planning

[AvineshTripathi]

Hey @parispittman I am interested joining the group
Slack: Avinesh

[valaparthvi]

Thts is great!
I'm interested in being a part of this, but I don't have a preference about SIG group at the moment. I'm an existing member of the org, and relevant slack channels, and I should be able to commit 2-3 hours a week to this.
Slack Handle: valaparthvi (Parthvi Vala)

[pravarag]

Hi @parispittman , I'm interested in joinning the group as a reviewer. I've done some regular contributions towards sig-scheduling in projects like descheduler, kube-scheduler-simulator and sig-testing issues. I'm ready to commit at least 2-5 hours per week and would love to stick around for the mentioned duration of 1 year or more.
I've GitHub org membership and a part of SIGs slack channels and attend meetings.

Slack handle: pravarag (Pravar Agrawal)

[CIPHERTron]

Hello @parispittman 👋
I can fulfill the above mentioned requirements and would love to be a part of this cohort.

Slack handle: Pritish (Pritish Samal)

[harshitasao]

Hi @parispittman, I'm interested in being a part of this cohort and I will be able to fulfill the above requirements.

Slack Handle: Harshita Sao

[suryashekhawat]

Hey @parispittman, I'm interested in working with this cohort, I am new to oss would like to start with you all as a starting step.
[email: sing.shekhawat67@gmail.com]

[cailyn-codes]

Hi! I am interested in joining this cohort and can meet the stated requirements.

Slack Handle: cailyn_codes

[dani-santos-code]

Hi @parispittman, I'm also interested in joining this cohort and also can meet the listed requirements
Slack Handle: Daniele Santos

[parispittman]

@suryashekhawat @cailynse @dani-santos-code I don't see you in the GitHub Org unfortunately. Here is the contributor ladder that describes how to become an org member. You'll need at least 2 merged pull requests and 2 sponsors from different companies/independents. https://github.com/kubernetes/community/blob/master/community-membership.md#member

feel free to join #kubernetes-contributors on slack for help and guidance from all of us on getting to member

[dani-santos-code]

oh, sure. yeah! i missed one of the steps! will handle that first. thanks for the feedback, @parispittman . going through all the docs now. newbie in the house. sorry! 🙈

[pgadige]

Hello @parispittman I'm interested to participate in this mentorship initiative. I'm a newbie to Kubernetes project though. Do you think I'm still eligible to participate in this cohort?

[cailyn-codes]

@parispittman - Is it conceivable to try and achieve membership before this program kicks off? If not, how often do these opportunities arise?

[Atharva-Shinde]

Hi @pgadige you can get started contributing to Kubernetes by joining our slack! In order to be able to participate in this cohort you at least need to be an org-member. (@cailynse) If you are not a member do not worry :) there's always some or the other work new contributors like you can help us with which will help you in becoming an org-member.
I would focus more on engaging and contributing to the community.

tip❗️: if you aren't able to be a part of this cohort and you are interested in working with the sig-cli or sig-apps projects join their slack channels (#sig-cli , #sig-apps) on the kubernetes workspace and get involved!

[chetak123]

Hello @parispittman I have contributed in kubernetes-sigs in the past and I'm really interested in this program, I have also asked for some help to get github membership in slack channel https://kubernetes.slack.com/archives/C09R23FHP/p1654108446287059
I would be really grateful if someone can please help me in fulfilling the requirement for this program

Slack handle : Ayushman Mishra

[Namanl2001]

Hey @parispittman 👋
I fulfill all the requirements mentioned above and would love to be a part of this long journey with all other folks :) Thanks!

Slack handle: Naman Lakhwani

[dstrbad]

Ehlo, would like to join, understood requirements (although not yet GitHub org member). On slack dstrbad, interested in following SIGs: security, scheduling, instrumentation, cli. Following advice from Atharva-Shinde to be eligible for future cohort.

[meghanajangi]

Hello @parispittman ,
I can meet the listed requirements and would like to join this cohort.
Slack handle: MeghanaJangi

[parispittman]

hi @dstrbad @pgadige - once you are a member of the kubernetes org, you will be qualified for this. it is possible to become a member in time for this cohort (cc/ @cailynse) but will require you to pick up help wanted issues, join groups, submit PRs with at least two merged, gain two sponsors from different companies, and participate in the groups meetings. This process can take a few days to a few months depending on how familiar you are with open source projects in general and the time that you have to give to it.

[parispittman]

it would be best if you have been contributing to apps, cli, or another related group for this as being a reviewer requires some previous knowledge of how things work

[atiratree]

Hi @parispittman , I would like to sign up for this cohort with a preference for sig-apps and ackowledge the requirements.

[feloy]

Hello @droslean @feloy which sig do you want to participate in particular, sig-cli or sig-apps? You need to pick one (that interests you the most).

I'm more interested in sig-apps

[Atharva-Shinde]

@mitul3737 @rajibmitra @SaiHarshaK unfortunately we will not be moving forward with you THIS time. The reason maybe either not having a GitHub org-membership or not enough prior experience. Nevertheless there are still plenty of ways to get involved in the Kubernetes community, I have mentioned them below.

[Atharva-Shinde]

Thank you everyone for showing your interest in sig-cli and sig-apps group mentoring cohort for becoming reviewers.
(We had a huge number of interests this time)

We have finalised all the mentees for sig-cli & sig-apps and their GitHub handles are displayed in the issue description above. Congratulations everyone who got into the cohort!

If you unfortunately didn’t get in this cycle, we urge you to keep an eye out for similar cohort opportunities in future (which probably will be open to new contributors too).
Also, not getting into this cohort shouldn’t stop you from getting involved with Kubernetes. You can still get involved in cli/apps(or any other kubernetes sig/project for that matter) by joining their respective slack channels and their mailing lists, go through their readme files and resources, attend their meetings and start contributing!

And for all the mentees selected buckle up and get ready! We will put you up in private slack channels soon, till then go through the attached resources and get comfortable with the foundations of the projects.

[m-Bilal]

Hi, if you happen to get any new vacant spot somehow, I'm interested in being a part of sig-cli. I have read the requirements and the program guidelines.

Slack handle: m-Bilal

[rosspeoples]

@parispittman I would like to be on the sig-cli list as well, thanks!

[iamNoah1]

@parispittman @Atharva-Shinde @PurneswarPrasad any news here about the kick off date? Looking to plan my next weeks :) Also vacation wise 😅

[valaparthvi]

@parispittman @Atharva-Shinde @PurneswarPrasad any news here about the kick off date? Looking to plan my next weeks :) Also vacation wise sweat_smile

I remember it was somewhere around 15th August.

[Atharva-Shinde]

Hey @iamNoah1 and everyone here,
The kickoff is scheduled on August 3rd, we'll add you to your private slack channels shortly

[iamNoah1]

thanks for the info @Atharva-Shinde, looking forward ;)

[mpuckett159]

Were we supposed to have been added to those channels by now?

[Atharva-Shinde]

hello everyone,
I have added all the mentees in our private slack channels, if you didn't get in do comment here with your slack handle to avoid confusion

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[MadhavJivrajani]

/reopen
I'm assuming this isn't supposed to be "Not Planned"

[k8s-ci-robot]

@MadhavJivrajani: Reopened this issue.

In response to this:

/reopen
I'm assuming this isn't supposed to be "Not Planned"

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[MadhavJivrajani]

/remove-lifecycle rotten

[soltysh]

Actually this can be closed, since the sessions has completed with the end of 2022.

[ashutosh887]

@parispittman @Atharva-Shinde

I'm realy willing to be a part of the upcoming Cohort
Please keep me posted on it!

[mrbobbytables]

/close

The cohort concluded awhile ago

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

/close

The cohort concluded awhile ago

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.