@FichteFoll , thanks for the ideas. I've updated the labels, adding prefixes, to allow sorting. To me looks very clean now. https://github.com/SublimeText/Issues/issues
This bug tracking is only for Sublime Text 3
, or these bugs of ST2, but still present in ST3.
These people asking for jon, forget jon, if we work here, this will eventually be good for the community. And I'm sure, jon will keep an eye, maybe not as an active "contributor", but he will be able to look freely there and probably find better ways to look at reported problems, with proper descriptions and ways to reproduce these. Take jon as a robot which understand code
When people report bugs in forums, we will be able to link to github, they may add more information and the overall quality of reported things, will improve. You may find ways to workaround these, and see how many people is complaining, etc.
The first step was to select a bug tracking platform. DONE
The second was some start labels. DONE
Now we need to add some bug guidelines. I suggest we draft in this document, which allows easy editing:https://docs.google.com/document/d/15c5 ... sp=sharing
then we can import the guidelines to the readme.md file.I somewhat leading this, and taking actions, but please, if you think something is wrong and you have intentions to improve looking at the big picture of all the community, please comment.