github.com/spotify/syslog-redirector-golang@v0.0.0-20140320174030-4859f03d829a/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="http://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="http://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="http://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  <p>A summary of the changes between Go releases.</p>
    34  
    35  <h4 id="go1notes"><a href="/doc/go1">Go 1 Release Notes</a></h4>
    36  <p>
    37  A guide for updating your code to work with Go 1.
    38  </p>
    39  
    40  <h4 id="go1.1notes"><a href="/doc/go1.1">Go 1.1 Release Notes</a></h4>
    41  <p>
    42  A list of significant changes in Go 1.1, with instructions for updating your
    43  code where necessary.
    44  </p>
    45  
    46  <h4 id="go1.2notes"><a href="/doc/go1.2">Go 1.2 Release Notes</a></h4>
    47  <p>
    48  A list of significant changes in Go 1.2, with instructions for updating your
    49  code where necessary.
    50  </p>
    51  
    52  <h3 id="go1compat"><a href="/doc/go1compat">Go 1 and the Future of Go Programs</a></h3>
    53  <p>
    54  What Go 1 defines and the backwards-compatibility guarantees one can expect as
    55  Go 1 matures.
    56  </p>
    57  
    58  
    59  <h2 id="resources">Developer Resources</h2>
    60  
    61  <h3 id="source"><a href="https://code.google.com/p/go/source">Source Code</a></h3>
    62  <p>Check out the Go source code.</p>
    63  
    64  <h3 id="golang-dev"><a href="http://groups.google.com/group/golang-dev">Developer Mailing List</a></h3>
    65  <p>The <a href="http://groups.google.com/group/golang-dev">golang-dev</a>
    66  mailing list is for discussing and reviewing code for the Go project.</p>
    67  <p>For general discussion of Go programming, see <a
    68  href="http://groups.google.com/group/golang-nuts">golang-nuts</a>.</p>
    69  
    70  <h3 id="golang-checkins"><a href="http://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="http://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="http://code.google.com/p/go/issues">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="http://code.google.com/p/go/issues/entry">filing a ticket</a>
    86  on our <a href="http://code.google.com/p/go/issues">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  <h3><a href="/doc/contribute.html">Contributing code</a></h3>
    96  
    97  <p>
    98  Go is an open source project and we welcome contributions from the community.
    99  </p>
   100  <p>
   101  To get started, read these <a href="/doc/contribute.html">contribution
   102  guidelines</a> for information on design, testing, and our code review process.
   103  </p>
   104  <p>
   105  Check <a href="http://code.google.com/p/go/issues">the tracker</a> for 
   106  open issues that interest you. Those labeled
   107  <a href="http://code.google.com/p/go/issues/list?q=status=HelpWanted">HelpWanted</a>
   108  are particularly in need of outside help.
   109  </p>