GitHub Licensing Disputes

Discussions center on copyright ownership, MIT licensing, and usage rights for code uploaded to or forked on public GitHub repositories, including conflicts with GitHub's Terms of Service and unauthorized sharing.

📉 Falling 0.4x Open Source
5,364
Comments
20
Years Active
5
Top Authors
#9252
Topic ID

Activity Over Time

2007
3
2008
12
2009
26
2010
100
2011
102
2012
149
2013
180
2014
232
2015
308
2016
311
2017
291
2018
242
2019
282
2020
346
2021
690
2022
667
2023
496
2024
427
2025
477
2026
23

Keywords

US FOSS OSS LICENSE MIT LGPL TOS creativecommons.org AI FSF license github code copyright gpl source mit repos open source tos

Sample Comments

pxc Feb 1, 2023 View on HN

Did you forget the part where this code is MIT-licensed? Yes, they don't own it, but the code is still 'theirs' to keep forever as they see fit.

posix86 Mar 5, 2024 View on HN

Isn't the github way of doing things: You add a copyright notice to your code, identifying your repository as the source, and changing the copyright is illegal? That would be applicable to this as well.

bdonlan Aug 26, 2013 View on HN

It's under the MIT license and in a public github repo - shouldn't that be enough? If you don't want your code public, don't put it in a public repo (if you can't afford a private one, just use git locally) and certainly don't stick an open-source license on it.

danielki Jan 23, 2015 View on HN

As others have said - long as proper attribution is provided in the finished product, it's within the terms of the license that you put up. In the future:* If you don't want your code available to the public, use a private repository - either Github's paid plans or Bitbucket (free private repos) or something similar.* If you want your code publicly available, but not to be used in this way, use a different license - GPL/LGPL, CC BY-NC-SA, etc. Research to figure out whi

iab Oct 16, 2021 View on HN

If your code does not contain an explicit license, it is by default “All rights reserved”, I.e not open-source or free.For op, they are obviously in violation of the MIT open-source requirements, but unfortunately the ramifications for this are usually minimal.

SeanLuke Aug 22, 2021 View on HN

The Github terms do not indicate that the license is transferable. Github can display the code, but even if someone downloads from Github, they still can't use it.

gcr Jul 26, 2016 View on HN

Why does this give OP the right to violate the author's copyright by posting it to Github?

Etheryte Sep 24, 2024 View on HN

There is no conflict here. The quote from Github's ToS means you allow others to copy the source code you've made public, it cannot and does not give you any rights regarding what you do with the code beyond that. Points one and two of the Winamp license quote are essentially one and the same, just worded in a different way for clarity.

jatone Aug 23, 2021 View on HN

github TOS do not grant you use of others code. it grants distribution. those are two very different things.

sneak Oct 18, 2022 View on HN

Not all code on GitHub was uploaded by the copyright holder. The entire linux kernel is on GitHub and at least some of those copyright holders have never explicitly granted a license to GitHub beyond the GPL.