<commit_before># Deis Maintainers

This document serves to describe the leadership structure of the Deis project, and list the current
project maintainers.

# What is a maintainer?

(Unabashedly stolen from the [Docker](https://github.com/docker/docker/blob/master/MAINTAINERS) project)

There are different types of maintainers, with different responsibilities, but
all maintainers have 3 things in common:

1. They share responsibility in the project's success.
2. They have made a long-term, recurring time investment to improve the project.
3. They spend that time doing whatever needs to be done, not necessarily what
is the most interesting or fun.

Maintainers are often under-appreciated, because their work is harder to appreciate.
It's easy to appreciate a really cool and technically advanced feature. It's harder
to appreciate the absence of bugs, the slow but steady improvement in stability,
or the reliability of a release process. But those things distinguish a good
project from a great one.

# Deis maintainers

Deis has two groups of maintainers in addition to our beloved Benevolent Dictator for Life.

## BDFL

Deis follows the timeless, highly efficient and totally unfair system known as [Benevolent dictator
for life](http://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life).

<NAME> ([@gabrtv](https://github.com/gabrtv)), as creator of the Deis project, serves as our
project's BDFL. While the day-to-day project management is carried out by the maintainers, Gabriel
serves as the final arbiter of any disputes and has the final say on project direction.

## Core maintainers

Core maintainers are exceptionally knowledgeable about all areas of Deis. Some maintainers work on Deis
full-time, although this is not a requirement.

The duties of a core maintainer include:
* Classify and respond to GitHub issues and review pull requests
* Help to shape the Deis roadmap and lead efforts to accomplish roadmap milestones
* Participate actively in feature development and bug fixing
* Answer questions and help users in IRC

The current core maintainers of Deis:
* <NAME> - <<EMAIL>> ([@carmstrong](https://github.com/carmstrong))
* <NAME> - <<EMAIL>> ([@mboersma](https://github.com/mboersma))
* <NAME> - <<EMAIL>> ([@technosophos](https://github.com/technosophos))
* <NAME> - <<EMAIL>> ([@bacongobbler](https://github.com/bacongobbler))

No pull requests can be merged until at least one core maintainer signs off with a [Code LGTM](http://docs.deis.io/en/latest/contributing/standards/#merge-approval). The other LGTM can come from either a core maintainer
or contributing maintainer.

## Contributing maintainers

Contributing maintainers are exceptionally knowledgeable about some but not necessarily all areas
of Deis, and are often selected due to specific domain knowledge that complements the project (but
a willingness to continually contribute to the project is most important!). Often,<commit_msg>docs(MAINTAINERS): add <NAME> as a core maintainer<commit_after># Deis Maintainers

This document serves to describe the leadership structure of the Deis project, and list the current
project maintainers.

# What is a maintainer?

(Unabashedly stolen from the [Docker](https://github.com/docker/docker/blob/master/MAINTAINERS) project)

There are different types of maintainers, with different responsibilities, but
all maintainers have 3 things in common:

1. They share responsibility in the project's success.
2. They have made a long-term, recurring time investment to improve the project.
3. They spend that time doing whatever needs to be done, not necessarily what
is the most interesting or fun.

Maintainers are often under-appreciated, because their work is harder to appreciate.
It's easy to appreciate a really cool and technically advanced feature. It's harder
to appreciate the absence of bugs, the slow but steady improvement in stability,
or the reliability of a release process. But those things distinguish a good
project from a great one.

# Deis maintainers

Deis has two groups of maintainers in addition to our beloved Benevolent Dictator for Life.

## BDFL

Deis follows the timeless, highly efficient and totally unfair system known as [Benevolent dictator
for life](http://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life).

<NAME> ([@gabrtv](https://github.com/gabrtv)), as creator of the Deis project, serves as our
project's BDFL. While the day-to-day project management is carried out by the maintainers, Gabriel
serves as the final arbiter of any disputes and has the final say on project direction.

## Core maintainers

Core maintainers are exceptionally knowledgeable about all areas of Deis. Some maintainers work on Deis
full-time, although this is not a requirement.

The duties of a core maintainer include:
* Classify and respond to GitHub issues and review pull requests
* Help to shape the Deis roadmap and lead efforts to accomplish roadmap milestones
* Participate actively in feature development and bug fixing
* Answer questions and help users in IRC

The current core maintainers of Deis:
* <NAME> - <<EMAIL>> ([@carmstrong](https://github.com/carmstrong))
* <NAME> - <<EMAIL>> ([@krancour](https://github.com/krancour))
* <NAME> - <<EMAIL>> ([@mboersma](https://github.com/mboersma))
* <NAME> - <<EMAIL>> ([@technosophos](https://github.com/technosophos))
* <NAME> - <<EMAIL>> ([@bacongobbler](https://github.com/bacongobbler))

No pull requests can be merged until at least one core maintainer signs off with a [Code LGTM](http://docs.deis.io/en/latest/contributing/standards/#merge-approval). The other LGTM can come from either a core maintainer
or contributing maintainer.

## Contributing maintainers

Contributing maintainers are exceptionally knowledgeable about some but not necessarily all areas
of Deis, and are often selected due to specific domain knowledge that complements the project (but
a willingness to continually contribute to the project is most important!). Often,
{'fraction_non_alphanumeric': 0.07223060164236635, 'fraction_numerical': 0.0013407072230601643, 'mean_word_length': 5.03437815975733, 'pattern_counts': {'":': 0, '<': 33, '<?xml version=': 0, '>': 33, 'https://': 13, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2430527', 'n_tokens_mistral': 1600, 'n_tokens_neox': 1543, 'n_words': 766}