Move docs/development to docs/maintaining

This commit is contained in:
Parker Moore 2016-11-02 14:03:08 -07:00
parent db4c571020
commit b108f4c87e
No known key found for this signature in database
GPG Key ID: 193CDEBA72063C58
9 changed files with 8 additions and 14 deletions

View File

@ -46,6 +46,6 @@
- title: Meta
docs:
- contributing
- development
- maintaining
- conduct
- history

View File

@ -1,7 +1,6 @@
---
title: Affinity Team Captains
layout: docs
permalink: /docs/development/affinity-team-captain/
---
**This guide is for affinity team captains.** These special people are **team maintainers** of one of our [affinity teams][] and help triage and evaluate the issues and contributions of others. You may find what is written here interesting, but its definitely not for everyone.

View File

@ -1,7 +1,6 @@
---
title: "Avoiding Burnout"
layout: docs
permalink: /docs/development/avoiding-burnout/
---
**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but its definitely not for everyone.

View File

@ -1,7 +1,6 @@
---
title: "Becoming a Maintainer"
layout: docs
permalink: /docs/development/becoming-a-maintainer/
---
**This guide is for contributors.** These special people have contributed to one or more of Jekyll's repositories, but do not yet have write access to any. You may find what is written here interesting, but its definitely not for everyone.

View File

@ -1,7 +1,7 @@
---
layout: docs
title: Maintaining Jekyll
permalink: /docs/development/
permalink: /docs/maintaining/
---
**This guide is for Jekyll contributors and maintainers.** These special people contribute to one or more of Jekyll's repositories or help merge the contributions of others. You may find what is written here interesting, but its definitely not for everyone.
@ -9,11 +9,12 @@ permalink: /docs/development/
Hello! This is where we document various processes for maintaining Jekyll. Being a maintainer for any Jekyll project is a big responsibility, so we put together some helpful documentation for various tasks you might do as a maintainer.
1. [Triaging and issue](triaging-an-issue/)
2. [Reviewing a pull request](reviewing-a-pull-request/)
3. [Merging a pull request](merging-a-pull-request/)
4. [Avoiding burnout](avoiding-burnout/)
5. [Special Labels](special-labels/)
1. [Affinity teams & their captains](affinity-team-captain/)
2. [Triaging and issue](triaging-an-issue/)
3. [Reviewing a pull request](reviewing-a-pull-request/)
4. [Merging a pull request](merging-a-pull-request/)
5. [Avoiding burnout](avoiding-burnout/)
6. [Special Labels](special-labels/)
Interested in becoming a maintainer? Here is some documentation for **contributors**:

View File

@ -1,7 +1,6 @@
---
title: "Merging a Pull Request"
layout: docs
permalink: /docs/development/merging-a-pull-request/
---
**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but its definitely not for everyone.

View File

@ -1,7 +1,6 @@
---
title: "Reviewing a Pull Request"
layout: docs
permalink: /docs/development/reviewing-a-pull-request/
---
**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but its definitely not for everyone.

View File

@ -1,7 +1,6 @@
---
title: "Special Labels"
layout: docs
permalink: /docs/development/special-labels/
---
**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but its definitely not for everyone.

View File

@ -1,7 +1,6 @@
---
title: "Triaging an Issue"
layout: docs
permalink: /docs/development/triaging-an-issue/
---
**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but its definitely not for everyone.