aboutsummaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.asciidoc
diff options
context:
space:
mode:
authorLoïc Hoguin <[email protected]>2015-11-16 18:55:53 +0100
committerLoïc Hoguin <[email protected]>2015-11-16 18:55:53 +0100
commitc37852fa2bdb03de1528320436b82b7a972f7f14 (patch)
treefaf2d138d9639ff3137eb91c6d1e58182a73e95c /CONTRIBUTING.asciidoc
parentf50bf62416843f6be25b8060c0c2e38a01fa5b1b (diff)
downloadcowboy-c37852fa2bdb03de1528320436b82b7a972f7f14.tar.gz
cowboy-c37852fa2bdb03de1528320436b82b7a972f7f14.tar.bz2
cowboy-c37852fa2bdb03de1528320436b82b7a972f7f14.zip
Update CONTRIBUTING
Diffstat (limited to 'CONTRIBUTING.asciidoc')
-rw-r--r--CONTRIBUTING.asciidoc7
1 files changed, 7 insertions, 0 deletions
diff --git a/CONTRIBUTING.asciidoc b/CONTRIBUTING.asciidoc
index 5674eae..ccca6a8 100644
--- a/CONTRIBUTING.asciidoc
+++ b/CONTRIBUTING.asciidoc
@@ -48,11 +48,18 @@ new ticket when they are opened. If the maintainer didn't say
anything after a few days, you *SHOULD* write a new comment asking
for more information.
+You *SHOULD* provide a reproducible test case, either in the
+ticket or by sending a pull request and updating the test suite.
+
When you have a fix ready, you *SHOULD* open a pull request,
even if the code does not fit the requirements discussed below.
Providing a fix, even a dirty one, can help other users and/or
at least get the maintainer on the right tracks.
+You *SHOULD* try to relax and be patient. Some tickets are merged
+or fixed quickly, others aren't. There's no real rules around that.
+You can become a paying customer if you need something fast.
+
== Security reports
You *SHOULD* open a ticket when you identify a DoS vulnerability