Commit 0cc1d2c6 authored by Greg Wilson's avatar Greg Wilson
Browse files

Documenting standard labels.

Closes #35.
parent 9bb202e7
Loading
Loading
Loading
Loading
+15 −0
Original line number Diff line number Diff line
@@ -10,6 +10,7 @@ keypoints:
- "Each lesson has one or two maintainers who act as editors."
- "Maintainers are responsible for ensuring that issues and change requests are addressed."
- "Maintainers have final say over lesson content."
- "We use a standard set of labels to classify issues and pull requests."
---

This episode describes the processes used to maintain our lessons.
@@ -57,3 +58,17 @@ will be named by the year and month they happen, e.g., `2016.05`.
   and adds an `index.html` page to it.
5. The release maintainer adds a submodule to the release directory of `swc-release`
   that points to the newly-created release branch of the lesson.

## Issue Labels in Repositories

Our repositories use the following labels (and colors) for issues and pull requests:

* `bug` (#bd2c00): errors to be fixed.
* `discussion` (#fc8dc1): discussion threads.
* `enhancement` (#9cd6dc): new features.
* `help-wanted` (#f4fd9c): requests for assistance.
* `instructor-training` (#6e5494): pull requests submitted as part of instructor training.
* `newcomer-friendly` (#eec275): suitable for people who are still learning the ropes.
* `question` (#808040): often turn into discussion threads.
* `template-and-tools` (#2b3990): issues related to the templates and tools rather than the lessons themselves.
* `work-in-progress` (#7ae78): someone is still working on this.