summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSahdev P. Zala <spzala@us.ibm.com>2017-12-13 15:09:44 -0500
committerSahdev P. Zala <spzala@us.ibm.com>2017-12-13 15:22:36 -0500
commitf84309aa517bef06c1f41824d4cfa8e621071f92 (patch)
tree3fce87909bfae06b3b2d8b4331e03922ec40d1a2
parentfdb9fbd9298d55dacabc939b408b036921d94267 (diff)
Complete File an Issue section
The File an Issue section is work in progress. Adding more detail with a broader coverage on what, why and where to file a issue to complete this section.
-rw-r--r--contributors/guide/README.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/contributors/guide/README.md b/contributors/guide/README.md
index e416a733..cff0989d 100644
--- a/contributors/guide/README.md
+++ b/contributors/guide/README.md
@@ -118,12 +118,13 @@ _Improvements needed_
### File an Issue
-Not ready to contribute code, but see something that needs work? While we encourage everyone to contribute code, we also appreciate it when someone finds a problem.
-Again, there are multiple repositories within the community, and each will have its own Issues.
-For example, here is where you file an Issue to [kubernetes/kubernetes](https://git.k8s.io/kubernetes/issues/new). Please make sure to adhere to the prompted submission guidelines.
+Not ready to contribute code, but see something that needs work? While the community encourage everyone to contribute code, it also appreciate when someone report a issue (aka problem).
+There are multiple repositories within the Kubernetes community and a full list of repositories can be found [here](https://github.com/kubernetes/).
+Issue should be reported to an appropriate repository instead of always reporting to the [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes/issues) repository. For example, a documentation issue should be opened to [kubernetes/website](https://github.com/kubernetes/website/issues). Make sure to adhere to the prompted submission guidelines while opening an issue.
-_Improvements needed_
-* clarify there are many k/subrepos where you can file issues. Refer to "how to find and appropriate SIG" document to find out which.
+Note that, you should not open issue for a question. While you are learning or playing with Kubernetes you may run into questions.
+Opening an issue for a question unnecessarily increases the total numbers of issues and creates load on the triage team.
+Ask question on [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes), [ServerFault](https://stackoverflow.com/questions/tagged/kubernetes) or on the appropriate Kubernetes [Slack Channel](http://slack.k8s.io/).
# Contributing