|
| 1 | +# WG ML Experience |
| 2 | + |
| 3 | +This charter adheres to the conventions, roles, and organisation management outlined in [wg-governance] for the Working Group "ML Experience". |
| 4 | + |
| 5 | +## Scope |
| 6 | + |
| 7 | +The ML Experience Working Group focuses on developing, maintaining, and improving tools and extensions that support data science and machine learning practitioners experiences within Kubeflow. The group is dedicated to delivering a high-level, seamless experience integrated with the IDE of choice across multiple Kubeflow components. |
| 8 | + |
| 9 | +### In scope |
| 10 | + |
| 11 | +#### Code, Binaries, and Other relevant assets |
| 12 | + |
| 13 | +1. Development of Kubeflow JupyterLab extensions that provide simple abstractions and UX to interact with the most common Kubeflow components (e.g., pipelines, hyperparameter tuning) and shorten the time to value for practitioners comfortable with Jupyter. These extensions will focus on the most used Kubeflow components, such as: |
| 14 | + - Pipelines; |
| 15 | + - Kubeflow Trainer |
| 16 | + - Kubeflow Katib |
| 17 | + - Model Registry; |
| 18 | + - Model Serving (KServe); |
| 19 | + - Feast. |
| 20 | + |
| 21 | +2. Promote the reusability of UI components from other Kubeflow UIs into the IDE (e.g., rendering a pipeline graph inside the JupyterLab environment) by establishing a shared contract between the IDE WG and the wider Kubeflow community. |
| 22 | + |
| 23 | +3. Develop a Python SDK to simplify operationalization across Kubeflow components and provide a “one-stop-shop” for practitioners who want easy access to Kubeflow services. The SDK also provides the groundwork for the IDE extension automation and workflows. |
| 24 | + - Create a single installation and configuration layer for users interacting programmatically with the Kubeflow ecosystem via SDKs. |
| 25 | + - The “common” SDK is not meant to replace individual components’ SDKs but rather to offer a unified access layer to simplify dependency management and shared configuration (like authorization). |
| 26 | + |
| 27 | +#### Guiding Principles |
| 28 | + |
| 29 | +- Synergy among Kubeflow Working Groups: Collaborate with other WG to promote reusability of UI components from other Kubeflow UIs to create a single UX between Jupyter IDE and Kubeflow Central Dashboard; |
| 30 | +- Collaboration with other open-source IDE projects (like Jupyter and VSCode) to promote the creation and reusability of open standards for AI/ML tools (protocols, communication exchange, file formats, etc.) and plugins. The aim of this group is to actively participate in the development of these standards to include Kubeflow in a broader ecosystem or interoperable tools. |
| 31 | + |
| 32 | +#### Cross-cutting and Externally Facing Processes |
| 33 | + |
| 34 | +- Collaboration with other Kubeflow WGs, including WG Notebooks, WG Pipelines, WG Training, WG AutoML, WG Data, and WG Serving, ensures that IDE tools are interoperable across different stages of the ML lifecycle. |
| 35 | +- Coordination with the release teams to align updates in IDE tools with broader Kubeflow release schedules. |
| 36 | + |
| 37 | + |
| 38 | +### Out of scope |
| 39 | + |
| 40 | +- Building and maintaining Notebook/Workspaces images (this falls under the WG Notebooks). |
| 41 | + |
| 42 | +## Roles and Organization Management |
| 43 | + |
| 44 | +This WG adheres to the Roles and Organization Management outlined in [wg-governance] and opts-in to updates and modifications to [wg-governance]. |
| 45 | + |
| 46 | +### Additional responsibilities of Chairs |
| 47 | + |
| 48 | +- Coordinating and facilitating discussions on ML experience topics in scope of the WG, within the WG itself and the Kubeflow community. |
| 49 | +- Ensuring alignment with overall Kubeflow goals and objectives in the context of user experience to data scientists and machine learning practitioners on Kubeflow. |
| 50 | + |
| 51 | +### Additional responsibilities of Tech Leads |
| 52 | + |
| 53 | +- Providing technical guidance and mentorship to contributors working on Kubeflow JupyterLab extensions, SDK, and the projects in scope of this WG. |
| 54 | +- Overseeing the technical direction of the subprojects and ensuring consistency with Kubeflow's vision for Kubeflow ML Experience. |
| 55 | + |
| 56 | +### Deviations from [wg-governance] |
| 57 | + |
| 58 | +This WG follows the outlined roles and governance in [wg-governance]. |
| 59 | + |
| 60 | +### Subproject Creation |
| 61 | + |
| 62 | +WG Technical Leads |
| 63 | + |
| 64 | +[wg-governance]: ../wgs/wg-governance.md |
0 commit comments