summaryrefslogtreecommitdiffstats
path: root/.github
diff options
context:
space:
mode:
authorDave Davenport <qball@gmpclient.org>2017-05-14 21:06:34 +0200
committerDave Davenport <qball@gmpclient.org>2017-05-14 21:06:34 +0200
commit9d068151fdbad2710b1fe9294c21c4c9d28ca15b (patch)
tree223122b30090fe5aa57614aeb01e10ce01262656 /.github
parent3fe42c3f79792b3fa07c865766e8128dc1c3d6aa (diff)
Update contributing
Diffstat (limited to '.github')
-rw-r--r--.github/CONTRIBUTING.md37
1 files changed, 26 insertions, 11 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 85fadd14..adf51bc6 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -1,9 +1,11 @@
# Creating an issue
-When reporting bugs keep in mind that the people working on it do this unpaid, in their free time and as a hobby. So be
-polite and helpful. Bug reports that demand, contain insults to this or other projects, or have a general unfriendly
-tone will be closed without discussion. Everybody has it own way of working; What might be the norm for you, might not
-be for others. Therefore be verbose in your description.
+When reporting bugs keep in mind that the people working on it do this unpaid,
+in their free time and as a hobby. So be polite and helpful. Bug reports that
+demand, contain insults to this or other projects, or have a general unfriendly
+tone will be closed without discussion. Everybody has it own way of working;
+What might be the norm for you, might not be for others. Therefore be verbose in
+your description.
Before creating an issue:
@@ -21,17 +23,30 @@ When reporting bugs include the following information:
* A proper title for others to search for.
* Be exact.
+When adding comments to an issue make sure:
+
+* It is relevant to the issue.
+* It contributes to solving the issue.
+* Use :+1: :-1: emojis instead of replying 'me too' or 'I also have this.'
+
+
+Issue high-jacking, e.g. adding a request/issue to an existing issue, is very
+disruptive.
+Please create a new issue, if it is similar it will be marked duplicate.
+
The issue tracker is not for:
* Questions.
* Writing complaints.
-These topics belong on [FORUM](https://reddit.com/r/qtools//), [IRC](https://webchat.freenode.net/?channels=#rofi),
-frequently asked questions will be added to the [F.A.Q](https://github.com/DaveDavenport/rofi/wiki#faq) on the
-[wiki](https://github.com/DaveDavenport/rofi/wiki).
+These topics belong on [FORUM](https://reddit.com/r/qtools//),
+[IRC](https://webchat.freenode.net/?channels=#rofi), frequently asked questions
+will be added to the [F.A.Q](https://github.com/DaveDavenport/rofi/wiki#faq) on
+the [wiki](https://github.com/DaveDavenport/rofi/wiki).
-Questions filled in on the bug tracker will be marked `question`, locked and closed. If the question is clear, I
-normally try to provide an answer.
+Questions filled in on the bug tracker will be marked `question`, locked and
+closed. If the question is clear, I normally try to provide an answer.
-**Please do not submit reports related to wayland, see [here](https://github.com/DaveDavenport/rofi/wiki/Wayland) for
-more information.**
+**Please do not submit reports related to wayland, see
+[here](https://github.com/DaveDavenport/rofi/wiki/Wayland) for more
+information.**