How To Organize GitHub Issues

Community

Issues should be categorized and prioritized by The Community.

Issues filed as Bugs should be sorted and categorized first.

All open Issues without a milestone should be sorted and categorized.

Open Wish List Issues should be periodically reviewed, and recategorized when resources (such as funding or new technology) become available.

Discuss open Needs Discussion Issues. Goal: Change them all to “Next Task.”

Prioritize open Next Task Issues.

Review open Active Development Issues. Stalled Issues may need recategorized; ensure that completed Issues have been closed.

Development

Developers encounter Issues in the following order, and will not encounter any Issue which is not found by one of these links.

• Active Development
• Next Task, Priority Critical
• Next Task, Priority High
• Next Task, Priority Normal
• Next Task, Priority Low

Edit this Documentation

If you see something that needs to be edited in this document, you can create an issue using the link under the search widget at the top left side of this page, or you can edit directly here.