THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Name | Organization |
|---|---|
| Michael Armbrust | Databricks |
| Joseph Bradley | Databricks |
Mosharaf Chowdhury | University of Michigan, Ann Arbor |
Jason Dai | Intel |
Tathagata Das | Databricks |
Ankur Dave | UC Berkeley |
| Aaron Davidson | Databricks |
Thomas Dudziak | |
Robert Evans | Yahoo! |
| Wenchen Fan | Databricks |
| Joseph Gonzalez | UC Berkeley |
Thomas Graves | Yahoo! |
Stephen Haberman | Bizo |
Mark Hamstra | ClearStory Data |
| Herman van Hovell | QuestTec B.V. |
| Yin Huai | Databricks |
Shane Huang | Intel |
Andy Konwinski | Databricks |
Ryan LeCompte | Quantifind |
Haoyuan Li | Alluxio, UC Berkeley |
| Davies Liu | Databricks |
| Cheng Lian | Databricks |
Sean McNamara | Webtrends |
| Xiangrui Meng | Databricks |
Mridul Muralidharam | Yahoo! |
| Andrew Or | Databricks |
| Kay Ousterhout | UC Berkeley |
| Sean Owen | Cloudera |
Nick Pentreath | IBM |
Imran Rashid | Cloudera |
Charles Reiss | UC Berkeley |
Josh Rosen | Databricks |
| Sandy Ryza | Clover Health |
| Kousuke Saruta | NTT Data |
Prashant Sharma | IBM |
Ram Sriharsha | Databricks |
| DB Tsai | Netflix |
| Marcelo Vanzin | Cloudera |
Shivaram Venkataraman | UC Berkeley |
Patrick Wendell | Databricks |
Andrew Xia | Alibaba |
Reynold Xin | Databricks |
Matei Zaharia | Databricks, MIT |
| Shixiong Zhu | Databricks |
Review Process and Maintainers
Spark development follows the Apache voting process, where changes to the code are approved through consensus. We use a review-then-commit model, where at least one committer other than the patch author has to review and approve it before it gets merged, and any committer may vote against it. For certain modules, changes to the architecture and public API should also be reviewed by a maintainer for that module (which may or may not be the same as the main reviewer) before being merged. The PMC has designated the following maintainers:
Component | Maintainers |
|---|---|
| Spark core public API | Josh Rosen, Patrick Wendell, Reynold Xin, Matei Zaharia |
Job scheduler | Mark Hamstra, Kay Ousterhout, Patrick Wendell, Matei Zaharia |
Shuffle and network | Aaron Davidson, Reynold Xin, Matei Zaharia |
Block manager | Aaron Davidson, Reynold Xin |
| Build system | Sean Owen, Patrick Wendell |
YARN | Thomas Graves, Andrew Or, Marcelo Vanzin |
| Python | Davies Liu, Xiangrui Meng, Josh Rosen, Matei Zaharia |
| R | Davies Liu, Shivaram Venkataraman |
| MLlib | Joseph Bradley, Xiangrui Meng, Shivaram Venkataraman, Matei Zaharia |
| SQL | Michael Armbrust, Reynold Xin |
| Streaming | Tathagata Das, Matei Zaharia |
| GraphX | Ankur Dave, Joseph Gonzalez, Reynold Xin |
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.
Becoming a Committer
To get started contributing to Spark, learn how to contribute – anyone can submit patches, documentation and examples to the project.
...