kubeflow · chasecadet · Feb 5, 2025 · Feb 5, 2025 · Feb 5, 2025 · Feb 7, 2025
diff --git a/KUBEFLOW-STEERING-COMMITTEE.md b/KUBEFLOW-STEERING-COMMITTEE.md
@@ -1,4 +1,5 @@
 # Kubeflow Steering Committee
+
 The Kubeflow Steering Committee (KSC) is the governing body of the Kubeflow project, providing decision-making and oversight pertaining to the Kubeflow project policies, sub-organizations, and financial planning, and defines the project values and structure.
 
 The governance of Kubeflow is an open, living document, and will continue to evolve as the community and project change.
@@ -16,6 +17,7 @@ The governance of Kubeflow is an open, living document, and will continue to evo
 ## Committee Meetings
 
 KSC currently meets at least bi-weekly, or as-needed. Meetings are open to the public and held online, unless they pertain to sensitive or privileged matters. Examples of such matters are:
+
 - Privacy related issues
 - Private emails to the committee
 - Code of conduct violations
@@ -29,23 +31,64 @@ Questions and proposals for changes to governance are posted as issues in the ku
 
 ## Committee members
 
-KSC is composed of 5 (five) members. They are elected according to the election policy [TODO: add link].  
-Seats on the Steering Committee are held by an individual, not by their employer.  
+KSC is composed of 5 (five) members. They are elected according to [the election policy](proposals/kubeflow-steering-committee-election-proposal.md).
+Seats on the Steering Committee are held by an individual, not by their employer.
 
 The current membership of the committee is (listed alphabetically by first name):
 
