# Maintainers

This file lists how the Chef project is maintained. When making changes to the system, this
file tells you who needs to review your patch - you need a simple majority of maintainers
for the relevant subsystems to provide a :+1: on your pull request. Additionally, you need
to not receive a veto from a Lieutenant or the Project Lead.

Check out [How Chef is Maintained](https://github.com/opscode/chef-rfc/blob/master/rfc030-maintenance-policy.md#how-the-project-is-maintained) for details on the process, how to become
a maintainer, lieutenant, or the project lead.

# Project Lead

[Adam Jacob](http://github.com/adamhjk)

# Components

## Chef Core

Handles the core parts of the Chef DSL, base resource and provider
infrastructure, and the Chef applications. Includes anything not covered by
another component.

### Lieutenant

### Maintainers

[Jon Cowie](http://github.com/jonlives)

[Phil Dibowitz](https://github.com/jaymzh)

## Dev Tools

Chef Zero, Knife, Chef Apply and Chef Shell.

### Lieutenant

### Maintainers

## Test Tools

ChefSpec, Berkshelf (the chef bits), Test Kitchen (the Chef bits)

### Lieutenant

### Maintainers

## Platform Specific Components

The specific components of Chef related to a given platform - including (but not limited to) resources, providers, and the core DSL.

## Enterprise Linux

### Lieutenant

### Maintainers

[Jon Cowie](http://github.com/jonlives)

## Ubuntu

### Lieutenant

### Maintainers

## Windows

### Lieutenant

### Maintainers

## Solaris

### Lieutenant

### Maintainers

## AIX

### Lieutenant

### Maintainers

## Mac OS X

### Lieutenant

### Maintainers