Have made minor changes to issue template to fix the nits
Change-Id: Iadaee1289a98427c15ea03dd0a7c77a8e3ac3f7f
Updates: #824
Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
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>
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>
