mirror of
https://github.com/golang/go
synced 2024-11-24 12:30:14 -07:00
778b649e38
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>
999 B
999 B
Contributing to Go
Go is an open source project.
It is the work of hundreds of contributors. We appreciate your help!
Filing issues
When filing an issue, make sure to answer these five questions:
- What version of Go are you using (
go version
)? - What operating system and processor architecture are you using?
- What did you do?
- What did you expect to see?
- What did you see instead?
General questions should go to the golang-nuts mailing list 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
Please read the Contribution Guidelines before sending patches.
We do not accept GitHub pull requests (we use Gerrit instead for code review).
Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.