Issue Assignment and Prioritization

The ExoCTK team uses GitHub Issues and GitHub projects for tracking development tasks and their progress. This wiki page describes how to properly assign and prioritize new GitHub issues.

A new GitHub issue should be created for any item of work that will eventually correspond to a change in the exoctk repository, including the code base itself, tests, conda environment, repository documentation, notebooks, etc. The creation of a new issue should also apply to changes needed to the official ExoCTK documentation or the EXOCTK_DATA package. Lastly, new issues should also be created for any tasks that may not result in changes to the repository, but requires significant effort by ExoCTK developers (e.g. "Ask ITSD for a new server", "Create presentation for Spring Symposium", etc.)

For new GitHub issues:

1. Add an appropriate title that concisely describes the issue
2. Add a description that provides a more detailed description of the issue. Make sure to link any related issues or materials.
3. Add one or more 'Assignee'(s).
4. Add a 'priority label' and one or more 'category label'(s):
   • The 'priority label' should be either 1: HIGH PRIORITY, 2: MEDIUM PRIORITY, or 3. LOW PRIORITY
   • The 'category label' should be the category or categories that is most appropriate for the issue. For example, if the issue is for adding a new unit test, apply Category: Tests
5. If applicable, add the Urgent: User Submission, Urgent: Bug, and/or Urgent: Question label(s)
6. If applicable, add a "Project" to the issue that corresponds to a future release.