-| Name                | Organization | GitHub                                             | Term Start | Term End   |
-|---------------------|--------------|----------------------------------------------------|------------|------------|
-| Andrey Velichkevich | Apple        | [andreyvelich](https://github.com/andreyvelich/)   | 02/01/2024 | 02/01/2026 |
-| Johnu George        | Nutanix      | [johnugeorge](https://github.com/johnugeorge/)     | 02/01/2024 | 02/01/2026 |
-| Josh Bottum         | Independent  | [jbottum](https://github.com/jbottum/)             | 02/01/2024 | 02/01/2025 |
-| James Wu            | Google       | [james-jwu](https://github.com/james-jwu/)         | 02/01/2024 | 02/01/2025 |
-| Yuan Tang           | Red Hat      | [terrytangyuan](https://github.com/terrytangyuan/) | 02/01/2024 | 02/01/2026 |
-
+| Name                | Organization | GitHub                                                           | Term Start | Term End   |
+| ------------------- | ------------ | ---------------------------------------------------------------- | ---------- | ---------- |
+| Andrey Velichkevich | Apple        | [andreyvelich](https://github.com/andreyvelich/)                 | 02/01/2024 | 02/01/2026 |
+| Francisco Arceo     | Red Hat      | [franciscojavierarceo](https://github.com/franciscojavierarceo/) | 02/01/2025 | 02/01/2027 |
+| Johnu George        | Nutanix      | [johnugeorge](https://github.com/johnugeorge/)                   | 02/01/2024 | 02/01/2026 |
+| Julius von Kohout   | DHL          | [juliusvonkohout](https://github.com/juliusvonkohout/)           | 02/01/2025 | 02/01/2027 |
+| Yuan Tang           | Red Hat      | [terrytangyuan](https://github.com/terrytangyuan/)               | 02/01/2024 | 02/01/2026 |
 
 ## Emeritus Committee Members
 
-[This section will be populated when there are retired committee members.]
+| Name        | Organization | GitHub                                     | Term Start | Term End   |
+| ----------- | ------------ | ------------------------------------------ | ---------- | ---------- |
+| Josh Bottum | Independent  | [jbottum](https://github.com/jbottum/)     | 02/01/2024 | 02/01/2025 |
+| James Wu    | Google       | [james-jwu](https://github.com/james-jwu/) | 02/01/2024 | 02/01/2025 |
+
+## Ownership Transfer
+
+KSC members hold administrative ownership of Kubeflow assets. When new members of the KSC are elected,
+a GitHub issue must be created to facilitate the transfer to the incoming members.
+
+GitHub issue name:
+
+```
+Transfer Ownership to KSC 2025
+```
+
+GitHub issue content:
+
+- [ ] Update Kubeflow Steering Committee document with the new members and emeritus members.
+- [ ] Archive the current Slack channel (e.g. `#archived-ksc-2024`) and create the new Slack channel (e.g. `kubeflow-steering-committee`).
+- [ ] Schedule weekly calls with the new members.
+- [ ] Update [admins for Kubeflow GitHub org](https://github.com/kubeflow/internal-acls/blob/master/github-orgs/kubeflow/org.yaml#L7).
+- [ ] Update the [`kubeflow-steering-committee` GitHub team](https://github.com/kubeflow/internal-acls/blob/master/github-orgs/kubeflow/org.yaml).
+- [ ] Update approvers for the following OWNERS files (e.g the past members should be moved to `emeritus_approvers`):
+  - `kubeflow/kubeflow` [OWNERS file](https://github.com/kubeflow/kubeflow/blob/master/OWNERS).
+  - `kubeflow/community` [OWNERS file](https://github.com/kubeflow/community/blob/master/OWNERS).
+  - `kubeflow/internal-acls` [OWNERS file](https://github.com/kubeflow/internal-acls/blob/master/OWNERS).
+  - `kubeflow/website` [OWNERS file](https://github.com/kubeflow/website/blob/master/OWNERS).
+  - `kubeflow/blog` [OWNERS file](https://github.com/kubeflow/blog/blob/master/OWNERS).
+- [ ] Kubeflow GCP projects under `kubeflow.org` organization for ACLs and DNS management.
+  - Access for `kf-admin-cluster` GKE cluster in `kubeflow-admin` GCP project for the GitHub ACLs sync.
+  - Access for `kubeflow-dns` GCP project for the DNS management.
+- [ ] Access for Kubeflow GKE cluster `kf-ci-v1` in `kubeflow-ci` GCP project (No Organization)
+      where Prow is running.
+- [ ] Kubeflow [Google Group](https://groups.google.com/g/kubeflow-discuss).
+- [ ] Update members for [KSC Google Group](https://groups.google.com/a/kubeflow.org/g/ksc).
+- [ ] Access to Kubeflow `1password` account.
+- [ ] Kubeflow social media resources.
+  - Kubeflow [LinkedIn](https://www.linkedin.com/company/kubeflow/)
+  - Kubeflow [X](https://x.com/kubeflow).
+  - Kubeflow [Bluesky](https://bsky.app/profile/kubefloworg.bsky.social).
+  - [Kubeflow Community](https://www.youtube.com/@KubeflowCommunity) YouTube channel.
+  - [Kubeflow](https://www.youtube.com/@Kubeflow) YouTube channel.
 
 ## Decision process
 
@@ -54,6 +97,7 @@ The steering committee desires to always reach consensus.
 ### Normal decision process
 
 Decisions requiring a vote include:
+
 - Issuing written policy
 - Amending existing written policy
 - Accepting, or removing a Kubeflow component
@@ -70,19 +114,22 @@ Members of KSC may abstain from a vote. Abstaining members will only be consider
 ### Special decision process
 
 Issues that impacts the KSC governance requires a special decision process. Issues include:
+
 - Changes to the KSC charter
 - KSC voting rules
 - Election rules
 
 The issue may pass with 70% of the members (rounded up) of the committee supporting it.
 
 One organization may cast 1 vote. Votes cast by members from the same organization are equally weighted. Example:
+
 - If KSC is made up of employees from organizations A, A, B, C, D, each vote from organization A is weighted by a factor of 0.5. The total number of votes is 4, and 3 votes (70% rounded up) is required to pass a proposal. This rule is designed to remove organization A's ability to defeat a proposal that is supported by all other KSC members.
-- Similarly, if KSC is made up of employees from organizations A, A, B, B, C, the total number of votes is 3, and 2.5 votes is required to pass a proposal. 
+- Similarly, if KSC is made up of employees from organizations A, A, B, B, C, the total number of votes is 3, and 2.5 votes is required to pass a proposal.
 
 ### Results
 
 The results of the decision process are recorded and made publicly available, unless they pertain to sensitive or privileged matters. The results will include:
+
 - Description of the issue
 - Names of members who supported, opposed, and abstained from the vote.
 

diff --git a/OWNERS b/OWNERS
@@ -4,3 +4,9 @@ approvers:
   - juliusvonkohout
   - johnugeorge
   - terrytangyuan
+
+
+emeritus_approvers:
+  - james-jwu
+  - jbottum
+
diff --git a/README.md b/README.md
@@ -38,3 +38,7 @@ please reach out to [email protected].
 
 * [proposals](https://github.com/kubeflow/community/tree/master/proposals): Kubeflow design proposals
 * [how-to](https://github.com/kubeflow/community/tree/master/how-to): for documenting community and other project processes
+
+## Legal
+
+The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see [Trademark Usage](https://www.linuxfoundation.org/trademark-usage/).
diff --git a/calendar/calendar.yaml b/calendar/calendar.yaml
@@ -139,9 +139,9 @@
 
 - id: kf042
   name: Kubeflow Spark Operator Meeting
-  date: 10/18/2024
-  time: 4:00PM-5:00PM
-  frequency: every-4-weeks
+  date: 03/07/2025
+  time: 8:00AM-9:00AM
+  frequency: bi-weekly
   video: https://zoom.us/j/93870602975?pwd=NWFNT2xrZU03alVTTXFBTEsvdDdMQT09
   attendees:
     - email: [email protected]
@@ -453,7 +453,6 @@
       Zoom: Provided in meeting notes
   organizer: woop
 
-
 - id: kf034
   name: Kubeflow Security Team Call (US West/APAC)
   date: 12/19/2023
@@ -514,4 +513,4 @@
 
       Join with Phone (USA): +1 669 900 6833 or +1 646 558 8656
       International numbers: https://zoom.us/zoomconference?m=Os1EjlUlpb2_XUMaQ6dX1azqMK5CkfWH
-  organizer: thesuperzapper
+  organizer: thesuperzapper
diff --git a/how-to/join_kubeflow_ecosystem.md b/how-to/join_kubeflow_ecosystem.md
@@ -0,0 +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
+