# Maintainers

This file lists the people who currently maintain Kapitan.

## Core maintainers

| GitHub handle | Name | Focus |
|---------------|------|-------|
| [@ramaro](https://github.com/ramaro) | Ricardo Amaro | Project lead, reviews, releases |
| [@ademariag](https://github.com/ademariag) | Alessandro De Maria | Architecture, features, community |
| [@uberspot](https://github.com/uberspot) | — | Code, features |
| [@adrianchifor](https://github.com/adrianchifor) | Adrian Chifor | Features, infrastructure |
| [@Moep90](https://github.com/Moep90) | Danny H. | Documentation, testing, backends |
| [@gburiola](https://github.com/gburiola) | Luis Buriola | Features, integrations |

## Bots and automation

| GitHub handle | Purpose |
|---------------|---------|
| [@kapicorpbot](https://github.com/kapicorpbot) | CI and release automation |
| [@KapitanCi](https://github.com/KapitanCi) | Continuous integration |

## How to become a maintainer

There is no formal process. Consistent, high-quality contributions over time are the main path. Existing maintainers nominate and vote privately. If you are interested, keep contributing, help review others' PRs, and engage respectfully in discussions.

## Maintainer responsibilities

- Triage issues and pull requests in a timely manner.
- Keep the codebase healthy: tests pass, dependencies up to date, security patches applied.
- Release new versions with clear release notes.
- Enforce the [Code of Conduct](CODE_OF_CONDUCT.md).
