chore: Update links for application to join Kubeflow #888
+236
−236
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,157 +1,157 @@ | ||
| # How to Become a Kubeflow Subproject | ||
| Please see the [proposals/748-expand-kubeflow-ecosystem.md](Documentation) to | ||
| better understand the full process for submitting a new project. | ||
| In short, copy this Application Template and populate the document. | ||
| ## Changes to the application process | ||
|
There was a problem hiding this comment. Let's move this section to the end on this doc, since it is less important for readers. |
||
| Changes to the application process charter may be proposed through a Pull Request | ||
| on this document by a Kubeflow community member. | ||
| Amendments are accepted following the Kubeflow Steering Committee's [Normal Decision Process](../KUBEFLOW-STEERING-COMMITTEE.md#normal-decision-process). | ||
| Proposals and amendments to the application process are available for at | ||
| least a period of one week for comments and questions before a vote will occur. | ||
| ## CNCF Short Checklist | ||
| - [ ] All project metadata and resources are vendor-neutral | ||
| - [ ] Governance structure | ||
| - [ ] Contributing guides | ||
| - [ ] Public list of adopters | ||
| ## Background information | ||
| 1. Submitter Name | ||
| - | ||
| 1. Submitter’s relationship to project / title | ||
| - | ||
| 1. Project Name | ||
| - | ||
| 1. Why is this project is valuable to the Kubeflow Community? | ||
| - | ||
| 1. Why is it beneficial for this project to be a part of the Kubeflow Community? | ||
| - | ||
| 1. List of existing (and potential) integrations with Kubeflow Core components | ||
| - | ||
| 1. Short Description / Functionality | ||
| - | ||
| 1. Adoption | ||
| - | ||
| 1. License Agreement | ||
| - | ||
| 1. Part of an Open Source Foundation? (e.g., Apache, Liniux, CNCF, etc.) | ||
| - | ||
| 1. Vendor Neutrality | ||
| - | ||
| 1. Trademark transition | ||
| - | ||
| 1. CI/CD Infra Requirements | ||
| - | ||
| 1. Governance Structure | ||
| - | ||
| 1. Website | ||
| - | ||
| 1. GitHub repository | ||
| - | ||
| 1. 1st Release date | ||
| - | ||
| 1. Project Meeting Times | ||
| - | ||
| 1. Meeting Notes | ||
| - | ||
| 1. Installation Documentation | ||
| - | ||
| 1. Project Documentation | ||
| - | ||
| 1. Security Profile (CVE scanning, Pod Security Standards, Network Policies) | ||
| - | ||
| 1. Ownership / Legal Profile (license type, any potential issues for CNCF) | ||
| - | ||
| 1. Authorization, Isolation mechanisms | ||
| - | ||
| 1. Project Roadmap | ||
| - | ||
| 1. Other Information | ||
| - | ||
| ## Metrics | ||
| - Number of Maintainers and their Affiliations | ||
| - Number of Releases in last 12 months | ||
| - Number of Contributors | ||
| - Number of Users | ||
| - Number of Forks | ||
| - Number of Stars | ||
| - Number of package/project installations/downloads | ||
| ## Kubeflow Checklist | ||
| 1. Overlap with existing Kubeflow projects | ||
| - [ ] Yes (If so please list them) | ||
| - [ ] No | ||
| 1. Manifest Integration | ||
| - [ ] Yes | ||
| - [ ] No | ||
| - [ ] Planned | ||
| 1. Commitment to Kubeflow Conformance Program | ||
| - [ ] Yes | ||
| - [ ] No | ||
| - [ ] Uncertain | ||
| 1. Installation | ||
| - [ ] Standalone/Self-contained Component | ||
| - [ ] Part of Manifests | ||
| - [ ] Part of Distributions | ||
| 1. Installation Documentation (Current Quality) | ||
| - [ ] Good | ||
| - [ ] Fair | ||
| - [ ] Part of Kubeflow | ||
| 1. CI/CD | ||
| - [ ] Yes | ||
| - [ ] No | ||
| 1. Release Process | ||
| - [ ] Automated | ||
| - [ ] Semi-automated | ||
| - [ ] Not Automated | ||
| 1. Kubeflow Website Documentation | ||
| - [ ] Yes | ||
| - [ ] No | ||
| 1. Blog/Social Media | ||
| - [ ] Yes | ||
| - [ ] No | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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:
....
Application Form
CNCF Checklist
Background info
....