This file lists the maintainers of LLMKube.
| Maintainer | GitHub | Areas |
|---|---|---|
| Chris Maher | @Defilan | Lead: operator, CLI, Helm, docs |
| Jory Irving | @joryirving | Foreman (coder/reviewer harness) |
| Tanguille | @Tanguille | Observability |
Maintainers review and merge pull requests, triage issues, and help set technical direction. Area maintainers focus their review and merge authority on their listed areas; the lead maintainer covers the rest, cuts releases, and owns overall direction.
Maintainership is earned through sustained, high-quality contribution rather than a formal application. The path we look for:
- A track record of well-scoped, reviewed pull requests in an area of the codebase.
- Helping triage issues and review others' pull requests.
- Reliable adherence to the project's process: DCO sign-off, tests alongside changes, and disclosure of AI assistance per CONTRIBUTING.md.
An existing maintainer then extends an invitation for an area (or the whole project), after which the new maintainer is added here and to CODEOWNERS.
The best starting points are opening focused pull requests, helping triage issues, and joining discussions. See CONTRIBUTING.md.
Security reports follow the process in SECURITY.md. Please do not send vulnerability reports to individual maintainers.