This document provides information on who the Kanister maintainers are, and their responsibilities. If you're interested in contributing, see the CONTRIBUTING guide.
These are the current Kanister maintainers:
- Tom Manville @tdmanv
- Pavan Navarathna @pavannd1
- Prasad Ghangal @PrasadG193
- Vivek Singh @viveksinghggits
- Daniil Fedotov @hairyhum
- Eugen Sumin @e-sumin
Maintainers are active and visible members of the community. They have a lot of experience with the project and are expected to have the knowledge and insight to lead its growth and improvement.
This section describes their responsibilities.
Uphold the values and behavior set forward by the Code of Conduct to ensure a safe and welcoming community.
Prioritize reported security vulnerabilities and ensure that they are addressed before features or bugs. See the project's security policy.
Review pull requests regularly with comments, suggestions, decision to reject, merge or close them. Accept only high quality pull requests. Provide code reviews and guidance on incoming pull requests to adhere to established standards, best practices and guidelines.
Review issues regularly to determine their priority and relevance, with proper labeling to identify milestones, blockers, complexity, entry-level issues etc.
Respond to Slack messages, enhancement requests, and forum posts. Allocate time to reviewing and commenting on issues and conversations as they come in.
Maintain healthy test coverage and code quality report score. Avoid dependency bloat. Mitigate breaking changes.
Make frequent project releases to the community. Keep the release branch at production quality at all times. Backport features as needed. Cut release branches and tags to enable future patches.
Regularly promote and attend the recurring Kanister community meetings.