github.com/dustinrc/deis@v1.10.1-0.20150917223407-0894a5fb979e/MAINTAINERS.md (about)

     1  # Deis Maintainers
     2  
     3  This document serves to describe the leadership structure of the Deis project, and list the current
     4  project maintainers.
     5  
     6  # What is a maintainer?
     7  
     8  (Unabashedly stolen from the [Docker](https://github.com/docker/docker/blob/master/MAINTAINERS) project)
     9  
    10  There are different types of maintainers, with different responsibilities, but
    11  all maintainers have 3 things in common:
    12  
    13  1. They share responsibility in the project's success.
    14  2. They have made a long-term, recurring time investment to improve the project.
    15  3. They spend that time doing whatever needs to be done, not necessarily what
    16  is the most interesting or fun.
    17  
    18  Maintainers are often under-appreciated, because their work is harder to appreciate.
    19  It's easy to appreciate a really cool and technically advanced feature. It's harder
    20  to appreciate the absence of bugs, the slow but steady improvement in stability,
    21  or the reliability of a release process. But those things distinguish a good
    22  project from a great one.
    23  
    24  # Deis maintainers
    25  
    26  Deis has two groups of maintainers in addition to our beloved Benevolent Dictator for Life.
    27  
    28  ## BDFL
    29  
    30  Deis follows the timeless, highly efficient and totally unfair system known as [Benevolent dictator
    31  for life](http://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life).
    32  
    33  Gabriel Monroy ([@gabrtv](https://github.com/gabrtv)), as creator of the Deis project, serves as our
    34  project's BDFL. While the day-to-day project management is carried out by the maintainers, Gabriel
    35  serves as the final arbiter of any disputes and has the final say on project direction.
    36  
    37  ## Core maintainers
    38  
    39  Core maintainers are exceptionally knowledgeable about all areas of Deis. Some maintainers work on Deis
    40  full-time, although this is not a requirement.
    41  
    42  The duties of a core maintainer include:
    43  * Classify and respond to GitHub issues and review pull requests
    44  * Help to shape the Deis roadmap and lead efforts to accomplish roadmap milestones
    45  * Participate actively in feature development and bug fixing
    46  * Answer questions and help users in IRC
    47  
    48  The current core maintainers of Deis:
    49  * Chris Armstrong - <carmstrong@engineyard.com> ([@carmstrong](https://github.com/carmstrong))
    50  * Kent Rancourt - <krancourt@engineyard.com> ([@krancour](https://github.com/krancour))
    51  * Matt Boersma - <mboersma@engineyard.com> ([@mboersma](https://github.com/mboersma))
    52  * Matt Butcher - <mbutcher@engineyard.com> ([@technosophos](https://github.com/technosophos))
    53  * Matthew Fisher - <mfisher@engineyard.com> ([@bacongobbler](https://github.com/bacongobbler))
    54  
    55  No pull requests can be merged until at least one core maintainer signs off with an
    56  [LGTM](http://docs.deis.io/en/latest/contributing/standards/#merge-approval). The other LGTM can
    57  come from either a core maintainer or contributing maintainer.
    58  
    59  ## Contributing maintainers
    60  
    61  Contributing maintainers are exceptionally knowledgeable about some but not necessarily all areas
    62  of Deis, and are often selected due to specific domain knowledge that complements the project (but
    63  a willingness to continually contribute to the project is most important!). Often,
    64  core maintainers will ask a contributing maintainer to weigh in on issues, pull requests, or
    65  conversations where the contributing maintainer is knowledgeable.
    66  
    67  The duties of a contributing maintainer are very similar to those of a core maintainer, but they are limited to areas of the Deis project where the contributing maintainer is knowledgeable.
    68  
    69  The current contributing maintainers of Deis:
    70  * Johannes Würbach - <johannes.wuerbach@googlemail.com> ([@johanneswuerbach](https://github.com/johanneswuerbach))
    71  * Manuel de Brito Fontes - <alejandro.debrito@soficom.cl> ([@aledbf](https://github.com/aledbf))
    72  * Seth Goings - <sgoings@engineyard.com> ([@sgoings](https://github.com/sgoings))
    73  * Sivaram Mothiki - <smothiki@engineyard.com> ([@smothiki](https://github.com/smothiki))
    74  * Wael Nasreddine - <waelnasreddine@gmail.com> ([@kalbasit](https://github.com/kalbasit))
    75  
    76  ## Becoming a maintainer
    77  
    78  The Deis project wouldn't be where it is today without its community. Many of the project's
    79  community members embody the spirit of maintainership, and have contributed substantially to
    80  the project.
    81  
    82  The contributing maintainers group was created in part so that exceptional members of the community
    83  who have an interest in the continued success of the project have the opportunity to join the
    84  core maintainers in guiding the future of Deis.
    85  
    86  Generally, potential contributing maintainers are selected by the Deis core maintainers based in
    87  part on the following criteria:
    88  * Sustained contributions to the project over a period of time (usually months)
    89  * A willingness to help Deis users on GitHub and in IRC
    90  * A friendly attitude :)
    91  
    92  The Deis core maintainers must unanimously agree before inviting a community member to join as a
    93  contributing maintainer, although in many cases the candidate has already been acting in the
    94  capacity of a contributing maintainer for some time, and has been consulted on issues, pull requests,
    95  etc.