# Helm Maintainers

This document explains the leadership structure of the Kubernetes Helm 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.

## Types of Maintainers

The Helm project includes two types of maintainers: collaborators and core maintainers.

### Helm Collaborators

Helm collaborators are developers who have commit access to the Helm repository.
The duties of a collaborator include:

* Classify and respond to GitHub issues and review pull requests
* Perform code reviews
* Shape the Helm roadmap and lead efforts to accomplish roadmap milestones
* Participate actively in feature development and bug fixing
* Answer questions and help users

### Helm Core Maintainers

Helm core maintainers help shape the direction of the Helm project.  In addition to the duties of a Collaborator, Helm Core Maintainers also:

 * Run project planning meetings
 * Place GitHub issues into GitHub milestones
 * Prioritize issues within a milestone

The current core maintainers of Helm (in alphabetical order):

* Jack Greenfield - [@jackgr](https://github.com/jackgr)
* Matt Butcher - [@technosophos](https://github.com/technosophos)

## Project Planning

The Helm core maintainers hold regular planning meetings to set the project direction, milestones, and relative prioritization of issues.  Planning meetings are coordinated via the #Helm room in the [Kubernetes Slack](http://slack.kubernetes.io/).  In order to solicit feedback from the community, planning meetings are run in public whenever possible.

## Becoming a Maintainer

Generally, potential maintainers are selected by the existing core maintainers based in part on the following criteria:

* Sustained contributions to the project over a period of time (usually months)
* A willingness to help users on GitHub and in the [#Helm Slack room](http://slack.kubernetes.io/)
* A friendly attitude

The Helm core maintainers must unanimously agree before inviting a community member to join as a maintainer, although in many cases the candidate has already been acting in the capacity of a maintainer for some time, and has been consulted on issues, pull requests, etc.