The issue tracker may look like like a pastel rainbow, but those tags aren't just for decoration -- here's what the main ones mean:
effort-x - How hard is this going to be? Low effort issues should be easy to pick up and quick to take care of. High effort issues may require significant knowledge of Intern's internals (adding test runner parallelism) or take quite a while (rewriting large parts of the documentation). Medium effort is...somewhere between those.
priority-x - Roughly how important is it to do something now. If you're looking for something to have an immediate impact, high priority issues are it. Low priority issues are still worthwhile, but it's not as important that they be done now.
domain-x - What "domain" an issue relates to. Interested in working on the CLI? Look for something in domain-cli. Want to make Intern work better with remote browsers? domain-webdriver.
repo-x - Whatever fix is made to Intern should also be applied to another repo (e.g., repo-leadfoot means apply the fix to @theintern/leadfoot).
enhancement - This will result in a new or improved feature
bug - Something is broken. These tend to be higher priority.
information - This issue isn't really an "issue", it just contains information
project-dev - These relate to the Intern project rather than Intern itself, things like fixing CI tests or updating a build script.
Picking up an issue
If you're looking for an issue to work on, bugs are often the highest priority issues. priority-high issues are, not surprisingly, the next highest priority things to work on. It's probably good to pick something that roughly fits in with how much effort you want to spend, too; don't pick an effort-high issue if you don't think you'll be able to spend much time on it.
Labels
The issue tracker may look like like a pastel rainbow, but those tags aren't just for decoration -- here's what the main ones mean:
effort-x- How hard is this going to be? Low effort issues should be easy to pick up and quick to take care of. High effort issues may require significant knowledge of Intern's internals (adding test runner parallelism) or take quite a while (rewriting large parts of the documentation). Medium effort is...somewhere between those.priority-x- Roughly how important is it to do something now. If you're looking for something to have an immediate impact, high priority issues are it. Low priority issues are still worthwhile, but it's not as important that they be done now.domain-x- What "domain" an issue relates to. Interested in working on the CLI? Look for something indomain-cli. Want to make Intern work better with remote browsers?domain-webdriver.repo-x- Whatever fix is made to Intern should also be applied to another repo (e.g.,repo-leadfootmeans apply the fix to @theintern/leadfoot).enhancement- This will result in a new or improved featurebug- Something is broken. These tend to be higher priority.information- This issue isn't really an "issue", it just contains informationproject-dev- These relate to the Intern project rather than Intern itself, things like fixing CI tests or updating a build script.Picking up an issue
If you're looking for an issue to work on, bugs are often the highest priority issues.
priority-highissues are, not surprisingly, the next highest priority things to work on. It's probably good to pick something that roughly fits in with how much effort you want to spend, too; don't pick aneffort-highissue if you don't think you'll be able to spend much time on it.