Skip to content

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.

Sign up for GitHub

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

Open
franciscojavierarceo wants to merge 2 commits into
base: master
Choose a base branch
from
+236 −236
Open

chore: Update links for application to join Kubeflow #888

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7fe1e2d
chore: Update links
franciscojavierarceo Jul 29, 2025
152b8b6
Apply suggestion from @andreyvelich
franciscojavierarceo Sep 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
314 changes: 157 additions & 157 deletions how-to/join_kubeflow_ecosystem.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,157 +1,157 @@
# Application for a Project to Join the Kubeflow Ecosystem

Please see the [proposals/new-project-join-process.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
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

# Application for a Project to Join the Kubeflow Ecosystem
Please see the [proposals/748-expand-kubeflow-ecosystem.md](Documentation) to
Copy link
Member

@andreyvelich andreyvelich Jul 30, 2025 •
edited
Loading

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
....

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
Copy link
Member

@andreyvelich andreyvelich Jul 30, 2025

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.

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
Loading