{"action":"created","issue":{"url":"https://api.github.com/repos/mypaint/mypaint/issues/606","repository_url":"https://api.github.com/repos/mypaint/mypaint","labels_url":"https://api.github.com/repos/mypaint/mypaint/issues/606/labels{/name}","comments_url":"https://api.github.com/repos/mypaint/mypaint/issues/606/comments","events_url":"https://api.github.com/repos/mypaint/mypaint/issues/606/events","html_url":"https://github.com/mypaint/mypaint/issues/606","id":134659690,"number":606,"title":"Set up a useful ISSUE_TEMPLATE.md","user":{"login":"achadwick","id":61299,"avatar_url":"https://avatars.githubusercontent.com/u/61299?v=3","gravatar_id":"","url":"https://api.github.com/users/achadwick","html_url":"https://github.com/achadwick","followers_url":"https://api.github.com/users/achadwick/followers","following_url":"https://api.github.com/users/achadwick/following{/other_user}","gists_url":"https://api.github.com/users/achadwick/gists{/gist_id}","starred_url":"https://api.github.com/users/achadwick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/achadwick/subscriptions","organizations_url":"https://api.github.com/users/achadwick/orgs","repos_url":"https://api.github.com/users/achadwick/repos","events_url":"https://api.github.com/users/achadwick/events{/privacy}","received_events_url":"https://api.github.com/users/achadwick/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mypaint/mypaint/labels/enhancement","name":"enhancement","color":"c7def8"},{"url":"https://api.github.com/repos/mypaint/mypaint/labels/Project","name":"Project","color":"323232"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-18T18:40:20Z","updated_at":"2016-02-18T18:42:51Z","closed_at":null,"body":"Issue reporters frequently have to be asked to supply basic information about new issues. we already use a `CONTRIBUTING.md` that refers people to the [bug reporting guide](https://github.com/mypaint/mypaint/wiki/Reporting-Bugs) and the [Contributing pages](https://github.com/mypaint/mypaint/wiki/Contributing) on the wiki, but this information is hidden away behind links that not many people click.\r\n\r\n**[Github have recently added support for templates for new issues](https://github.com/blog/2111-issue-and-pull-request-templates)**. This is just a bit of Markdown, meaning that reporters could be given some [task list checkboxes](https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments). If we do that, what ought to go there?\r\n\r\n@yourfirstpr and @Charlotteis [remind us](https://twitter.com/yourfirstpr/status/700303824892768257) that the template's job is to make the project more accessible. What can we do there to improve our workflow? There seem to be two main jobs here:\r\n\r\n* Leading new reporters through the process of reporting an issue\r\n  - This is a crowd with few coding skills, but deep knowledge in other areas and a very clear idea of what they want, or when something's wrong. MyPaint's userbase is artists, not coders. It's HIGHLY international, meaning that language can be a barrier when reporting.\r\n  - Gathering the information has the checkbox nature, and we really need that reproducibility info for the next stage\r\n  - Basic bug report/triage checkboxes: \"I have searched for duplicates\", \"I've tried this with a fresh config\", \"I verified that this affects the latest stable version / the latest master HEAD\", \"I've written up what version this affects / what OS I'm using\".\r\n* Providing information to people with (some of) the skills required to fix the bug, and helping them grow their skills\r\n  - These folk will be more technical, a mix of triagers and coders. Sometimes the occasional icon artist or documenter.\r\n  - A canned workflow for us would be an improvement over our current rather lax approach. For starters:\r\n    - Checkbox: someone has managed to reproduce this issue enough for it to be fixed\r\n    - Checkbox: task-is-assigned\r\n    - Checkbox: forked and cloned and branched\r\n    - Checkbox: PR submitted.\r\n\r\nThe great thing about this is that it puts relevant information in the user's eyeline.\r\n\r\nMyPaint already does something a little like this from the exception dialog: we offer a button for searching the tracker, and have a translated template in there on the Submit button that becomes unlocked after a search is started. We HAVE had a couple of reports with just the exception and an uncustomized template, however - perhaps due to the aforementioned language issues.\r\n\r\nPerhaps an obvious checkbox-based reporting nature may help with this?\r\n\r\nOne thing is obvious: we shouldn't let the structure constrain us too much if we do this. Best make it clear that contributors can and should remove tasks which don't make sense.\r\n\r\nOne stumbling block: who has permissions to edit those checklists or the original post? That may make the ticky-box idea unworkable for the details."},"comment":{"url":"https://api.github.com/repos/mypaint/mypaint/issues/comments/185853921","html_url":"https://github.com/mypaint/mypaint/issues/606#issuecomment-185853921","issue_url":"https://api.github.com/repos/mypaint/mypaint/issues/606","id":185853921,"user":{"login":"achadwick","id":61299,"avatar_url":"https://avatars.githubusercontent.com/u/61299?v=3","gravatar_id":"","url":"https://api.github.com/users/achadwick","html_url":"https://github.com/achadwick","followers_url":"https://api.github.com/users/achadwick/followers","following_url":"https://api.github.com/users/achadwick/following{/other_user}","gists_url":"https://api.github.com/users/achadwick/gists{/gist_id}","starred_url":"https://api.github.com/users/achadwick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/achadwick/subscriptions","organizations_url":"https://api.github.com/users/achadwick/orgs","repos_url":"https://api.github.com/users/achadwick/repos","events_url":"https://api.github.com/users/achadwick/events{/privacy}","received_events_url":"https://api.github.com/users/achadwick/received_events","type":"User","site_admin":false},"created_at":"2016-02-18T18:42:51Z","updated_at":"2016-02-18T18:42:51Z","body":"Alternative/less officious approach: **[just the headings](https://help.github.com/articles/creating-an-issue-template-for-your-repository/)**, per the feature documentation."}}