Labels

• Comp:Analysis

  This issue has to do with the analysis component of the code or document. (plots, postprocessing)
• Comp:Build

  This issue has to do with the build system of the code/doc (makefiles, cmake, install errors)
• Comp:Core

  This issue has to do with the main bulk of the code or document. (methods, main content)
• Comp:Input

  This issue has to do with the input component of the code or document. (input parameters, prep)
• Comp:Output

  This issue has to do with the output component of the code or document. (writing to databases, etc.)
• Difficulty:1-Beginner

  This issue does not require expert knowledge and may be a good issue for new contributors.
• Difficulty:2-Challenging

  This issue may be complex or require specialized skills.
• Difficulty:3-Expert

  This issue is not only complicated, but also complex. It may require special advanced skills.
• Priority:1-Critical

  This is the highest priority (i.e. it is blocking other work or facing a deadline).
• Priority:2-Normal

  This work is important and should be completed ASAP.
• Priority:3-Desired

  This work is important, but not urgent.
• Priority:4-Low

  This work is valuable, but not urgent or mission critical.
• Status:1-New

  No one has claimed this issue yet. It is in need of solving.
• Status:2-Backlog

  This issue has been claimed, but it's not being worked on right now, and it's not next to be tackled
• Status:3-Selected

  The assignee has chosen to work on this item next (after their current, in progress, issue)
• Status:4-In Progress

  This is actively being worked on by the assignee.
• Status:5-In Review

  This issue has been handled, and the solution is being reviewed. (probably as a PR)
• Status:6-Duplicate

  This can be closed because it is covered by / duplicative of the content of another issue or PR.
• Status:7-WontFix

  This issue can be closed because it is not necessary to fix this issue.
• Type:Bug

  Something is wrong or broken. This issue or PR is related to a bug in code.
• Type:Docs

  Is related to API documentation, website content, etc.
• Type:Feature

  New feature or feature request
• Type:Question

  This issue can be closed with a discussion and/or an answer.
• Type:Style

  Is related to coding style guide compliance (e.g. PEP8 or google C++ style guide).
• Type:Test

  Is related to software testing. Failing tests, necessary new tests, test frameworks, etc.