From fba2815469b9e9c0b1bac77113eb1594cef16f6d Mon Sep 17 00:00:00 2001 From: DominikKawka Date: Mon, 13 Apr 2026 15:32:10 +0100 Subject: [PATCH 1/5] Added non-code contributions header in contributing.md Signed-off-by: DominikKawka --- content/en/docs/about/contributing.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/en/docs/about/contributing.md b/content/en/docs/about/contributing.md index aa7d2c3a2f..fafec32755 100644 --- a/content/en/docs/about/contributing.md +++ b/content/en/docs/about/contributing.md @@ -5,7 +5,7 @@ weight = 20 aliases = ["/docs/contributing/"] +++ -This document is the single source of truth for how to contribute to the code base. +This document is the single source of truth for how to contribute to Kubeflow. We'd love to accept your patches and contributions to this project. There are just a few small guidelines you need to follow. @@ -95,6 +95,12 @@ To ensure smooth collaboration and avoid duplicate work, please follow these gui Following these guidelines helps maintain a collaborative and efficient community, reduces wasted effort, and ensures everyone's contributions are valued. +### Non-code contributions + +- **Documentation**: Improve the accuracy and clarity of our technical docs by fixing stale information and ensuring all new content follows the standards set in the [Kubeflow Documentation Style Guide](style-guide.md). +- **Blog posts and user stories**: Share your technical insights or success stories on the Kubeflow blog to help the community learn from real-world use cases. +- **Event outreach**: Help spread awareness by speaking at events, and representing Kubeflow at community booths. + ## Owners files and PR workflow Our PR workflow is nearly identical to Kubernetes'. From a29832cac00e2d798bbadda19452b4c2772b7404 Mon Sep 17 00:00:00 2001 From: Valentina Rodriguez Sosa Date: Wed, 20 May 2026 09:29:39 -0400 Subject: [PATCH 2/5] Update contributing.md Signed-off-by: Valentina Rodriguez Sosa --- content/en/docs/about/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/about/contributing.md b/content/en/docs/about/contributing.md index fafec32755..cb44758c03 100644 --- a/content/en/docs/about/contributing.md +++ b/content/en/docs/about/contributing.md @@ -98,7 +98,7 @@ Following these guidelines helps maintain a collaborative and efficient communit ### Non-code contributions - **Documentation**: Improve the accuracy and clarity of our technical docs by fixing stale information and ensuring all new content follows the standards set in the [Kubeflow Documentation Style Guide](style-guide.md). -- **Blog posts and user stories**: Share your technical insights or success stories on the Kubeflow blog to help the community learn from real-world use cases. +- **Blog posts**: Share your technical insights or success stories on the Kubeflow blog or CNCF about Kubeflow to help the community to gain more knowledge on kubeflow. These content can take different forms from learn from real-world use cases, Kubeflow integrations, news about releases or practical use cases. - **Event outreach**: Help spread awareness by speaking at events, and representing Kubeflow at community booths. ## Owners files and PR workflow From f26be9996d8b0343621acdd2682fcdd01d1dba27 Mon Sep 17 00:00:00 2001 From: Valentina Rodriguez Sosa Date: Wed, 20 May 2026 09:31:09 -0400 Subject: [PATCH 3/5] Update event outreach contribution guidelines Clarified the description of event outreach contributions to include more specific activities. Signed-off-by: Valentina Rodriguez Sosa --- content/en/docs/about/contributing.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/about/contributing.md b/content/en/docs/about/contributing.md index cb44758c03..be90b17d47 100644 --- a/content/en/docs/about/contributing.md +++ b/content/en/docs/about/contributing.md @@ -99,7 +99,8 @@ Following these guidelines helps maintain a collaborative and efficient communit - **Documentation**: Improve the accuracy and clarity of our technical docs by fixing stale information and ensuring all new content follows the standards set in the [Kubeflow Documentation Style Guide](style-guide.md). - **Blog posts**: Share your technical insights or success stories on the Kubeflow blog or CNCF about Kubeflow to help the community to gain more knowledge on kubeflow. These content can take different forms from learn from real-world use cases, Kubeflow integrations, news about releases or practical use cases. -- **Event outreach**: Help spread awareness by speaking at events, and representing Kubeflow at community booths. +- **Event outreach**: Contribute to outreach activities by bringing awareness of kubeflow with activities such as: +speaking at events, representing Kubeflow at community booths/tables, helping organize an event, Program committee or Program Chairs. ## Owners files and PR workflow From 8af6869cdd3537beec86913e978517799cb8436d Mon Sep 17 00:00:00 2001 From: Valentina Rodriguez Sosa Date: Wed, 20 May 2026 13:47:03 -0400 Subject: [PATCH 4/5] Improve clarity in documentation contribution guidelines Clarified the documentation contribution guidelines by rephrasing the sentence for better readability. Signed-off-by: Valentina Rodriguez Sosa --- content/en/docs/about/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/about/contributing.md b/content/en/docs/about/contributing.md index be90b17d47..95349e86f0 100644 --- a/content/en/docs/about/contributing.md +++ b/content/en/docs/about/contributing.md @@ -97,7 +97,7 @@ Following these guidelines helps maintain a collaborative and efficient communit ### Non-code contributions -- **Documentation**: Improve the accuracy and clarity of our technical docs by fixing stale information and ensuring all new content follows the standards set in the [Kubeflow Documentation Style Guide](style-guide.md). +- **Documentation**: Contribute to technical documentation by improving the accuracy and clarity of Kubeflow technical documentation and/or fixing stale information and ensuring all new content follows the standards set in the [Kubeflow Documentation Style Guide](style-guide.md). - **Blog posts**: Share your technical insights or success stories on the Kubeflow blog or CNCF about Kubeflow to help the community to gain more knowledge on kubeflow. These content can take different forms from learn from real-world use cases, Kubeflow integrations, news about releases or practical use cases. - **Event outreach**: Contribute to outreach activities by bringing awareness of kubeflow with activities such as: speaking at events, representing Kubeflow at community booths/tables, helping organize an event, Program committee or Program Chairs. From 78d58c71f47e94ae713836b908918ca120f0ad5a Mon Sep 17 00:00:00 2001 From: Valentina Rodriguez Sosa Date: Wed, 20 May 2026 13:54:09 -0400 Subject: [PATCH 5/5] Revise contributing guidelines for clarity and detail Updated the section on contributions to clarify non-code contributions and added details on community engagement and technical content. Signed-off-by: Valentina Rodriguez Sosa --- content/en/docs/about/contributing.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/en/docs/about/contributing.md b/content/en/docs/about/contributing.md index 95349e86f0..b180e30819 100644 --- a/content/en/docs/about/contributing.md +++ b/content/en/docs/about/contributing.md @@ -95,12 +95,15 @@ To ensure smooth collaboration and avoid duplicate work, please follow these gui Following these guidelines helps maintain a collaborative and efficient community, reduces wasted effort, and ensures everyone's contributions are valued. -### Non-code contributions +### Contributions outside the Kubeflow components (including non-technical contributions) - **Documentation**: Contribute to technical documentation by improving the accuracy and clarity of Kubeflow technical documentation and/or fixing stale information and ensuring all new content follows the standards set in the [Kubeflow Documentation Style Guide](style-guide.md). -- **Blog posts**: Share your technical insights or success stories on the Kubeflow blog or CNCF about Kubeflow to help the community to gain more knowledge on kubeflow. These content can take different forms from learn from real-world use cases, Kubeflow integrations, news about releases or practical use cases. +- **Blog posts**: Contribute to Kubeflow blog and/or CNCF about Kubeflow to help the community to gain more knowledge on Kubeflow. The content can take different forms from learn from real-world use cases, Kubeflow integrations, news about releases, contributions or practical use cases. - **Event outreach**: Contribute to outreach activities by bringing awareness of kubeflow with activities such as: speaking at events, representing Kubeflow at community booths/tables, helping organize an event, Program committee or Program Chairs. +- **Community Engagement**: Engagement with end-users, contributors (Kubeflow community) participating or leading community meetings, social media management/promotion, discussions with end-users and contributors to enrich the kubeflow ecosystem. +- **Technical Content**: Creating webinars, demos, tutorials that showcase Kubeflow use cases and Kubeflow ecosystem including integrations, solution architectures, publications, e-books, books, white papers. +- **Website contributions**: Contributing to website desing, new content creation, website maintenance and/or contributing to PR's review. ## Owners files and PR workflow