Does Github&#39;s License Grant clause in the ToS make one legally liable?
<p>The popular <a href="https://en.wikipedia.org/wiki/Git" rel="nofollow noreferrer">Git</a> Repository hosting service used by many open-source projects Github recently adopted a new <a href="https://help.github.com/articles/github-terms-of-service/" rel="nofollow noreferrer">Terms of Service</a>. </p>

<p>I am puzzled by the implications of the <a href="https://help.github.com/articles/github-terms-of-service/#4-license-grant-to-us" rel="nofollow noreferrer">License Grant Section.</a> Which is reproduced below for reference:</p>

<blockquote>
  <ol start="4">
  <li>License Grant to Us</li>
  </ol>
  
  <p>Your Content belongs to you, and you are responsible for Content you
  post even if it does not belong to you. However, we need the legal
  right to do things like host it, publish it, and share it. You grant
  us and our legal successors the right to store and display your
  Content and make incidental copies as necessary to render the Website
  and provide the Service.</p>
  
  <p>That means you're giving us the right to do things like reproduce your
  content (so we can do things like copy it to our database and make
  backups); display it (so we can do things like show it to you and
  other users); modify it (so our server can do things like parse it
  into a search index); distribute it (so we can do things like share it
  with other users); and perform it (in case your content is something
  like music or video).</p>
  
  <p>This license does not grant GitHub the right to sell your Content or
  otherwise distribute it outside of our Service.</p>
</blockquote>

<p>It also includes <a href="https://help.github.com/articles/github-terms-of-service/#5-license-grant-to-other-users" rel="nofollow noreferrer">an additional License Grant to Github's Users</a>.</p>

<p>Particularly content that is posted to Github does not always belong to <em>one</em> user - it may for example be a project where many contributions from different collaborators were made under one the <a href="https://en.wikipedia.org/wiki/GNU_General_Public_License" rel="nofollow noreferrer">GPL</a> or <a href="https://en.wikipedia.org/wiki/BSD_licenses" rel="nofollow noreferrer">BSD</a> licenses. All of which include for example, required attribution. </p>

<p>While I or another user may personally may be in a position to give Github and <a href="https://help.github.com/articles/github-terms-of-service/#5-license-grant-to-other-users" rel="nofollow noreferrer">Github User's a License Grant</a> for my work; as far as I understand I can do no such thing on behalf of other users that made their contributions under the GPL or BSD family of licenses (unless a CLA specified that one may grant additional licenses beyond those under which they made their contributions). Since Github appears to indemnify themselves - </p>

<blockquote>
  <p>you are responsible for Content you post even if it does not belong to you. </p>
</blockquote>

<p>Does that mean that Github users uploading GPL or BSD licensed projects whose contributors have not explicitly given Github or Github User's License Grants as per the ToS are doing something potentially illegal?</p>

<p>As far as I can tell, whenever GitHub redistributes code, it adheres to all of the requirements of the GPL/BSD etc. For example, it never gives away code without including the license text, and it doesn't claim to add unpermitted restrictions to the code.</p>

<p>The section you're concerned about is this:</p>

<blockquote>
  <p>That means you're giving us the right to do things like reproduce your content (so we can do things like copy it to our database and make backups); display it (so we can do things like show it to you and other users); modify it (so our server can do things like parse it into a search index); distribute it (so we can do things like share it with other users); and perform it (in case your content is something like music or video).</p>
</blockquote>

<p>That section isn't worded very precisely, but I understand this to mean they want to reproduce your content <em>in full</em>, not just the code without the license text attached. They want to display your content <em>in full</em>, as you provided it. They want to modify it <em>internally</em> (i.e. they are not redistributing this modified form) in order to allow searching. To the extent that they display code-snippets as search results, that is likely defensible as fair use (search engines are frequently cited as examples of successful fair use defenses).</p>

<p>GitHub appears to be acting consistently with the GPL when it reproduces, displays, modifies, and distributes code that you upload. If I'm correct about these facts then nothing that GitHub does with the code goes beyond what the many contributors to a GPL project have explicitly permitted, or what is otherwise permitted by <a href="https://law.stackexchange.com/tags/fair-use/info">fair use</a> law.</p>

<p>If you had some code with a more restrictive license, you might not be able to simultaneously comply with that restrictive license <em>and</em> GitHub's License Grant. Consider the scenario where you have some code that is licensed exclusively to you, and you are not given permission to reproduce or distribute it. In that scenario, the code's license prevents you from agreeing to GitHub's request for a license grant.</p>

<p><strong>All</strong> users of Github are subject to the ToS so <strong>all</strong> users who upload are agreeing to this license with Github. This is independent and parallel to any license they give to the public at large.</p>

licensing terms-of-service gpl