Add comparison of good and not good reports

This commit is contained in:
YUKI "Piro" Hiroshi 2016-06-11 22:28:16 +09:00 committed by GitHub
parent fdba3ee393
commit 6a408401eb

View File

@ -9,6 +9,7 @@ This is possibly a generic guideline for contributing any Firefox addon project
A good report is the fastest way to solve a problem.
Even if the problem is very clear for you, possibly unclear for me.
Unclear report can be left unfixed for long time.
You'll see an example of [good report](https://github.com/piroor/treestyletab/issues/1134) and [another report with too less information](https://github.com/piroor/treestyletab/issues/1135).
Here is a list of typical questions I asked to existing reports: