GitHub Issues Labels

As of 2013/4/17, all the GitHub Issues have been labelled according to the following color scheme and meanings:

• Red: bug
  • Repro'd: reported by a user, reproduced by a repo collaborator
  • Known: reported by a user, already known by repo collaborators but not yet recorded in the issue tracker
  • on master: self-reported (by @laughinghan or @jneen), live on current master
• Green: external enhancement
  • Feature: feature request or feature change that affects intended behavior of MathQuill
  • Docs: documentation issue
• Bright Blue: internal enhancement
  • Refactor: renaming, refactoring, re-architecting
  • Build: build system toolchain
  • Test: never enough
• Dark Blue: design issue
  • API: issue with the design of (some aspect of) the API; not just a bug in some API method
  • Usability: usability issue, concrete solutions are always Features
• Pink: difficulty
  • Nebulous: annoying problem without clear, specific criteria for being solved
  • Hard, Hard as Hell: trivial or straightforward. Really. Please, go take a swing at one of these right now, it'll take you no time at all
• Gray: topic
  • Compat: browser compatibility
  • Key Events: cross-browser key events shitshow, isolated into textarea.js starting in #87
  • Parser: bugs in and refactors of the isolated parser combinator micro-library, parser.js, in generality as a parser combinator library, ignoring the specifics of LaTeX parsing
  • LaTeX parsing: bugs in actual MathQuill LaTeX parsing; mostly centralized to latex.js by #99
  • LatexCommandInput: bugs in LatexCommandInput
  • Text: bugs with text "mode", in TextBlock and RootTextBlock
  • Visual: visual rather than behavioral bugs; no exceptions thrown, tree still well-formed; especially if a purely cosmetic issue, or a CSS-only fix
• Closed Issues Only
  • Black, IgnoreMe: (in the actual issues list, extra gray for some reason) created by mistake, pretend deleted. There should be no other labels, so as not to affect label statistics
  • Yellow, Archived: don't want to delete the branch and lose the commits/code/work forever, don't want to clutter up the branches list, so PR just to close it and delete the branch, they keep around a "Restore" button accessible from the closed PR

The statistics by topic are actually quite interesting, for example, it's unsurprising that Key Events clocked in a solid 18 issues, and unsurprising that Text would also have many issues, but I thought, "no way it would have as many as the shitshow Key Events was!" Well, I thought wrong: Text has 22 issues and climbing. - @laughinghan, 2013/4/19