[RELEASE] Assemble the 1.10 Release Team

[rimolive]

With Kubeflow 1.9 being released it is time to assemble the Kubeflow 1.10 Release Team!

I would like to say thank you for the opportunity to work on a release and I really enjoyed being part of a brilliant team. Right now I don't have any nominations for the next Release Manager to lead the 1.10 Kubeflow Release. I would like to introduce one more role in this next Release Team to prepare the next 1.11 Release Team: The Release Manager shadowing. As for now, I'd like to nominate @tarilabs for the Release Manager shadowing. @tarilabs as the Model Registry lead proved that he has all the leadership skills to handle the future Kubeflow releases, but it's important for him to work along with someone with more experience to prepare himself for future releases.

The release manager role hasn't been decided, and it's still open for anyone in the community.

With that, I would also like to encourage everyone to participate in the 1.10 Release Team! The Release Team welcomes both new and existing members of the Kubeflow community and is a great way to get started with the project.

You can learn more about the Kubeflow release process and the release team in the release handbook.

To be part of the release team, please leave a comment with which working group you like to be assigned to. We look forward to your involvement!

cc @kubeflow/wg-automl-leads @kubeflow/wg-data-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-training-leads @kubeflow/wg-manifests-leads @kubeflow/kubeflow-steering-committee @StefanoFioravanzo

[tarilabs]

I volunteer as liaison for the Model Registry WG,
and I candidate/volunteer as 1 of the Release mgr shadows.

[juliusvonkohout]

I volunteer for platform.

[diegolovison]

I volunteer for docs.

[milosjava]

I volunteer for MR liaison if Mateo wants to focus only on release manager shadow position

[juliusvonkohout]

Since you asked @rimolive, I can be co-releasemanager with more or less the same effort that i spent in the 1.9 cycle.

[Tob-iee]

I would like to volunteer for docs as well

[SiverJohn]

I volunteer to fulfill any position where I can be of most use.

[juliusvonkohout]

I would like to volunteer for docs as well

As many documentation writers and testers as we can get :-)

[tarekabouzeid]

I would like to volunteer for Platform WG liaison

[tombuuz]

I can contribute in documentation and testing.

[lizvladi-ds]

I would like to join as a release team member. My current position is MLOps at a company that has KubeFlow-based ML-platform.

[thesuperzapper]

Hey everyone, please remember you have to be an active member of kubeflow to be on the release team.

If you're not already a member, feel free to share what areas you're able to contribute (in terms of code), and we can connect you you with a working group in need.

For example, if you have experience with Go programming (or React JS), I have a big need in the Notebooks WG. We are currently working on Notebooks 2.0 (kubeflow/kubeflow#7156).

[mcruzdev]

I'd like to contribute to the release team. If that's not possible, I'd be happy to help with GoLang and ReactJS @thesuperzapper

[thesuperzapper]

@mcruzdev Kubeflow 1.10 is still a while away, so there is time to get your org membership and join the release team!

Let's connect on the CNCF Slack (slack name: Mathew Wicks), and we can you find some critical tasks to help get Notebooks 2.0 shipped, which will absolutely count towards the contribution requirements of membership.

For example we still need someone to pick up this issue (requires KubeBuilder/Golang experience):

• Notebooks 2.0 // Controller // Implement VirtualService reconciliation  notebooks#37

PS: other people watching this thread with Go/React experience are encouraged to message me on Slack too.

[andreyvelich]

Thanks @Tob-iee @SiverJohn @tarekabouzeid @tombuuz @lizvladi-ds @mcruzdev for volunteering to be on the Kubeflow 1.10 release team!

In addition to the @thesuperzapper's comments, you can start contributing to Kubeflow ecosystem by looking into issues with good-first-issue label.
Usually, those issues are relatively easy to solve and you can start your contributions for the Kubeflow projects.

For example:

• Training Operator good first issues.
• Katib good first issues.
• Pipelines good first issue.

Additionally, I would suggest you to join the Kubeflow community calls and the Kubeflow release team calls to show your interest being on the Kubeflow release team.

[saileshd1402]

I would like to join the release team. I can volunteer to be the Training Operator and Katib WG liaison.

[rimolive]

@saileshd1402 @mcruzdev @lizvladi-ds @tombuuz @tarekabouzeid @SiverJohn @Tob-iee Please join the next Release Team meeting on September 9th. You can find details in https://www.kubeflow.org/docs/about/community/#kubeflow-community-calendars

[varodrig]

Hi, I'm interested in the Release Manager role please let me know next steps. I'll be joining Monday's meeting.

[anencore94]

Hi, Unless I'm not late, I'd like to join as a training or notebooks or automl WG. @rimolive

[biswassri]

@rimolive I'm interested in joining too. Unfortunately I missed the meeting but any chance there is more position available?

[mvlassis]

@rimolive Hello everyone! I'd like to participate as a liaison for the Notebooks WG, and as a point of contact for the Charmed Kubeflow distribution.

[omarsumadi]

Hey folks. I'd be happy to take up the Release Product Manager role. cc @StefanoFioravanzo. I'll attend the Release Team Meeting on Monday.