github.com/slayercat/go@v0.0.0-20170428012452-c51559813f61/doc/contrib.html (about)

     1  <!--{
     2  	"Title": "The Go Project",
     3  	"Path": "/project/"
     4  }-->
     5  
     6  <img class="gopher" src="/doc/gopher/project.png" />
     7  
     8  <div id="manual-nav"></div>
     9  
    10  <p>
    11  Go is an open source project developed by a team at
    12  <a href="//google.com/">Google</a> and many
    13  <a href="/CONTRIBUTORS">contributors</a> from the open source community.
    14  </p>
    15  
    16  <p>
    17  Go is distributed under a <a href="/LICENSE">BSD-style license</a>.
    18  </p>
    19  
    20  <h3 id="announce"><a href="//groups.google.com/group/golang-announce">Announcements Mailing List</a></h3>
    21  <p>
    22  A low traffic mailing list for important announcements, such as new releases.
    23  </p>
    24  <p>
    25  We encourage all Go users to subscribe to
    26  <a href="//groups.google.com/group/golang-announce">golang-announce</a>.
    27  </p>
    28  
    29  
    30  <h2 id="go1">Version history</h2>
    31  
    32  <h3 id="release"><a href="/doc/devel/release.html">Release History</a></h3>
    33  
    34  <p>A <a href="/doc/devel/release.html">summary</a> of the changes between Go releases. Notes for the major releases:</p>
    35  
    36  <ul>
    37  	<li><a href="/doc/go1.8">Go 1.8</a> <small>(February 2017)</small></li>
    38  	<li><a href="/doc/go1.7">Go 1.7</a> <small>(August 2016)</small></li>
    39  	<li><a href="/doc/go1.6">Go 1.6</a> <small>(February 2016)</small></li>
    40  	<li><a href="/doc/go1.5">Go 1.5</a> <small>(August 2015)</small></li>
    41  	<li><a href="/doc/go1.4">Go 1.4</a> <small>(December 2014)</small></li>
    42  	<li><a href="/doc/go1.3">Go 1.3</a> <small>(June 2014)</small></li>
    43  	<li><a href="/doc/go1.2">Go 1.2</a> <small>(December 2013)</small></li>
    44  	<li><a href="/doc/go1.1">Go 1.1</a> <small>(May 2013)</small></li>
    45  	<li><a href="/doc/go1">Go 1</a> <small>(March 2012)</small></li>
    46  </ul>
    47  
    48  <h3 id="go1compat"><a href="/doc/go1compat">Go 1 and the Future of Go Programs</a></h3>
    49  <p>
    50  What Go 1 defines and the backwards-compatibility guarantees one can expect as
    51  Go 1 matures.
    52  </p>
    53  
    54  
    55  <h2 id="resources">Developer Resources</h2>
    56  
    57  <h3 id="source"><a href="https://golang.org/change">Source Code</a></h3>
    58  <p>Check out the Go source code.</p>
    59  
    60  <h3 id="golang-dev"><a href="https://groups.google.com/group/golang-dev">Developer</a> and
    61  <a href="https://groups.google.com/group/golang-codereviews">Code Review Mailing List</a></h3>
    62  <p>The <a href="https://groups.google.com/group/golang-dev">golang-dev</a>
    63  mailing list is for discussing code changes to the Go project.
    64  The <a href="https://groups.google.com/group/golang-codereviews">golang-codereviews</a>
    65  mailing list is for actual reviewing of the code changes (CLs).</p>
    66  
    67  <p>For general discussion of Go programming, see <a
    68  href="https://groups.google.com/group/golang-nuts">golang-nuts</a>.</p>
    69  
    70  <h3 id="golang-checkins"><a href="https://groups.google.com/group/golang-checkins">Checkins Mailing List</a></h3>
    71  <p>A mailing list that receives a message summarizing each checkin to the Go repository.</p>
    72  
    73  <h3 id="build_status"><a href="//build.golang.org/">Build Status</a></h3>
    74  <p>View the status of Go builds across the supported operating
    75  systems and architectures.</p>
    76  
    77  
    78  <h2 id="howto">How you can help</h2>
    79  
    80  <h3><a href="//golang.org/issue">Reporting issues</a></h3>
    81  
    82  <p>
    83  If you spot bugs, mistakes, or inconsistencies in the Go project's code or
    84  documentation, please let us know by
    85  <a href="//golang.org/issue/new">filing a ticket</a>
    86  on our <a href="//golang.org/issue">issue tracker</a>.
    87  (Of course, you should check it's not an existing issue before creating
    88  a new one.)
    89  </p>
    90  
    91  <p>
    92  We pride ourselves on being meticulous; no issue is too small.
    93  </p>
    94  
    95  <p>
    96  Security-related issues should be reported to
    97  <a href="mailto:security@golang.org">security@golang.org</a>.<br>
    98  See the <a href="/security">security policy</a> for more details.
    99  </p>
   100  
   101  <p>
   102  Community-related issues should be reported to
   103  <a href="mailto:conduct@golang.org">conduct@golang.org</a>.<br>
   104  See the <a href="/conduct">Code of Conduct</a> for more details.
   105  </p>
   106  
   107  <h3><a href="/doc/contribute.html">Contributing code</a></h3>
   108  
   109  <p>
   110  Go is an open source project and we welcome contributions from the community.
   111  </p>
   112  <p>
   113  To get started, read these <a href="/doc/contribute.html">contribution
   114  guidelines</a> for information on design, testing, and our code review process.
   115  </p>
   116  <p>
   117  Check <a href="//golang.org/issue">the tracker</a> for 
   118  open issues that interest you. Those labeled
   119  <a href="https://github.com/golang/go/issues?q=is%3Aopen+is%3Aissue+label%3Ahelpwanted">helpwanted</a>
   120  are particularly in need of outside help.
   121  </p>