KiCad MCP Pro is maintained by @oaslananka. The project uses maintainer-led decisions with lazy consensus for routine changes.
- Small fixes, docs updates, tests, and CI maintenance can be merged after normal review.
- User-facing behavior, public tool contracts, profile changes, transport behavior, and release policy changes need an issue or discussion before implementation.
- Major public API or workflow changes require an RFC under
docs/rfcs/.
- Create
docs/rfcs/000N-title.mdwith motivation, design, compatibility, migration, and alternatives. - Open a GitHub Discussion and keep it open for at least 14 days.
- Maintainers accept, reject, or request revision.
- Accepted RFCs become the source of truth for implementation PRs.
Automated GitHub CI/CD is owned by the oaslananka-lab/kicad-mcp-pro mirror. Personal GitHub, Azure DevOps, and GitLab remain manual fallback surfaces.