-
Notifications
You must be signed in to change notification settings - Fork 58
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
Deploying AI with with KubeFlow Blog Series #144
Comments
Current doc by Michael: https://docs.google.com/document/d/1GD2y6mOkSh4_q2s0x37eunuYizD3ofWHrPLEjMi4pqI/edit?usp=sharing |
Assigned |
Closing as won't do for now. |
Hi @zanetworker I want to contribute by writing the first part of the series or maybe more but that's depend on ongoing bandwidth I have on my hand for now, I can work on the first part. Could you please help me by directing to the relevant conversation/thread if we have any? And is it open for me to work on? I saw you assigned yourself then marked it as closed. Also, did we had any ToC (Table of Content) before Micheal wrote the draft? If not, I would love to understand what exactly we want to cover on this? |
@sudhanshu456 Michael wanted to start off a series on Applied AI through the lens of KubeFlow as one of the well-documented projects the community. If you'd like to take a stab at continuing this work, let me know. Previous work can be found here: https://docs.google.com/document/d/1GD2y6mOkSh4_q2s0x37eunuYizD3ofWHrPLEjMi4pqI/edit?usp=sharing |
@zanetworker the google doc link you shared it's saying |
Looks like the author closed the doc (sorry about that). @sudhanshu456 If you would like to start a new doc and a new issue, please feel free to do that. |
Thanks @zanetworker. I will go through the past threads to get more context around this and will share the ToC and plan accordingly. |
This is to track progress on the blog series for deploying AI with KubeFlow.
The text was updated successfully, but these errors were encountered: