-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request to be User Group Contributor for Kubeflow 1.5 for the AutoML Working Group #1747
Comments
Hi @anencore94, thank you for your interest and help with Kubeflow projects! If you are available, let's discuss in our AutoML Community Meeting on December 1st the Katib issues that you would like to work on. |
@andreyvelich Thank you for saying so. However, I'm sorry I couldn't make to attend the Metting on December 1st. |
Sure, sounds good @anencore94. |
First of all, I'd like to work on #1207, maybe I could collaborate with #1708. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
Hello guys, I'm a MLOps Engineer at MakinaRocks in South Korea. (I have CKA and my company have KCSP certification) We've used kubeflow to try and share ML experiments easily.
I've used Kubernetes since 2020 and Kubeflow since 2021 in production level.
My experience with Kubeflow includes:
I'd like to see release process of kubeflow, and give any help if I could do.
If you guys are ok, I'd like to collaborate with you guys and other User Group Contributors like #1745
cc @kubeflow/wg-automl-leads
Please let me know if you need more information!
The text was updated successfully, but these errors were encountered: