-
Notifications
You must be signed in to change notification settings - Fork 243
chore: Update links for application to join Kubeflow #888
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
base: master
Are you sure you want to change the base?
chore: Update links for application to join Kubeflow #888
Conversation
Signed-off-by: Francisco Javier Arceo <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
||
# Application for a Project to Join the Kubeflow Ecosystem | ||
|
||
Please see the [proposals/748-expand-kubeflow-ecosystem.md](Documentation) to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@franciscojavierarceo Can we transfer the process from KEP to this document ?
So folks don't need to read KEP to understand the process.
So this document look like this:
How to Become a Kubeflow Project
This document describes how open source projects can become a Kubeflow subproject.
The process outlined in the six steps:
- Create GitHub issues ...
- Provide demo ...
- Submit a Pull Request with the application form
....
Application Form
CNCF Checklist
Background info
....
In short, copy this Application Template and populate the document. | ||
|
||
|
||
## Changes to the application process |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's move this section to the end on this doc, since it is less important for readers.
Co-authored-by: Andrey Velichkevich <[email protected]> Signed-off-by: Francisco Arceo <[email protected]>
Update links