Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds definitions for projects and maintainership of projects #25

Merged
merged 2 commits into from
Dec 12, 2018
Merged

Adds definitions for projects and maintainership of projects #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7bdbf75
Adds definitions for projects and maintainership of projects
nellshamrell Dec 11, 2018
f73e95a
clarifies definitions of projects and maintainers
nellshamrell Dec 12, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions definitions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Definitions

### Project

A Project is one GitHub repo that contains code.

### Product

A Product consists of one or more Projects.

### Maintainer

A maintainer is responsible for merging pull requests, triaging issues, and general project maintenance.

A Project has many maintainers.
15 changes: 15 additions & 0 deletions maintainership.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Maintainership of Projects

## Definition
* Projects have **maintainers**, not authors
* The maintainers are responsible for merging pull requests, triaging issues, and more.

## Rules and Responsibilities
* At least two maintainers must be current Chef employees
* Roadmaps are planned by Product Management, Engineering Leadership, and maintainers (including external maintainers - who have input, but not veto power)
* Maintainers are responsible for **communicating** overall project planning and roadmap of their project.
* Maintainer reviews are required on all code and maintainers are the only ones that can merge code into a project. If you need to merge code, then you are a maintainer.
* All maintainer team discussion outside of security issues should be done in a public forum.
* The maintainer team is added as a codeowner on their repository so that they are automatically setup via Github for code reviews
* All contributions must include Developer Certificate of Origin signoff
* A tool is setup to ping maintainers for reviews / triage.