This document lays out the guidelines under which the AWS Controllers for Kubernetes (ACK) project will be governed. The goal is to make sure that the roles and responsibilities are well defined and clarify on how decisions are made.
In the context of ACK, we consider the following roles:
- Users ... everyone using ACK, typically willing to provide feedback on ACK by proposing features and/or filing issues.
- Contributors ... everyone contributing code, documentation, examples, testing infra, and participating in feature proposals as well as design discussions. Code contributions will require a Developer Certificate of Origin (DCO).
- Maintainers ... are responsible for engaging with and assisting contributors to iterate on the contributions until it reaches acceptable quality. Maintainers can decide whether the contributions can be accepted into the project or rejected. Any active contributor meeting the project quality can be made a Maintainer by the Advisory Board.
- Advisory Board ... is responsible for defining the guidelines and processes that the project operates under.
The initial members of the Advisory Board are @jaypipes and @mhausenblas.
The primary mechanism for communication will be via the #provider-aws channel on the Kubernetes Slack community.
All features and bug fixes will be tracked as issues in GitHub. All decisions will be documented in GitHub issues.
In the future, we may consider using a public mailing list, which can be better archived.
Maintainers will share roadmap and release versions as milestones in GitHub.
The Advisory Board will propose a release management proposal via a GitHub issue and resolve it there.
- The ACK Contributing Guidelines
- Our Code of Conduct