Home | History | Annotate | Download | only in doc
      1 <!--{
      2 	"Title": "Help",
      3 	"Path": "/help/"
      4 }-->
      5 
      6 <div id="manual-nav"></div>
      7 
      8 <h2 id="help">Get help</h2>
      9 
     10 <img class="gopher" src="/doc/gopher/help.png"/>
     11 
     12 <h3 id="mailinglist"><a href="https://groups.google.com/group/golang-nuts">Go Nuts Mailing List</a></h3>
     13 <p>
     14 Get help from Go users, and share your work on the official mailing list.
     15 </p>
     16 <p>
     17 Search the <a href="https://groups.google.com/group/golang-nuts">golang-nuts</a>
     18 archives and consult the <a href="/doc/go_faq.html">FAQ</a> and
     19 <a href="//golang.org/wiki">wiki</a> before posting.
     20 </p>
     21 
     22 <h3 id="forum"><a href="https://forum.golangbridge.org/">Go Forum</a></h3>
     23 <p>
     24 The <a href="https://forum.golangbridge.org/">Go Forum</a> is a discussion
     25 forum for Go programmers.
     26 </p>
     27 
     28 <h3 id="slack"><a href="https://blog.gopheracademy.com/gophers-slack-community/">Gopher Slack</a></h3>
     29 <p>Get live support from other users in the Go slack channel.</p>
     30 
     31 <h3 id="irc"><a href="irc:irc.freenode.net/go-nuts">Go IRC Channel</a></h3>
     32 <p>Get live support at <b>#go-nuts</b> on <b>irc.freenode.net</b>, the official
     33 Go IRC channel.</p>
     34 
     35 <h3 id="faq"><a href="/doc/faq">Frequently Asked Questions (FAQ)</a></h3>
     36 <p>Answers to common questions about Go.</p>
     37 
     38 <h2 id="inform">Stay informed</h2>
     39 
     40 <h3 id="announce"><a href="https://groups.google.com/group/golang-announce">Go Announcements Mailing List</a></h3>
     41 <p>
     42 Subscribe to
     43 <a href="https://groups.google.com/group/golang-announce">golang-announce</a>
     44 for important announcements, such as the availability of new Go releases.
     45 </p>
     46 
     47 <h3 id="blog"><a href="//blog.golang.org">Go Blog</a></h3>
     48 <p>The Go project's official blog.</p>
     49 
     50 <h3 id="twitter"><a href="https://twitter.com/golang">@golang at Twitter</a></h3>
     51 <p>The Go project's official Twitter account.</p>
     52 
     53 <h3 id="pluscom"><a href="https://plus.google.com/communities/114112804251407510571">Go+ community</a></h3>
     54 <p>A Google+ community for Go enthusiasts.</p>
     55 
     56 <h3 id="reddit"><a href="https://reddit.com/r/golang">golang sub-Reddit</a></h3>
     57 <p>
     58 The <a href="https://reddit.com/r/golang">golang sub-Reddit</a> is a place
     59 for Go news and discussion.
     60 </p>
     61 
     62 <h2 id="community">Community resources</h2>
     63 
     64 <h3 id="go_user_groups"><a href="/wiki/GoUserGroups">Go User Groups</a></h3>
     65 <p>
     66 Each month in places around the world, groups of Go programmers ("gophers")
     67 meet to talk about Go. Find a chapter near you.
     68 </p>
     69 
     70 <h3 id="playground"><a href="/play">Go Playground</a></h3>
     71 <p>A place to write, run, and share Go code.</p>
     72 
     73 <h3 id="wiki"><a href="/wiki">Go Wiki</a></h3>
     74 <p>A wiki maintained by the Go community.</p>
     75 
     76 <h3 id="conduct"><a href="/conduct">Code of Conduct</a></h3>
     77 <p>
     78 Guidelines for participating in Go community spaces
     79 and a reporting process for handling issues.
     80 </p>
     81 
     82