| layout |
|---|
documentation |
We'd like to thank the following committers to the Apache Mesos project who have helped get the project to where it is today. Committers are voted on by members of the Mesos PMC.
| Timezone GMT | Full Name | Company/Organization | IRC Handle | Email Address |
|---|---|---|---|---|
| -8 | Ross Allen | ssorallen@apache.org | ||
| -8 | Adam B | Mesosphere | me@apache.org | |
| -8 | Tim Chen | Mesosphere | tnachen | tnachen@apache.org |
| -8 | Ian Downes | idownes | idownes@apache.org | |
| -8 | Ali Ghodsi | UC Berkeley | alig@apache.org | |
| -8 | Dominic Hamon | dma@apache.org | ||
| -8 | Benjamin Hindman | Mesosphere | _benh_ | benh@apache.org |
| -8 | Ian Holsman | ianh@apache.org | ||
| -8 | Vinod Kone | vinodkone | vinodkone@apache.org | |
| -8 | Andy Konwinski | UC Berkeley | andrew@apache.org | |
| -8 | Dave Lester | dlester | dlester@apache.org | |
| -8 | Benjamin Mahler | bmahler | bmahler@apache.org | |
| -8 | Thomas Marshall | Carnegie Mellon University | tmarshall@apache.org | |
| -8 | Brenden Matthews | Mesosphere | brenden_ | brenden@apache.org |
| -8 | Chris Mattmann | NASA JPL | mattmann@apache.org | |
| -8 | Brian McCallister | Groupon | brianm@apache.org | |
| -8 | Niklas Quarfot Nielsen | Mesosphere | niq_ | nnielsen@apache.org |
| -8 | Charles Reiss | UC Berkeley | woggle@apache.org | |
| -5 | Timothy St Clair | Redhat | tstclair | tstclair@apache.org |
| +2 | Till Toenshoff | Mesosphere | tillt | tillt@apache.org |
| -8 | Thomas White | Cloudera | tomwhite@apache.org | |
| -8 | Yan Xu | xujyan | yan@apache.org | |
| -8 | Jie Yu | jieyu | jieyu@apache.org | |
| -8 | Matei Alexandru Zaharia | Databricks | matei@apache.org |
If you're interested in becoming a committer yourself, the best way to do so is by participating in developer discussions and contributing patches to the project.
We currently make no distinction between committers and PMC members. As such, every committer is responsible for the quality of the entire codebase. Some components are widely maintained (e.g. build and support tooling, tests, etc), whereas some components are inherently more critical / complex and have committers with increased context, interest, and long-term perspective.
We aim to have more than one maintainer for each component, in order to ensure that contributors can obtain timely feedback. To avoid information silos, we encourage committers to learn about areas of the code that they are unfamiliar with.
When sending reviews, it can be valuable to consult the component maintainer, as specified below. Component maintainers do not have any special "ownership" over the code, but merely serve as a resource for obtaining valuable feedback in a timely manner. We trust every committer to use good judgement to determine when to obtain feedback from a component maintainer.
| Component | Maintainers |
|---|---|
| Build / Support Tooling | widely maintained |
| Documentation | widely maintained |
| Master / Slave | Benjamin Hindman, Vinod Kone, Benjamin Mahler, Jie Yu |
| Scheduler / Executor Drivers | Benjamin Hindman, Vinod Kone, Benjamin Mahler |
| Framework API | Benjamin Hindman, Vinod Kone, Benjamin Mahler, Jie Yu |
| State Libraries | Benjamin Hindman, Benjamin Mahler |
| Replicated Log | Benjamin Hindman, Jie Yu |
| ZooKeeper Bindings | Benjamin Hindman, Vinod Kone, Benjamin Mahler, Yan Xu |
| Authentication / Authorization | Vinod Kone, Till Toenshoff |
| Modules / Hooks | Niklas Nielsen, Benjamin Hindman |
| CLI | maintainers needed |
| WebUI | maintainers needed |
| Component | Maintainers |
|---|---|
| Mesos Containerizer w/ Isolators | Ian Downes, Jie Yu |
| Docker Containerizer | Tim Chen, Benjamin Hindman |
| External Containerizer | Till Toenshoff, Benjamin Hindman |
| Component | Maintainers |
|---|---|
| Libprocess | Benjamin Hindman, Benjamin Mahler, Jie Yu |
| Stout | Benjamin Hindman, Vinod Kone, Benjamin Mahler, Jie Yu |