aboutsummaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorgorhill <rhill@raymondhill.net>2015-06-21 17:40:52 -0400
committergorhill <rhill@raymondhill.net>2015-06-21 17:40:52 -0400
commit86eb558f4353612a7aa803179671d572cd876917 (patch)
tree27a2bc11d7d2650d375e239154fb4fd5d670e539 /CONTRIBUTING.md
parent19487f10cd41cfc01b88e8b11b094e780395982f (diff)
downloaduBlock-86eb558f4353612a7aa803179671d572cd876917.zip
uBlock-86eb558f4353612a7aa803179671d572cd876917.tar.gz
uBlock-86eb558f4353612a7aa803179671d572cd876917.tar.bz2
editing
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md19
1 files changed, 10 insertions, 9 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ea34f70..9b46787 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,6 +1,8 @@
# Submitting issues
-**Must read:** [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).
+Any issue opened with no effort to provide the required details **for me to reproduce** it will be closed as _invalid_.
+
+***
### Before you submit
@@ -15,15 +17,10 @@
- Any such issue will be closed without comment.
1. Make sure your issue [hasn't already been fixed in a recent release](https://github.com/gorhill/uBlock/releases).
1. Verify that the issue does **not** occur with uBlock disabled.
- - If it still occurs with uBlock disabled, it's probably not an issue with uBlock.
1. Verify that the issue is not related to a 3rd-party filter lists.
- - If it is the case, report to the list maintainer(s).
- - It helps to also test with Adblock Plus, with **same** filter lists.
- - If issue also occurs with ABP, it's most likely a filter list issue.
-1. Verify that the issue is not caused by another extension, such as HTTPS Everywhere.
-1. Any issue opened with no effort to provide the required details will be closed without comment.
+1. Verify that the issue is not caused by another extension.
----
+***
### What to include
@@ -31,7 +28,7 @@
To help diagnose and fix the bug/issue, please always, **always**, **ALWAYS** include the following in your report:
* A clear list of steps to reproduce the problem
- * **Always include a URL**, _even_ if "it happens everywhere". Just do it.
+ * **Always include a URL**, _even_ if "it happens everywhere".
* Symptoms of the issue
* Describe what you observe and consider broken behavior; this is what we'll be looking for after executing the steps
* Example: video doesn't start playing, page layout broken
@@ -48,3 +45,7 @@ To help diagnose and fix the bug/issue, please always, **always**, **ALWAYS** in
* Tip: try disabling them and see if your issue still occurs
Otherwise, we've noticed that a lot of **your** time (and the developers') gets thrown away on exchanging back and forth to get this information.
+
+***
+
+**Good read:** [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).