...
Name | Organization |
---|---|
Michael Armbrust | Databricks |
Mosharaf Chowdhury | UC Berkeley |
Jason Dai | Intel |
Tathagata Das | Databricks |
Ankur Dave | UC Berkeley |
Aaron Davidson | Databricks |
Thomas Dudziak | Groupon |
Robert Evans | Yahoo! |
Joseph Gonzalez | UC Berkeley |
Thomas Graves | Yahoo! |
Andy Konwinski | Databricks |
Stephen Haberman | Bizo |
Mark Hamstra | ClearStory Data |
Shane Huang | National University of Singapore |
Ryan LeCompte | Quantifind |
Haoyuan Li | UC Berkeley |
Sean McNamara | Webtrends |
Xiangrui Meng | Databricks |
Mridul Muralidharam | Yahoo! |
Andrew Or | Databricks |
Kay Ousterhout | UC Berkeley |
Nick Pentreath | Mxit |
Imran Rashid | Quantifind |
Charles Reiss | UC Berkeley |
Josh Rosen | Databricks |
Prashant Sharma | Imaginea, Pramati, Databricks |
Ram Sriharsha | Yahoo! |
Shivaram Venkataraman | UC Berkeley |
Patrick Wendell | Databricks |
Andrew Xia | Alibaba |
Reynold Xin | Databricks |
Matei Zaharia | Databricks, MIT |
Review Process and Maintainers
...
Note that the maintainers in Spark do not "own" each module – every committer is responsible for the quality of the whole codebase. Instead, maintainers are asked by the PMC to ensure that public APIs and changes to complex components are designed consistently. Any committer may contribute to any module, and any committer may review any code change. If maintainers do not respond to a change within a reasonable amount of time, other committers may also merge it and ask the PMC to add more maintainers for that module.
...