<!--
  Title: Miniforge.ai
  Author: Christopher Lester (christopher@miniforge.ai)
  Copyright 2025-2026 Christopher Lester. Licensed under Apache 2.0.
-->

# Maintainers

This document lists the current maintainers of the Miniforge project, describes the roles and
responsibilities involved, and explains how decisions are made.

## Current Maintainers

| Name                | Role            | Contact                       |
| ------------------- | --------------- | ----------------------------- |
| Christopher Lester  | Lead Maintainer | christopher@miniforge.ai      |

## Roles

**Lead Maintainer** -- Owns the project roadmap, has final say on architectural decisions, merges
PRs, and manages releases. Responsible for ensuring the project stays aligned with its design
principles.

**Reviewer** -- Trusted contributors who review and approve pull requests. Reviewers can approve
PRs but do not have merge authority without Lead Maintainer sign-off on substantial changes.

**Contributor** -- Anyone who submits issues, pull requests, documentation improvements, or
participates in discussions. See [CONTRIBUTING.md](CONTRIBUTING.md) for how to get started.

## Response SLAs

- **Issues:** Triaged within 48 hours of submission.
- **Pull requests:** Initial review within 72 hours of submission.
- **Security reports:** Acknowledged within 48 hours per our [Security Policy](SECURITY.md).

These are targets, not guarantees. Response times may vary during holidays or periods of high
activity.

## Decision Process

Decisions are made through consensus-seeking discussion on GitHub Issues and Pull Requests. When
consensus cannot be reached, the Lead Maintainer has final say.

For significant architectural changes, open a GitHub Discussion or Issue first to gather feedback
before submitting a PR.

## Becoming a Maintainer

Maintainer status (Reviewer or Lead Maintainer) is granted based on:

1. **Sustained contributions** -- A track record of high-quality pull requests over multiple months.
2. **Architectural understanding** -- Demonstrated familiarity with the Polylith structure, workflow
   engine, and agent subsystems.
3. **Community trust** -- Constructive participation in code reviews, issues, and discussions.
4. **Alignment with project values** -- Adherence to the [Code of Conduct](CODE_OF_CONDUCT.md) and
   [Development Guidelines](docs/development-guidelines.md).

The Lead Maintainer will invite new Reviewers when these criteria are met. If you believe you
qualify, you may also reach out directly.

## Contact

- **General questions:** Open a [GitHub Discussion](https://github.com/miniforge-ai/miniforge/discussions)
- **Maintainer inquiries:** christopher@miniforge.ai
- **Security issues:** security@miniforge.ai (see [SECURITY.md](SECURITY.md))
- **Code of Conduct reports:** conduct@miniforge.ai
