The official list of committers can be found here: Apache Parquet Committers and PMC
Below is more information about each committer (in alphabetical order). If this information becomes out of date, please send a PR to update!
| Name | Apache Id | github id | JIRA id |
|---|---|---|---|
| Alex Levenson | alexlevenson | @isnotinvain | alexlevenson |
| Aniket Mokashi | aniket486 | @aniket486 | |
| Brock Noland | brock | @brockn | |
| Cheng Lian | lian | @liancheng | liancheng |
| Chris Aniszczyk | caniszczyk | @caniszczyk | |
| Chris Mattmann | mattmann | @chrismattmann | |
| Daniel C. Weeks | dweeks | @danielcweeks | |
| Dmitriy Ryaboy | dvryaboy | @dvryaboy | |
| Fokko Driesprong | Fokko | @Fokko | fokko |
| Gang Wu | gangwu | @wgtmac | |
| Gidon Gershinsky | gershinsky | @ggershinsky | gershinsky |
| Jake Farrell | jfarrell | ||
| Jonathan Coveney | jcoveney | @jcoveney | |
| Julien Le Dem | julien | @julienledem | julienledem |
| Lukas Nalezenec | lukas | @lukasnalezenec | |
| Marcel Kornacker | marcel | @mkornacker | |
| Mickael Lacour | mlacour | @mickaellcr | |
| Nong Li | nong | @nongli | |
| Remy Pecqueur | rpecqueur | @Lordshinjo | |
| Roman Shaposhnik | rvs | @rvs | |
| Ryan Blue | blue | @rdblue | |
| Sergio Pena | spena | @spena | spena |
| Tianshuo Deng | tianshuo | @tsdeng | |
| Todd Lipcon | todd | @toddlipcon | |
| Tom White | tomwhite | @tomwhite | |
| Wes McKinney | wesm | @wesm | |
| Wesley Graham Peck | wesleypeck | @wesleypeck | |
| Xinli Shang | shangxinli | @shangxinli |
Committers have the responsibility to give constructive and timely feedback on the pull requests. Anybody can give feedback on a pull request but only committers can merge it.
First things to look at in a Pull Request:
- Is there a corresponding JIRA, and is it mentioned in the description? If not ask the contributor to make one.
- If a JIRA is open, make sure it is assigned to the contributor. (they need to have the contributor role here: https://issues.apache.org/jira/plugins/servlet/project-config/PARQUET/roles)
- Is it an uncontroversial change that looks good (has apropriate tests and the build is succesful)? => merge it
- Is it something that requires the attention of committers with a specific expertise? => mention those committers by their github id in the pull request.