《Go開發指南》翻譯邀請

并發程式設計網組織新的一期系列文章翻譯，這期是GO官網教程 https://golang.google.cn/doc/ 相關技術文章，歡迎大家踴躍參加。

如何領取

通過本文留言或網站原文( http://ifeve.com/go/ )評論領取想要翻譯的文章，每次領取一章或一節（根據内容長短），翻譯完後再領取其他章節。領取完成之後，譯文最好在一個星期内翻譯完成，如果不能完成翻譯，也歡迎你邀請其他同學和你一起完成翻譯。請謹慎領取，很多文章領取了沒有翻譯，導緻文章很長時間沒人翻譯。

如何送出？

翻譯完成之後請登入到并發網送出成待稽核狀态，會有專門的編輯校對後進行釋出。如果多篇文章翻譯被評為A級會更新您為譯者，并加入譯者溝通微信群。如果在本站翻譯超過十篇文章，将有禮品贈送，比如簽名版的《Java并發程式設計的藝術》或者榮譽譯者獎杯等。如果你喜歡使用markdown編寫文章，可以将markdown生成後的HTML複制到網站上進行送出，mac下推薦使用MacDown軟體。

Getting started 

• Installing Go  ( https://golang.google.cn/doc/install )  Instructions for downloading and installing Go.
• Tutorial: Getting started  ( https://golang.google.cn/doc/tutorial/getting-started.html ) A brief Hello, World tutorial to get started. Learn a bit about Go code, tools, packages, and modules.（該章節已翻譯）
• Tutorial: Create a module ( https://golang.google.cn/doc/tutorial/create-module.html )   A tutorial of short topics introducing functions, error handling, arrays, maps, unit testing, and compiling.
• Writing Web Applications (https://golang.google.cn/doc/articles/wiki/) Building a simple web application.
• How to write Go code ( https://golang.google.cn/doc/code.html )This doc explains how to develop a simple set of Go packages inside a module, and it shows how to use the 

  go

   command( https://golang.google.cn/cmd/go/ ) to build and test packages.

A Tour of GoAn interactive introduction to Go in three ps. The first p covers basic syntax and data structures; the second discusses methods and interfaces; and the third introduces Go’s concurrency primitives. Each p concludes with a few exercises so you can practice what you’ve learned. You can install it locally with:$ go get golang.org/x/tour This will place the 

tour

 binary in your workspace’s 

bin

 directory.

Using and understanding Go

• Effective Go ( https://golang.google.cn/doc/effective_go.html ) A document that gives tips for writing clear, idiomatic Go code. A must read for any new Go programmer. It augments the tour and the language specification, both of which should be read first.
• Editor plugins and IDEs ( https://golang.google.cn/doc/editors.html ) A document that summarizes commonly used editor plugins and IDEs with Go support.
• Diagnostics ( https://golang.google.cn/doc/diagnostics.html ) Summarizes tools and methodologies to diagnose problems in Go programs.
• Managing dependencies ( https://golang.google.cn/doc/modules/managing-dependencies ) When your code uses external packages, those packages (distributed as modules) become dependencies.

Developing modules

• Developing and publishing modules ( https://golang.google.cn/doc/modules/developing )

You can collect related packages into modules, then publish the modules for other developers to use. This topic gives an overview of developing and publishing modules.

• Module release and versioning workflow ( https://golang.google.cn/doc/modules/release-workflow )

When you develop modules for use by other developers, you can follow a workflow that helps ensure a reliable, consistent experience for developers using the module. This topic describes the high-level steps in that workflow.

• Managing module source ( https://golang.google.cn/doc/modules/managing-source )

When you’re developing modules to publish for others to use, you can help ensure that your modules are easier for other developers to use by following the repository conventions described in this topic.

• Developing a major version update ( https://golang.google.cn/doc/modules/major-version )

A major version update can be very disruptive to your module’s users because it includes breaking changes and represents a new module. Learn more in this topic.

• Publishing a module ( https://golang.google.cn/doc/modules/publishing )

When you want to make a module available for other developers, you publish it so that it’s visible to Go tools. Once you’ve published the module, developers importing its packages will be able to resolve a dependency on the module by running commands such as go get.

• Module version numbering ( https://golang.google.cn/doc/modules/version-numbers )

A module’s developer uses each part of a module’s version number to signal the version’s stability and backward compatibility. For each new release, a module’s release version number specifically reflects the nature of the module’s changes since the preceding release.

• Frequently Asked Questions (FAQ) ( https://golang.google.cn/doc/faq ) Answers to common questions about Go.

References

• Package Documentation ( https://golang.google.cn/pkg/ ) The documentation for the Go standard library.
• Command Documentation ( https://golang.google.cn/doc/cmd ) The documentation for the Go tools.
• Language Specification ( https://golang.google.cn/ref/spec ) The official Go Language specification.
• Go Modules Reference ( https://golang.google.cn/ref/mod ) A detailed reference manual for Go’s dependency management system.

• go.mod file reference ( https://golang.google.cn/doc/modules/gomod-ref )

Reference for the directives included in a go.mod file.

• The Go Memory Model ( https://golang.google.cn/ref/mem ) A document that specifies the conditions under which reads of a variable in one goroutine can be guaranteed to observe values produced by writes to the same variable in a different goroutine.
• Release History ( https://golang.google.cn/doc/devel/release.html ) A summary of the changes between Go releases.