2 Commits

Author	SHA1	Message	Date
Niels de Vos	6baa79b173	doc: describe how to contribute when a GitHub Pull-Request is made ... Every now and then new contributors create a GitHub Pull-Request. We do not use those for accepting changes, and almost never check for new PRs. Redirecting contributors can be done automatically, just like we do when users create a GitHub Issue. Note that the bulk of the description comes from gluster-block. Just like most Gerrit maintained projects, it uses 'git review' and not a custom ./rfc.sh. New contributors that are familiar with Gerrit, will prefer the 'git review' approach over ./rfc.sh (which we want to deprecate or at least have it use 'git review' too). Change-Id: Ide36cbd80fdaaf238ea35ae5932a0cd21fc41f36 Updates: #381 URL: https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/ Signed-off-by: Niels de Vos <ndevos@redhat.com>	2018-01-30 15:05:55 +00:00
Shyam	1c19d1f4cf	doc: Added a github issue template to redirect to mails or bugzilla ... We currently see an increased activity by users filing github issues. As we do not use github issues to track or respond to queries, adding this template to help redirect users to the right forum. Change-Id: Ied69af1c42b85e10018bbd83d48f7e6fa3c1f10b Signed-off-by: Shyam <srangana@redhat.com> Reviewed-on: https://review.gluster.org/16795 Smoke: Gluster Build System <jenkins@build.gluster.org> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Vijay Bellur <vbellur@redhat.com>	2017-03-02 22:07:40 -05:00