Skip to content

docs: add MAINTAINERS.md for CII Best Practices submission #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
amavashev merged 1 commit into from
May 3, 2026
Merged

docs: add MAINTAINERS.md for CII Best Practices submission #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions MAINTAINERS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Maintainers

This document lists the people responsible for triaging issues, reviewing PRs, and cutting releases for `cycles-client-python` (the `runcycles` package on PyPI).

## Project lead

- **Albert Mavashev** — [@amavashev](https://github.com/amavashev) — primary committer, release manager

## Contributing organizations

The project receives contributions from:

- [Runcycles](https://github.com/runcycles)
- [K2NIO](https://github.com/K2NIO)
- Singleton Labs

## Responsibilities

| Area | Owner | SLA |
|---|---|---|
| Issue triage | Project lead | 5 business days for first response |
| PR review | Project lead | 3 business days for initial review |
| Security disclosures | See [SECURITY.md](https://github.com/runcycles/.github/blob/main/SECURITY.md) | 48h acknowledgment, 5 business days assessment |
| Release cuts | Project lead | Per repository tags; PyPI publish via `python-publish.yml` workflow on tag |
| Dependency updates | Dependabot + project lead | Auto-merge on patch updates passing CI; manual review on minor/major |

## Becoming a maintainer

We're a small team and add maintainers cautiously. Path is usually: sustained contribution (≥3 substantive PRs) → triage assistance → invitation to commit access. Open a discussion if you're interested.

## How to reach maintainers

- **General questions / bug reports**: [GitHub Issues](https://github.com/runcycles/cycles-client-python/issues)
- **Security disclosures**: see [SECURITY.md](https://github.com/runcycles/.github/blob/main/SECURITY.md) (do **not** open a public issue)
- **Conduct concerns**: see the org-wide [Code of Conduct](https://github.com/runcycles/.github/blob/main/CODE_OF_CONDUCT.md)
Loading