Committers

Current Committers

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. This list might be stale, the canonical list is located on Apache's website.

Timezone GMT Full Name Company/Organization IRC Handle Email Address
-8 Ross Allen [email protected]
-8 Adam B Mesosphere [email protected]
-8 Tim Chen Mesosphere tnachen [email protected]
-8 Ian Downes Twitter idownes [email protected]
-8 Ali Ghodsi UC Berkeley [email protected]
-8 Dominic Hamon [email protected]
-8 Benjamin Hindman Mesosphere _benh_ [email protected]
-8 Ian Holsman [email protected]
-8 Vinod Kone Twitter vinodkone [email protected]
-8 Andy Konwinski UC Berkeley [email protected]
-8 Dave Lester Twitter dlester [email protected]
-8 Benjamin Mahler Twitter bmahler [email protected]
-8 Thomas Marshall Carnegie Mellon University [email protected]
-8 Brenden Matthews Mesosphere brenden_ [email protected]
-8 Chris Mattmann NASA JPL [email protected]
-8 Brian McCallister Groupon [email protected]
-8 Niklas Quarfot Nielsen Mesosphere niq_ [email protected]
-8 Charles Reiss UC Berkeley [email protected]
-5 Timothy St Clair Redhat tstclair [email protected]
+2 Till Toenshoff Mesosphere tillt [email protected]
-8 Thomas White Cloudera [email protected]
-8 Yan Xu Twitter xujyan [email protected]
-8 Jie Yu Twitter jieyu [email protected]
-8 Matei Alexandru Zaharia Databricks [email protected]

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.

Component Maintainers

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 maintainers, 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 component maintainers.

Component Maintainers (alphabetical)
Master / Slave Benjamin Hindman, Vinod Kone, Benjamin Mahler, Jie Yu
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 Adam B, Vinod Kone, Till Toenshoff
Modules / Hooks Niklas Nielsen, Benjamin Hindman
CLI maintainers needed
WebUI maintainers needed
Project Website Dave Lester

Containerization

Component Maintainers (alphabetical)
Mesos Containerizer Ian Downes, Jie Yu
Docker Containerizer Tim Chen, Benjamin Hindman
External Containerizer Till Toenshoff, Benjamin Hindman

C++ Libraries

Component Maintainers (alphabetical)
Libprocess Benjamin Hindman, Benjamin Mahler, Jie Yu
Stout Benjamin Hindman, Vinod Kone, Benjamin Mahler, Jie Yu