cncf / mentoring

👩🏿‍🎓👨🏽‍🎓👩🏻‍🎓CNCF Mentoring: LFX Mentorship + Summer of Code
https://mentoring.cncf.io
Apache License 2.0
2.29k stars 600 forks source link

Add Kubernetes LFX project idea for Jun-Aug 2024 #1223

Closed mehabhalodiya closed 1 month ago

mehabhalodiya commented 1 month ago

Project for upcoming summer session related to KEP versioning in Kubernetes. FYI SIG Release and SIG architecture are closely involved and affected here.

cc @marosset @katcosgrove

katcosgrove commented 1 month ago

+1 on behalf of the Release Team subproject! This is a problem that impacts Release Enhancements, as well as PRR reviewers/approvers and KEP owners. We would love to see some motion here.

nate-double-u commented 1 month ago

Thanks for this @mehabhalodiya & @marosset!

@marosset, could you 👍 or approve this PR to confirm your participation?

Also, since this is a proposal for a Kubernetes project, I think we'll need the sig-contribex leads approval as well. Usually we'd require a project maintainer's approval, but things are a touch different with K8s projects and subprojects. I believe the chairs are currently: @kaslin & @palnabarun, if you could both take a look 🙂

aliok commented 1 month ago

@mehabhalodiya Thanks for the proposal.

I understand that this needs to be done, but it is a lot of manual work and I am not so sure if a mentee would learn adequate skills in a mentorship.

Is there any automation involved? Or, any programmatic approach to validate KEPs against templates?

marosset commented 1 month ago

+1 I'd be happy to help mentor @mehabhalodiya on these projects. I have experience as both a KEP author and as an enhancement lead and feel strongly that this work would help the community and project!

nate-double-u commented 1 month ago

@mehabhalodiya Thanks for the proposal.

I understand that this needs to be done, but it is a lot of manual work and I am not so sure if a mentee would learn adequate skills in a mentorship.

Is there any automation involved? Or, any programmatic approach to validate KEPs against templates?

Related: is this project big enough? The program is a 12-week, full-time program. Is there enough to keep a candidate engaged for 12 weeks (32-40 hours per week)?

kaslin commented 1 month ago

If @marosset and @katcosgrove are onboard, I'm all for it. Mark, you mentioned mentoring Meha on this. Do you think it will meet @nate-double-u's requirements for the program?

nate-double-u commented 1 month ago

To clarify:

+1 I'd be happy to help mentor @mehabhalodiya on these projects.

@mehabhalodiya and @marosset, you would be co-mentors mentoring a candidate you select from the applicants on the LFX platform. @mehabhalodiya can't be both mentor and mentee in this case.

mehabhalodiya commented 1 month ago

@mehabhalodiya can't be both mentor and mentee in this case.

Yes, I am aware of this. So about meeting the requirements of the program, it will be like Mark will be the primary mentor as he has the full knowledge of working with Enhancements and some other related concepts while me being familiar with the Kubernetes community and the Release process, hence I will be secondary. Both together put up our own experience to help the mentee, who will be new to Kubernetes and the open source community.

I hope this answers your question @kaslin @nate-double-u 🙂

mehabhalodiya commented 1 month ago

Related: is this project big enough? The program is a 12-week, full-time program. Is there enough to keep a candidate engaged for 12 weeks (32-40 hours per week)?

Yes, I believe it would be fine assuming the mentee would be new to understanding the KEP process and the related concepts involved in the Kubernetes release. Further implementing what we need includes several loops of feedback and modifications. This will consume much time, so IMO 12 weeks is good for all of us (mentee, mentor, and the community folks).

kaslin commented 1 month ago

I love that idea! As long as Mark agrees on everything, I approve.

xmudrii commented 1 month ago

Related: is this project big enough? The program is a 12-week, full-time program. Is there enough to keep a candidate engaged for 12 weeks (32-40 hours per week)?

Speaking from the experience, yes, it is enough. SIG Release processes take some to get along with, we had great success in Sept-Nov term, but it's definitely something to keep in mind. With that, and with getting along with KEP processes, making eventual proposal, and doing the implementation, I think 12 week, full-time, is enough to keep the mentee busy and engaged for the whole 12 weeks.

kikisdeliveryservice commented 1 month ago

Hi all,

There's some current in-progress work that has been done very recently by another contributor. I'm checking to see if the project would have enough work for an intern or if there might be some other substantive alternative.

varshith257 commented 1 month ago

@kikisdeliveryservice I can't see any PR work in the repo of this WIP. Can you clarify it?

varshith257 commented 1 month ago

@mehabhalodiya @marosset I am ready to grab this opportunity to work under your guidance. I am new to k8s but completed bootcamp and a done project on it now I have a strong command of k8s working and architecture. I enjoyed learning k8s, exploring it, and looking for an opportunity to use my skills and abilities.

I recently heard about LFX Mentorship and exploring the projects going to add for this season. Got this cool project coming to this mentorship season.

I have seen the upstream issue and it seems to help the enhancements team which is a needed enhancement. Hope this project will be added to this mentorship season.

katcosgrove commented 1 month ago

After further review, it has come to light that an individual within the Release Team is already actively working on this problem, with significant progress and a proof of concept in flight. There is no longer enough work to justify the inclusion of an intern. With my official hat on, I suggest this PR be closed.

cc: @mehabhalodiya

nate-double-u commented 1 month ago

After further review, it has come to light that an individual within the Release Team is already actively working on this problem, with significant progress and a proof of concept in flight. There is no longer enough work to justify the inclusion of an intern. With my official hat on, I suggest this PR be closed.

Thanks for following up on that @katcosgrove and @kikisdeliveryservice. Given there's not enough work in this project for a candidate for this program, I agree that we'll decline this project proposal.

Thanks everyone for the effort, and @mehabhalodiya & @marosset for being willing to mentor!