This document lists the current maintainers and their areas of responsibility.
New contributors: Please read CONTRIBUTING.md before submitting your first pull request.
| GitHub | Role |
|---|---|
| @makr-code | Project Lead, Release Manager, Core Architect |
The table below maps each source module to its responsible maintainer. All code review requests and issues for a module are routed to the corresponding maintainer via CODEOWNERS.
| Module | Path | Maintainer |
|---|---|---|
| Storage & MVCC | src/storage/, src/transaction/ |
@makr-code |
| Query Engine & AQL | src/query/, src/aql/ |
@makr-code |
| Vector & Index | src/index/ |
@makr-code |
| Graph | src/graph/ |
@makr-code |
| Search | src/search/ |
@makr-code |
| LLM / AI | src/llm/, src/rag/, src/prompt_engineering/, src/training/ |
@makr-code |
| Network & Server | src/network/, src/server/, src/rpc_grpc/ |
@makr-code |
| Replication & Sharding | src/replication/, src/sharding/, src/cdc/ |
@makr-code |
| Security & Auth | src/security/, src/auth/, src/governance/ |
@makr-code |
| Observability | src/observability/ |
@makr-code |
| Analytics & Geo | src/analytics/, src/geo/, src/timeseries/, src/temporal/ |
@makr-code |
| Content & Ingestion | src/content/, src/ingestion/, src/importers/, src/exporters/ |
@makr-code |
| Core & Performance | src/core/, src/base/, src/performance/, src/utils/ |
@makr-code |
| Plugins & Scheduler | src/plugins/, src/scheduler/, src/updates/ |
@makr-code |
| Build & Infrastructure | cmake/, .github/, CMakeLists.txt |
@makr-code |
| Documentation | docs/, compendium/ |
@makr-code |
- Final decision authority on architecture, API stability, and release dates
- Merges PRs to
main,enterprise, andhyperscalerrelease branches - Creates release tags and publishes GitHub Releases
- Manages the security advisory process
- Reviews and approves PRs touching their module within 5 business days
- Ensures module tests remain green on
develop - Keeps module
ROADMAP.mdandREADME.mdup to date - Escalates blockers to the Project Lead
ThemisDB is currently a single-maintainer project. If you are interested in taking on a co-maintainer role for a specific module:
- Contribute consistently (≥ 3 accepted PRs to the module).
- Open a GitHub Discussion proposing your co-maintainer candidacy.
- The Project Lead will review and respond within 2 weeks.
No emeritus maintainers at this time.
- General questions: GitHub Discussions
- Security issues: GitHub Security Advisories — see SECURITY.md
- Bug reports: GitHub Issues