Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Elvish is a pretty ambitious project. There are always a lot of things to do, which translates to a lot of issues (among other things). Without some proper organization, it is very easy to get buried in details and lose track of important problems to solve.
We use labels in a structured way to organize issues. You can browse the list of all labels; have it open alongside this document and explore it.
The most important labels are those that categorizes issues. There are 3 sets of them:
With the exception of a few "meta" issues like this one, all issues have exactly one category label. When an issue conceptually belongs to both a Project and a Component, the Project is favored as it is more specific. Likewise, a Component takes precedence over an Area.
Issues may be recategorized over time, to represent shifts in our conception. For example, a Project may eventually emerge from a Component, and issues may move from the Component to the newly conceived Project.
There are 4 type labels:
Feature requests do not have a specific label as they are so common.
There is an additional label,