Maintainers

Apache Arrow does not use a CODEOWNERS file. Maintainership is informal and decentralized — every Apache committer can review and merge any PR, but in practice there is a clear set of subsystem owners derived from sustained activity. This page summarizes the de-facto subsystem owners, derived from git log over the last year.

Subsystem ownership

Subsystem	Most active recent contributors	Last activity
C++ Acero	William Ayd, Rossi Sun, gitmodimo	Apr 2026
C++ Compute	Rossi Sun, Antoine Pitrou, Hyukjin Kwon	Apr 2026
C++ Parquet	Antoine Pitrou, Zehua Zou, mwish	Apr 2026
C++ Gandiva	Sutou Kouhei, Dmitry Chirkov, Logan Riggs	Apr 2026
C++ Dataset	Antoine Pitrou, Joris Van den Bossche, Felipe Aramburu	Apr 2026
C++ Flight + Flight SQL	David Li, Antoine Pitrou, Sutou Kouhei	Apr 2026
C++ Filesystem	Antoine Pitrou, Tianchen Ding, Sutou Kouhei	Apr 2026
C++ Substrait engine	Weston Pace, Antoine Pitrou, David Li	2026
C++ IPC + format	Antoine Pitrou, Wes McKinney (legacy)	Apr 2026
C++ Util / SIMD / async	Antoine Pitrou, William Ayd, Sutou Kouhei	Apr 2026
PyArrow	Hyukjin Kwon, Raúl Cumplido, Rok Mihevc, Antoine Pitrou	Apr 2026
R arrow	Nic Crane, Hyukjin Kwon, Bryce Mecum	Apr 2026
C-GLib	Sten Larsson, Sutou Kouhei, Hiroyuki Sato	Apr 2026
Ruby (Red Arrow)	Sutou Kouhei	Apr 2026
MATLAB	Kevin Gurney, Sarah Gilmore	Apr 2026
CI / Crossbow / Release	Raúl Cumplido, Sutou Kouhei	Apr 2026
Documentation	Joris Van den Bossche, Bryce Mecum, Vibhatha Abeykoon	Apr 2026

This list reflects who has reviewed and merged the most PRs in the last year. The list is not exclusive — the broader committer list is public on the Apache Arrow committers page.

Project governance

Apache Arrow is governed by the Apache Software Foundation. The PMC (Project Management Committee) handles project-level decisions: releases, committer additions, code-of-conduct enforcement. PMC discussions happen on the private list (private@arrow.apache.org); release votes happen on the public dev list (dev@arrow.apache.org).

The project follows the standard Apache release process:

1. A release manager opens a release branch and prepares an RC.
2. The RC is signed and posted for a 72-hour vote.
3. Committers and PMC members verify the RC by running dev/release/verify-release-candidate.sh (which lives outside the repo at https://github.com/apache/arrow-release).
4. After three +1 PMC votes and no -1 votes, the release is finalized.

Major releases happen approximately quarterly. Patch releases are issued from maint-* branches as needed.

Contacting maintainers

• General questions: https://arrow.apache.org/community/.
• Bug reports: GitHub issues with the appropriate component label.
• Design discussions: dev@arrow.apache.org (subscribe via dev-subscribe@arrow.apache.org).
• Security issues: security@apache.org (per ASF policy).

This wiki page is informational. The official contributor guide is the canonical reference for working with the project.