From c37852fa2bdb03de1528320436b82b7a972f7f14 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 16 Nov 2015 18:55:53 +0100 Subject: Update CONTRIBUTING --- CONTRIBUTING.asciidoc | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'CONTRIBUTING.asciidoc') 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 -- cgit v1.2.3