Maintainers

Subsystem ownership inferred from the last two years of git log (since 2024-01-01) on origin/main. Bot accounts are excluded. Order within each cell is by commit count, descending.

Subsystem	Recent contributors
src/parser/	Mytherin, Tishj, dtenwolde
src/planner/	Mark Raasveldt, Mark, Mytherin
src/optimizer/	Laurens Kuiper, Tmonster, Tom Ebergen
src/execution/	Pedro Holanda, Mark, Laurens Kuiper
src/parallel/	Laurens Kuiper, Carlo Piovesan, Tishj
src/storage/	Mytherin, Tishj, Mark
src/catalog/	Tishj, Mytherin, Mark Raasveldt
src/transaction/	Mytherin, Mark Raasveldt, taniabogatsch
src/function/	Tishj, Mark, Mytherin
src/main/	Mark, Tishj, Mytherin
src/common/	Mytherin, Mark, Laurens Kuiper
extension/parquet/	Mytherin, Tishj, Laurens Kuiper
extension/json/	Mytherin, Laurens Kuiper, Tishj
extension/icu/	Richard Wesley, Mytherin, Mark
extension/core_functions/	Mytherin, Tishj, Pedro Holanda
tools/shell/	Mytherin, Mark Raasveldt, Mark

Notes

• Mark Raasveldt (GitHub: Mytherin) and Hannes Mühleisen are DuckDB's two co-creators. The Mark Raasveldt and Mytherin author strings refer to the same person and are co-listed in some cells.
• The project does not ship a CODEOWNERS file. Reviewer assignment happens through GitHub team membership at duckdb/duckdb-maintainers and through subsystem maintainers' triage of incoming PRs.
• For sustained engagement on a subsystem, the surest route is to contribute a few small focused PRs and engage in the issue tracker first. The "Outside Contributors" guidance in CONTRIBUTING.md is normative.

Contact

• Issue tracker: https://github.com/duckdb/duckdb/issues
• Discord: https://discord.gg/tcvwpjfnZx
• Code-of-conduct contact: quack@duckdb.org
• Security disclosures: see SECURITY.md.

For commercial support around DuckDB, see DuckDB Labs.