<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>CONTRIBUTING.md - fork/rules_rust @ 0.5.0</title>
<meta name="description" content="CONTRIBUTING.md in fork/rules_rust at 0.5.0.">
<meta property="og:title" content="CONTRIBUTING.md - fork/rules_rust @ 0.5.0">
<meta property="og:description" content="CONTRIBUTING.md in fork/rules_rust at 0.5.0.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="0.5.0" data-tip="121d65fe6a037b4ff77ec43845e128c7daf8a235">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/rules_rust</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/rules_rust</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">Kristina Chodorow</span><span class="commit-message" data-commit="5c4faadf4ce04743d4ddb502f84c89b27264426e">Move rust rules to their own repository</span><span class="snapshot-sha sha" data-commit="5c4faadf4ce04743d4ddb502f84c89b27264426e">5c4faadf</span><time datetime="2016-03-04T13:40:15-05:00" title="2016-03-04 13:40:15 -0500">2016-03-04</time></p>
<header class="topbar"><details class="switcher"><summary>0.5.0</summary><div class="menu"><strong>branches</strong><a href="/fork/rules_rust/ref/cleanup/">cleanup</a><a href="/fork/rules_rust/ref/gh-pages/">gh-pages</a><a href="/fork/rules_rust/ref/main/">main</a><a href="/fork/rules_rust/ref/patching/">patching</a><a href="/fork/rules_rust/ref/rust-analyzer/">rust-analyzer</a><strong>tags</strong><a href="/fork/rules_rust/ref/0.10.0/">0.10.0</a><a href="/fork/rules_rust/ref/0.11.0/">0.11.0</a><a class="current" href="/fork/rules_rust/ref/0.5.0/">0.5.0</a><a href="/fork/rules_rust/ref/0.6.0/">0.6.0</a><a href="/fork/rules_rust/ref/0.7.0/">0.7.0</a><a href="/fork/rules_rust/ref/0.8.0/">0.8.0</a><a href="/fork/rules_rust/ref/0.8.1/">0.8.1</a><a href="/fork/rules_rust/ref/0.9.0/">0.9.0</a><a class="all" href="/fork/rules_rust/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/rules_rust/">rules_rust</a> / <span class="cur">CONTRIBUTING.md</span></nav>
<span class="view-stats"><span>1.4 KiB</span><span>27 lines</span></span><span class="actions"><a class="raw" href="/fork/rules_rust/raw/9d3d1aaf8a32d1fdf4775975a66d9eae758da799/CONTRIBUTING.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><p>Want to contribute? Great! First, read this page (including the small print at the end).</p>
<h3>Before you contribute</h3>
<p><strong>Before we can use your code, you must sign the
<a href="https://developers.google.com/open-source/cla/individual?csw=1">Google Individual Contributor License Agreement</a>
(CLA)</strong>, which you can do online.</p>
<p>The CLA is necessary mainly because you own the copyright to your changes,
even after your contribution becomes part of our codebase, so we need your
permission to use and distribute your code. We also need to be sure of
various other things — for instance that you'll tell us if you know that
your code infringes on other people's patents. You don't have to sign
the CLA until after you've submitted your code for review and a member has
approved it, but you must do it before we can put your code into our codebase.</p>
<p>Before you start working on a larger contribution, you should get in touch
with us first. Use the issue tracker to explain your idea so we can help and
possibly guide you.</p>
<h3>Code reviews and other contributions.</h3>
<p><strong>All submissions, including submissions by project members, require review.</strong>
Please follow the instructions in <a href="http://bazel.io/contributing.html">the contributors documentation</a>.</p>
<h3>The small print</h3>
<p>Contributions made by corporations are covered by a different agreement than
the one above, the
<a href="https://cla.developers.google.com/about/google-corporate">Software Grant and Corporate Contributor License Agreement</a>.</p>
</section><div class="code-panel"><pre class="code src language-markdown"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text">Want to contribute? Great! First, read this page (including the small print at the end).</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text"><a-p>###</a-p> <a-tt>Before you contribute</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text">**Before we can use your code, you must sign the</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text">[Google Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual?csw=1)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text">(CLA)**, which you can do online.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text">The CLA is necessary mainly because you own the copyright to your changes,</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text">even after your contribution becomes part of our codebase, so we need your</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text">permission to use and distribute your code. We also need to be sure of</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text">various other things — for instance that you&#39;ll tell us if you know that</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text">your code infringes on other people&#39;s patents. You don&#39;t have to sign</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text">the CLA until after you&#39;ve submitted your code for review and a member has</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L14" href="#L14">14</a><span class="code-text">approved it, but you must do it before we can put your code into our codebase.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L15" href="#L15">15</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L16" href="#L16">16</a><span class="code-text">Before you start working on a larger contribution, you should get in touch</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L17" href="#L17">17</a><span class="code-text">with us first. Use the issue tracker to explain your idea so we can help and</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L18" href="#L18">18</a><span class="code-text">possibly guide you.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L19" href="#L19">19</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L20" href="#L20">20</a><span class="code-text"><a-p>###</a-p> <a-tt>Code reviews and other contributions.</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L21" href="#L21">21</a><span class="code-text">**All submissions, including submissions by project members, require review.**</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L22" href="#L22">22</a><span class="code-text">Please follow the instructions in [the contributors documentation](http://bazel.io/contributing.html).</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L23" href="#L23">23</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L24" href="#L24">24</a><span class="code-text"><a-p>###</a-p> <a-tt>The small print</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L25" href="#L25">25</a><span class="code-text">Contributions made by corporations are covered by a different agreement than</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L26" href="#L26">26</a><span class="code-text">the one above, the</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L27" href="#L27">27</a><span class="code-text">[Software Grant and Corporate Contributor License Agreement](https://cla.developers.google.com/about/google-corporate).</span></span></pre></div></div>
</main>
</body>
</html>
