Implementation:Kubeflow Kubeflow Slack Working Group Engagement
| Knowledge Sources | |
|---|---|
| Domains | Community, Governance, Communication |
| Last Updated | 2026-02-13 00:00 GMT |
Overview
Concrete pattern for engaging with the Kubeflow community provided by Slack channels, Working Group meetings, and governance structures documented in the kubeflow/community repository.
Description
Kubeflow's community engagement infrastructure consists of three interconnected systems: the Kubeflow Slack workspace for real-time communication, Working Group (WG) meetings for synchronous coordination, and the kubeflow/community repository for governance documentation and meeting records.
The Slack workspace is organized around Working Group-specific channels, allowing contributors to engage directly with the teams responsible for the component they want to contribute to. Working Group meetings follow a regular cadence and are open to all contributors, providing a forum for discussing roadmap items, reviewing design proposals, and coordinating development efforts.
The README.md "Kubeflow Community" section (lines 55-62) serves as the entry point, directing contributors to the community page on kubeflow.org, which aggregates links to Slack channels, meeting schedules, and governance documents.
Usage
Use this engagement pattern when:
- Joining the Kubeflow community for the first time and seeking orientation.
- Preparing to make a significant contribution and needing alignment with a Working Group.
- Looking for mentorship or guidance on a specific component.
- Wanting to understand the current state of a feature or roadmap item before beginning work.
- Seeking feedback on a design proposal or architectural decision.
Code Reference
Source Location
- Repository: kubeflow/kubeflow
- File:
README.md(Lines 55-62, "Kubeflow Community" section)
Signature
## Kubeflow Community
The Kubeflow Community page provides information on the governance structure,
community meetings, Slack channels, and other community resources.
Visit the Kubeflow Community page:
https://www.kubeflow.org/docs/about/community/
Import
# Join the Kubeflow Slack workspace
# Navigate to the community page for the Slack invite link:
xdg-open https://www.kubeflow.org/docs/about/community/#kubeflow-slack-channels
# Clone the community repository for governance docs and meeting notes:
git clone https://github.com/kubeflow/community.git
I/O Contract
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
| Target sub-project | string | Yes | The Kubeflow component the contributor intends to work on (e.g., Pipelines, Katib, Notebooks). |
| Contribution intent | string | Yes | Description of the planned contribution (bug fix, feature, documentation) to help WG leads provide relevant guidance. |
| Contribution guidelines knowledge | boolean | Yes | Contributor should have reviewed the canonical contributor guide before engaging with the community. |
Outputs
| Name | Type | Description |
|---|---|---|
| Community context | Knowledge | Understanding of project priorities, in-progress work, and technical direction for the target component. |
| Working Group alignment | Agreement | Confirmation from WG leads that the planned contribution aligns with project goals and is not duplicating existing efforts. |
| Mentor/reviewer contacts | Contact list | Identification of specific maintainers who can review and guide the contribution. |
| Project priorities understanding | Knowledge | Awareness of the current roadmap, release schedule, and areas where contributions are most needed. |
Usage Examples
Example: New Contributor Onboarding
# Step 1: Join the Kubeflow Slack workspace
# Visit: https://www.kubeflow.org/docs/about/community/#kubeflow-slack-channels
# Click the Slack invite link and create an account
# Step 2: Join relevant channels
# #general - Project-wide announcements and discussions
# #wg-pipelines - Kubeflow Pipelines working group
# #wg-training - Training operators (Trainer, MPI Operator)
# #wg-notebooks - Kubeflow Notebooks working group
# #wg-serving - KServe and model serving
# #wg-manifests - Kubeflow Manifests and deployment
# Step 3: Introduce yourself in #general or the relevant WG channel
# Example message:
# "Hi! I'm interested in contributing to Kubeflow Pipelines.
# I've read the contributor guide and found issue #1234 that
# I'd like to work on. Is anyone currently working on this?"
Example: Preparing a Feature Contribution
# Step 1: Review the community repository for governance docs
git clone https://github.com/kubeflow/community.git
ls community/wgs/ # List Working Groups
# Step 2: Find the relevant Working Group meeting schedule
# Meeting schedules are documented in each WG's directory
# under the community repository
# Step 3: Attend a WG meeting to present your proposal
# Meetings are typically held via video call (Zoom)
# Add your topic to the meeting agenda doc before attending
# Step 4: Create a design document if the feature is significant
# Share the design doc in the WG Slack channel for async review
# Iterate on feedback before beginning implementation
Example: Finding Good First Issues
# Search for beginner-friendly issues across Kubeflow repositories
# Visit the GitHub issues page with "good first issue" label:
xdg-open "https://github.com/kubeflow/kubeflow/labels/good%20first%20issue"
# Or ask in Slack for recommendations:
# "Looking for a good first issue in Kubeflow Notebooks.
# Can anyone point me to something appropriate for a new contributor?"