Apache Arrow Project Governance

The Arrow project is a part of the Apache Software Foundation and follows its project management guidelines, which promote community-led consensus decisionmaking, independent of commercial influence.

Project Management Committee (PMC)

The PMC governs the project. Members vote on important decisions, including releases and inviting committers to join the PMC.

Name Affiliation
Andy Grove (Chair) NVIDIA
Abdelhakim Deneche Salesforce
Alex Levenson Twitter
Andrew Lamb InfluxData
Antoine Pitrou Voltron Data
Ben Baumgold Independent
Ben Kietzman Voltron Data
Daniël Heres Coralogix
David Li Voltron Data
Dewey Dunnington Voltron Data
François Saint-Jacques Optable
Hanifi Gunes MZ
Jacob Quinn RelationalAI
Jacques Nadeau Sundeck
Jake Luciani DataStax
James Taylor Salesforce
Jason Altekruse Workday
Jie Wen SelectDB
Jonathan Keane Independent
Jorge Cardoso Leitao Munin Data ApS
Joris van den Bossche Voltron Data
Julian Hyde Looker
Julien Le Dem Datakin
Krisztián Szűcs Voltron Data
Kun Liu Ebay
Liang-Chi Hsieh Apple
Marcel Kornacker Independent
Matthew Topol Voltron Data
Micah Kornfield Google
Michael Stack Cloudera
Neal Richardson Posit
Neville Dipale commutenav
Nic Crane Independent
P. Taylor Goetz Monetate
Parth Chandra MapR
Philipp Moritz Anyscale
Phillip Cloud Standard Cognition
Qingping Hou Scribd, Inc.
Raphael Taylor-Davies InfluxData
Raúl Cumplido Voltron Data
Reynold Xin Databricks
Sebastien Binet CERN
Siddharth Teotia LinkedIn
Steven Phillips Dremio
Sutou Kouhei ClearCode
Ted Dunning MapR
Todd Lipcon Google
Uwe L. Korn Quantco
Wes McKinney Voltron Data
Weston Pace LanceDB
Will Jones LanceDB
Yibo Cai Arm

Committers

Contributors who have demonstrated a sustained commitment to the project may be invited by the PMC to become committers. Committers are authorized to merge code patches to the project’s repositories and serve as non-voting project maintainers. See the “Becoming a committer” section below for more details.

Name Affiliation
Alenka Frim Voltron Data
Alessandro Molina Voltron Data
Bogumił Kamiński SGH Warsaw School of Economics
Brent Gardner Coralogix
Brian Hulette Google
Bryan Cutler IBM
Chao Sun Apple
Curt Hagenlocher Microsoft
Curtis Voigt Beacon Biosignals
Dan Harris Coralogix
David Alves CortexXus
Deepak Majeti Ahana
Dominik Moritz Carnegie Mellon University
Eric Erhardt Microsoft
Eric Patrick Hanson Beacon Biosignals
Felipe Oliveira Carvalho Voltron Data
Gang Wu Unknown
Ian Cook Voltron Data
Ippokratis Pandis Amazon
Jacob Wujciak Voltron Data
James Duong Improving
Jarrett Revels Beacon Biosignals
Jay Zhan None
Jeffrey Vo None
Ji Liu Alibaba
Jiayu Liu Airbnb Inc.
Kazuaki Ishizaki IBM
Kenta Murata Xica Co., Ltd.
Kevin Gurney MathWorks
Li Jin Two Sigma
Liya Fan Alibaba
Marco Neumann InfluxData
Mehmet Ozan Kabak Synnada
Mustafa Akur Synnada
Oleks V. None
Paddy Horan Assured Allies
Paul Taylor NVIDIA
Praveen Kumar Dremio
Ravindra Pindikura Dremio
Remzi Yang NVIDIA
Robert Nishihara Anyscale
Rok Mihevc Voltron Data
Romain Francois Posit
Ruihang Xia Greptime
Rémi Dattai Cloudfuse
Wang Mingming Ebay
Xudong Wang ByteDance
Xuwei Fu Unknown
Yang Jiang Ebay
Yanghong Zhong Ebay
Yijie Shen Space and Time
Yosuke Shiro Red Data Tools

Becoming a committer

There are many ways to contribute to the Apache Arrow project, including issue reports, documentation, tests, and code. Contributors with sustained, high-quality activity may be invited to become committers by the PMC as a recognition of their sustained contribution to the project. A committer can commit changes directly in all Arrow GitHub repositories, and have the significant responsibility of using their status and access to improve the Arrow project for the entire community.

When considering to invite someone to be a committer, the PMC looks for contributors who are doing the work and exercising the judgment expected of a committer already. After all, any contributor can do all of the things a committer does except for merge a PR. While there is no set list of requirements, nor a checklist that entitles one to commit privileges, typical behaviors include:

  • Contributions beyond pull requests, such as reviewing other pull requests, fixing bugs and documentation, triaging issues, answering community questions, improving usability, reducing technical debt, helping with CI, verifying releases, debugging in strange environments, etc.

  • These contributions to the project should be consistent in quality and sustained over time, typically on the order of 6 months or more.

  • Assistance growing the size and health of the community via constructive, respectful, and consensus driven interactions, as described in our Code of Conduct and the Apache Way.

The mechanics of how the process works is documented here. If you feel you should be offered committer privileges, but have not been, you can reach out to one of the PMC members or the private@arrow.apache.org mailing list.