Skip to content

Issue triage and priority

Jonathan Allard edited this page Apr 1, 2016 · 6 revisions

Selectize is maintained by volunteers and has a large amount of requests to handle. Here is how we can make it easier to manage.

Voting

We're going to start taking into account "positive reactions" (+1s that are the Github feature, not the comment) to assess need/support on issues and PRs. You can add your reactions to help us figure out the priority in which to processs the requests.

Priority

Issues and pull requests are treated in order of priority. It is assessed according to the following factors:

  • Actionability: PR, Issue with code proposed, Issue with cause known, Issue with cause unknown, Question

Pull requests are easiest to process, while cause-unknown issues and questions most difficult.

Triage

Triage is what allows us to assess the priority of a requests and thus to process the most important first. You can help with the triage and suggest tags by commenting with tags in bracket (eg. [has-tests][enhancement]). That will make the work of maintainers easier to triage and add tags.

PR

  • Has tests?: [has tests], [drafting tests], (default) no tests
  • Complexity: [trivial], (default) medium, [complex]

To sum up, the perfect PR:

  • Has tests, and they pass
  • Has been tested and confirmed by someone else
  • Doesn't add options or expand scope without need
  • Has clear one-action commit(s), and is cleanly mergeable

Issues

  • Actionability: [code proposed], [cause known], [cause unknown], [question]
  • Brokkenness: [regression], [bug], [enhancement]
  • Scope: [refactor], (default) no change, [expands scope] (such as adding an option)
  • Support: [consensus], (default) no wide consensus yet
  • Component: [dropdown], [input component]
Clone this wiki locally