Open nimbinatus opened 10 months ago
Holding; steering is discussing this one with some draft proposals.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
@nimbinatus I am assuming that we need to automate the KEPs stored in here? IMO the report / pdf generation pipeline should get triggered whenever there is a merge to master.
Proposal: Centralized Kubernetes KEP Site for Enhanced Discoverability and Accessibility
Background Kubernetes Enhancement Proposals (KEPs) are critical to the development and evolution of Kubernetes. Currently, KEPs are managed in the kubernetes/enhancements repository. While this structure is effective for version control, it lacks user-friendly discoverability and accessibility features that would encourage more widespread community engagement.
Objective This proposal aims to create a centralized, publicly accessible website that aggregates all KEPs and offers a more readable, searchable format. The website will be automatically updated upon any new merges to the KEP repository, ensuring the latest content is always available. The site will also provide the ability to download all KEPs as a single PDF.
Solution Overview Centralized Repository for Hosting the Site: A new repository (e.g., kubernetes/enhancements-site) will be created under the Kubernetes GitHub organization to host the website and manage the GitHub Pages deployment.
Automated CI/CD Pipeline: The kubernetes/enhancements repository will use GitHub Actions to automatically generate and deploy the site to the enhancements-site repository whenever a change is merged into master. The pipeline will use MkDocs, a static site generator, to render the KEPs in a readable format and deploy them to the gh-pages branch of the enhancements-site repository.
Key Features:
Benefits:
Implementation Plan
Rollout and Communication:
Maintenance and Future Enhancements
Conclusion This proposal addresses the need for a more accessible and discoverable KEP resource. By leveraging existing tools and automating the deployment process, the community will benefit from a polished, user-friendly site that stays up to date with the latest developments in Kubernetes.
/remove-lifecycle rotten
Describe the issue
During a podcast recording, @mrbobbytables, @katcosgrove, and I were discussing how to make the KEPs and annual reports a bit more discoverable and comprehensible. We discussed having a pipeline that generated either PDFs or a website that aggregated the KEPs and reports in a more readable format for users to encourage people to read them and understand them. I'm opening this issue to at least get the conversation in writing and started.
/assign @nimbinatus /sig contributor-experience