Consider an issue template to help streamline new issues and to ask the right questions

[talllguy]

Consider this a meta-issue to this issue tracker. Github has a nifty new-ish feature that allows those with write access to a repository to create a template for new issues, such as the (untemplated) one I'm currently writing. For a great example, check out the one over on the Mapillary Issue tracker.

The advantage here for those that fix the issues reported, is that you can ask the questions that turn sometimes incoherent issues into succinct user stories. Asking things like the platform used, expected result, and actual result challenge the reporter to consider what exactly they're reporting.

Read more.

[pnorman]

CONTRIBUTING.md says

As OpenStreetMap data is always changing, rendering bug reports should always contain a cropped screenshot of the problem, and a link to the area. Don't assume that we will see exactly what you see. If a particular OSM object is an issue, the issue should contain the tagging of the object.

So we want to encourage that.

[kocio-pl]

I'd like to introduce it soon - GitHub suggests that it's the last thing missing for a community friendly project:

https://github.com/gravitystorm/openstreetmap-carto/community