diff options
| author | Brad Fitzpatrick <bradfitz@golang.org> | 2015-01-18 10:56:00 -0800 |
|---|---|---|
| committer | Brad Fitzpatrick <bradfitz@golang.org> | 2015-01-18 21:27:07 +0000 |
| commit | 778b649e386788ec834336f0a222e3f515dadd3a (patch) | |
| tree | d9bba894c96508e9edd1e34b3afcc45bc1793bd3 /CONTRIBUTING.md | |
| parent | c2c0bf77efef5fd0e1cdecb330a9d30de1509ff8 (diff) | |
| download | go-git-778b649e386788ec834336f0a222e3f515dadd3a.tar.gz | |
doc: direct people to the mailing list
Since the move to Github, we've started to receive lots of
introductory questions to the bug tracker. I posit this is because
most projects on Github don't have mailing lists, so the culture on
Github is to use the Issue Tracker as a discussion forum.
The Go project doesn't use the Issue Tracker as our first point of
communication. This CL updates CONTRIBUTING.md (which is linked when
you file a bug or send a pull request), to mention that we have a
mailing list.
It certainly won't stop all the errant bug reports, but it should
help.
Change-Id: Id8fbfd35b73f5117617dff53b1e72d5b5276388b
Reviewed-on: https://go-review.googlesource.com/3002
Reviewed-by: Rob Pike <r@golang.org>
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6444e76b5c..0ba13d34b7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -15,6 +15,8 @@ When filing an issue, make sure to answer these five questions: 4. What did you expect to see? 5. What did you see instead? +General questions should go to the [golang-nuts mailing list](https://groups.google.com/group/golang-nuts) instead of the issue tracker. +The gophers there will answer or ask you to file an issue if you've tripped over a bug. ## Contributing code |