From f8fb74a6d853088ffb4279a3360a69e5c91e40f1 Mon Sep 17 00:00:00 2001 From: William Vu Date: Tue, 4 Mar 2014 12:19:34 -0600 Subject: [PATCH] Add more examples of good contributions --- CONTRIBUTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 58a956fdd3..ef528d245b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -25,7 +25,7 @@ guide](https://github.com/rapid7/metasploit-framework/wiki/Setting-Up-a-Metasplo * **Don't** leave your pull request description blank. * **Don't** abandon your pull request. Being responsive helps us land your code faster. -[Here](https://github.com/rapid7/metasploit-framework/pull/3043) is an excellent example of a good pull request. Try to follow that format. +Pull requests [#2940](https://github.com/rapid7/metasploit-framework/pull/2940) and [#3043](https://github.com/rapid7/metasploit-framework/pull/3043) are a couple good examples to follow. #### New Modules @@ -53,6 +53,8 @@ guide](https://github.com/rapid7/metasploit-framework/wiki/Setting-Up-a-Metasplo * **Don't** file duplicate reports - search for your bug before filing a new report. * **Don't** report a bug on GitHub. Use [Redmine](https://dev.metasploit.com/redmine/projects/framework) instead. +Redmine issues [#8762](https://dev.metasploit.com/redmine/issues/8762) and [#8764](http://dev.metasploit.com/redmine/issues/8764) are a couple good examples to follow. + If you need some more guidance, talk to the main body of open source contributors over on the [Freenode IRC channel](http://webchat.freenode.net/?channels=%23metasploit&uio=d4) or e-mail us at [metasploit-hackers](https://lists.sourceforge.net/lists/listinfo/metasploit-hackers)