issue tracker

An  issue tracker  is a place to post and discuss issues like bugs & feature requests.

IndieWeb Examples
IndieWeb community members that use an issue tracker on their personal site:


 * hosts the canonical issue tracker for  on his website. He also hosts issue trackers for self-hosted Go packages on his website (e.g., https://dmitri.shuralyov.com/text/kebabcase/...$issues).


 * add yourself...

Software
Software you can use to host your own issue tracker:


 * - a simple issue tracker, compatible with GitHub issue tracker.
 * Find various  implementations in subdirectories of https://github.com/shurcooL/issues, including filesystem- and GitHub API-based implementations.

GitHub

 * GitHub provides an issue tracker for each repo

Jira
Jira provides an issue tracking / project management service.


 * https://twitter.com/isislovecruft/status/1292331568330022913
 * "i sent my anonymous friend at atlassian this tweet and i’ve been informed that the jira team uses post-it walls to organise.. jira development https://twitter.com/tesseralis/status/1291839437802844160?s=21" @isislovecruft August 9, 2020
 * https://twitter.com/tesseralis/status/1291839437802844160
 * "man goes to doctor. says he's depressed. says work is overwhelming. everything is disorganized, swamped with bureaucracy. "use the app JIRA" says doctor. "It'll help your organization keep track of work."  "but doc," says the man. "I work on JIRA."" @tesseralis August 7, 2020

Brainstorming
TODO: Capture brainstorming starting at http://indiewebcamp.com/irc/2015-05-17#t1431887181504

After the above discussion, there were undiscussed suggestions to generalize from "issue" to "request" or "todo".

Vendan: [...] I'd almost steer towards a more generic noun then issue, like request. You could have feature requests, bugfix requests, even patch requests(with code patch attached). Also opens it up to making requests on people instead of projects, which would be an interesting idea


 * The ^^^ above IRC discussion appears to be nearly completely theoretical handwaving. I'd advise anyone actually interested in trying to solve this problem to start by actually posting some of the elemental types of content involved on their own site with permalinks, e.g., before solving "issue tracker", I challenge you to prove your real-world interest by first:
 * 1. post reply posts on your own site in reply to GitHub issues, and then POSSE them to GitHub. Only two people are doing this currently:
 * Aaron Parecki (see inside for permalinks)
 * Colin Tedford
 * 2. post a new issue as a reply post on your own site in reply to a code repo on GitHub (or an indieweb site that has a code repo itself per previous point). Only one person is doing this currently:
 * Colin Tedford (see inside for permalinks)
 * 3. post code to on your own site, and then POSSE it to GitHub. A few people are doing this:
 * code
 * ... start with those three to start understanding the problem space, because otherwise all talk of naming "issue" vs "request" vs "todo" is just timewasting bikeshedding, and all other abstractions being discussed are essentially architecture astronomy. - Tantek 16:46, 20 August 2015 (PDT)

Discourage antipatterns
An issue tracker would ideally discourage various antipattern behaviors in issues, or at least raise a higher bar for prioritizing / doing them. E.g.

bikeshedding
Discourage bikeshedding (as referenced above)

yak shaving

 * extended explanation
 * Definition: https://en.wiktionary.org/wiki/yak_shaving
 * Example: Hal fixing a light bulb (from Malcolm in the Middle S03E06 - Health Scare)

http://zeroplayer.com/images/stuff/doNotShave.png