c82da09984
- Add .github/ISSUE_TEMPLATE/ (bug_report, feature_request, config) - Add MAINTAINERS.md with maintainer list and roles - Add GOVERNANCE.md with decision-making, lifecycle, vendor neutrality - Add ADOPTERS.md with adopter collection template - Add ROADMAP.md with current focus areas and planned initiatives - Add INTEGRATIONS.md with CNCF, AI provider, and tool integrations - Add RELEASE.md documenting automated release process Part of CNCF incubation preparation tracking issue #1641 Signed-off-by: Alex Jones <axjns@example.com> Co-authored-by: Alex Jones <axjns@example.com>
4.4 KiB
k8sgpt Governance
This document describes how k8sgpt is governed and how decisions are made.
Principles
k8sgpt operates under the following principles:
- Open: k8sgpt is open source. All changes to the project are made publicly.
- Neutral: k8sgpt is vendor-neutral. No single organization controls the project.
- Collaborative: We welcome contributions from all individuals and organizations.
- Merit-based: Influence is earned through sustained, quality contributions.
- Community-focused: We serve the cloud native community, not any single vendor.
k8sgpt is a CNCF project and adheres to the CNCF Code of Conduct.
Decision Making
Consensus-Seeking
The project strives for consensus among maintainers. For most decisions:
- A proposal is made (via GitHub issue or PR)
- Maintainers review and discuss for at least 48 hours
- If consensus is reached, the proposal is implemented
- If consensus cannot be reached, the proposal is put to a vote
Voting
When consensus cannot be reached on significant matters:
- Each maintainer receives one vote
- A simple majority (50% + 1) decides the outcome
- Quorum requires at least 50% of active maintainers to participate
- Ties are broken by the project lead (AlexsJones)
Significant Decisions
The following require a formal vote:
- Addition or removal of maintainers
- Changes to this governance document
- Project direction changes (e.g., major architectural shifts)
- Deprecation or removal of core features
- Licensing changes
Operational Decisions
Minor operational decisions (bug fixes, documentation, small features) do not require a full vote and can be handled through normal PR review.
Maintainer Lifecycle
Becoming a Maintainer
- Make sustained, quality contributions over a period of at least 3 months
- Be nominated by an existing maintainer
- Receive approval from a majority of current maintainers
- Be added to the MAINTAINERS.md file and granted write access
Stepping Down
Maintainers may step down at any time by notifying the remaining maintainers. Stepping-down maintainers are listed in the Emeritus Maintainers section of MAINTAINERS.md.
Inactive Maintainers
A maintainer who has not contributed (code, review, or community) for 6 months may be asked to step down. If they do not respond within 30 days, the remaining maintainers may vote to move them to emeritus status.
Revocation
A maintainer's access may be revoked for violations of the CNCF Code of Conduct. This requires a supermajority (2/3) vote of active maintainers.
Vendor Neutrality
k8sgpt is committed to vendor neutrality:
- No single vendor may control project direction
- All AI backend providers are supported equally (OpenAI, Azure, Cohere, Ollama, Amazon Bedrock, Google Gemini, etc.)
- Decisions about supported backends are made based on community merit, not vendor influence
- Financial contributions from sponsors do not buy decision-making power
- The project benefits from the CNCF's neutral governance structure
Subproject Governance
k8sgpt has several subprojects under the k8sgpt-ai organization:
- k8sgpt (main project) - This repository
- k8sgpt-operator - Kubernetes operator for continuous monitoring
- docs - Documentation site
- charts - Helm charts
- website - Project website
- community - Community management
Subprojects have their own maintainers but are expected to align with the main project's governance. Changes to a subproject's governance should be coordinated with the main project maintainers.
Community Engagement
We encourage broad community participation:
- Slack: #k8sgpt
- GitHub Issues: All feature requests and bug reports
- GitHub Discussions: Open for community questions and ideas
- CNCF Slack: #k8sgpt
Code of Conduct
All participants in this project are expected to adhere to the CNCF Code of Conduct. Reports should be sent to the project maintainers and/or CNCF staff.
Amendment Process
This governance document may be amended at any time by a supermajority (2/3) vote of active maintainers. Proposed amendments should be discussed publicly before voting.