r/debian • u/LiveVegetable • Jul 25 '21
Open source projects need to migrate their code away from github NOW!
If you're writing any kind of open source code and storing it on GitHub, you need to move it away from the platform NOW!
24
u/DanLynch Jul 25 '21
Even if an open source project were to "migrate away" from GitHub, anyone could just make a copy of the project and upload it anywhere they want, including to GitHub. That's the whole point of open source.
Closed-source/non-free projects are the only ones who can effectively migrate away from GitHub.
40
u/FPiN9XU3K1IT Jul 25 '21
What prevents Microsoft from copying public code from elsewhere and then train their AI with it? And how are code suggestions worse than literally selling FOSS, which is something you can do under most FOSS licenses?
16
u/Kare11en Jul 25 '21
What prevents Microsoft from copying public code from elsewhere?
When you sign up to Github, the terms of service that you voluntarily agree to, explicitly give Github a bunch of extra rights to the code you post there.
If you do not sign up to Github, you do not agree to those terms, and have not given them a bunch of extra rights.
That said, moving your code off of Github does not cancel the terms of service that you already agreed to, and the rights you've given them to any code you upload probably have a "perpetual" and "irrevocable" in there somewhere. (TBF most licenses do. The GPL is "for the term of copyright on the Program" which is effectively perpetual, and is "irrevocable provided the stated conditions are met.")
how are code suggestions worse than literally selling FOSS?
You're allowed to sell FOSS. Other people are allowed to sell your FOSS, provided they adhere to the other terms of your FOSS license. What other people are not allowed to do is make a derivative work of your FOSS, claim that it's actually their code, put whatever license they want on it, and then sell that. Github Copilot gives "suggestions" which, according to Github, are not a derivative work of the code it was trained on, and therefore don't have to be released under a compatible or FOSS license.
7
Jul 25 '21
MS can always clone a repo from elsewhere and upload to Github themselves. Unless, the project has a license that prohibits any form of cloning or forking of course.
7
u/brennanfee Jul 25 '21
When you sign up to Github, the terms of service that you voluntarily agree to, explicitly give Github a bunch of extra rights to the code you post there.
Which is the case with anywhere else you might decide to hose your code. Unless you intend to self-host (and pay for that), there is no real way to avoid this. Furthermore, by self-hosting, you lose the whole community aspect that those platforms provide.
0
Jul 26 '21
[deleted]
2
u/brennanfee Jul 26 '21
but it is a piece of Github's marketing that you have internalized.
I wasn't speaking specifically of GitHub. Could be BitBucket, GitLab... whatever. And I do NOT believe that it is FUD. The public and well-known nature of the sites is what brings people around and fosters that community. If you self-host a server, even on the internet, you and the 3 other people that know you will be involved but others won't "find" it unless YOU specifically seek them out and bring them to your server.
The fact is people stumble upon projects all the time on sites like the ones I mentioned above. Why? Because they are PUBLIC and POPULAR.
Just for example (and because this in on /r/debian), the Debian project
Bad example as they pretty much pre-dated the web (I know, I was there - and still am), so of course lots of people are going to know about that project.
1
u/Leseratte10 Jul 28 '21
I'd definitely say you lose some contributors. I can't speak for others, but when I am using a piece of software I downloaded from Github and notice an issue, I'm way more likely to write a quick bug report (or, if it's a very small fix, maybe even make a PR myself) than if that particular software used another hoster where I don't have an account on yet, or worse, uses their own platforms for Git and issue tracking.
5
u/DeliciousIncident Jul 26 '21
Selling FOSS software is one thing, if you sell a GPL software - it's still GPL, but allowing a proprietary software to include large chunks of your GPL code while ignoring the GPL license is another matter entirely. Copilot basically washes away all the license and copyrights of the code it generates, exploiting open source projects without respecting their licensing. That's the problem.
23
u/ABotelho23 Jul 25 '21
I'm not sure how this would only apply to GitHub? I guess it's easier?
Someone could literally just grab a machine with a bunch of storage and git clone the top 1000 projects on GitLab. What's stopping them?
11
u/Zipdox Jul 25 '21
GitLab TOS or licenses
8
u/ABotelho23 Jul 25 '21
And what would the license have to say to prevent such a thing?
2
u/Zipdox Jul 25 '21
Something stating that if the code is used for machine learning, the output should be licensed under the same license.
2
1
u/LcuBeatsWorking Jul 26 '21
But why? That reminds me of all those failed licenses who tried to exclude specific use cases.
1
u/Zipdox Jul 26 '21
No, it doesn't prohibit any use of the software, just use of the code.
1
u/LcuBeatsWorking Jul 26 '21
Almost all licenses deal with copyright and distribution.
What you suggest is to limit is what the code is used for personally. Like saying "You are not allowed to read this code on an apple computer".
1
u/Zipdox Jul 26 '21
A human reading code is something completely different than a machine using it.
1
0
1
u/DeliciousIncident Jul 26 '21
Anyone can re-upload your open source GitLab projects to GitHub, making GitHub ToS apply to them. Heck, even Microsoft themselves could do it. So no, hosting code somewhere else is not a 100% bulletproof way of avoiding it from being used by GitHub's Copilot.
1
0
u/JmbFountain Jul 26 '21
git pull git@gitlab:repo/name git remote add github [email protected]:some/repo git push -u github
15
u/jarfil Jul 25 '21 edited Dec 02 '23
CENSORED
-1
u/Kare11en Jul 26 '21
How about, some people might not want their FLOSS code to be used to make suggestions to other people who are using Copilot's to write non-FLOSS code? Especially FLOSS authors who release their code under copyleft licenses.
"Just don't use Copilot" completely misunderstands FLOSS authors' worries about who is going to be using the suggestions, and what they're going to be using them for - or, what license those suggestions are going to be released under.
6
u/jarfil Jul 26 '21 edited Dec 02 '23
CENSORED
-1
u/Kare11en Jul 26 '21
Copying code doesn't change its license, anyone releasing non-trivial suggestions under an incompatible license, will just become an easy target for a lawsuit.
Riiight. Given that Github claims that any suggestions made by Copilot are not a derivative work of the training data that informed those suggestions, it seems likely that they would step in to defend any proprietary vendor who had used it and was a target of such a lawsuit, to maintain Copilot's value. Sorry, did I say Github? Silly me, I meant Microsoft.
So, the copyright lawsuit of J. Random Hobbyist FLOSS Developer vs. Microsoft Corp. I must admit, I admire your notion of what constitutes an "easy target".
5
2
u/LcuBeatsWorking Jul 26 '21
some people might not want their FLOSS code to be used to make suggestions to
other people
Then put your code under a license excluding this specific usage scenario. Non of the classic FOSS licenses do that AFAIK.
But I predict such restrictive licensing won't be very popular.
0
u/Kare11en Jul 26 '21
Then put your code under a license excluding this specific usage scenario.
Whether or not that's necessary depends entirely on whether the law considers Copilot's suggestions "derivative works" of its inputs under copyright, or not.
And no-one knows whether that's going to be the case until the issue makes it to a courtroom and a verdict is given.
Until then, I think it's an issue reasonable people can respectfully disagree on. That said, I think that code coming out of such a tool is derivative of the code that went into it, and no extra license restrictions should be necessary to prevent it.
The fact that Github disagrees and is going ahead with this anyway is, in my opinion, therefore a good reason not to place new FOSS code on Github, and to remove existing code from there so that any future modifications don't fall under whatever Github T&Cs might allow this in spite of the declared license.
The alternative option is to bring a lawsuit against
GithubMicrosoft in order to make the law settle the issue. Good luck with that.1
u/LcuBeatsWorking Jul 26 '21
The alternative option is to bring a lawsuit against
Github
Microsoft in order to make the law settle the issue.
For that to have standing you would need an instance for your own code being used in a project with an incompatible license.
And even then not copilot commits the violation, but the user of that repository.
0
u/Kare11en Jul 26 '21
even then not copilot commits the violation, but the user of that repository.
I'm pretty sure that trafficking in tools that help/encourage others to commit copyright violations are also now illegal, thanks to the efforts of the MPAA/RIAA against Napster and all its successors.
The issue of "standing" is, I admit, thornier.
But, if bringing lawsuits isn't just hard because Github/Microsoft have a much bigger legal department with much deeper pockets than you do, but also because proving that your code specifically has been infringed, and the need to show that Copilot falls into the category of "circumvention tools", then isn't that all the more reason to take an alternative means of make your code as hard to co-opt by Copilot as possible? Such as, for instance, just off the top of my head, migrating your code away from github?
1
u/DeliciousIncident Jul 26 '21
and to remove existing code from there so that any future modifications don't fall under whatever Github T&Cs might allow this in spite of the declared license.
Anyone can upload your future modifications back on GitHub though, even Microsoft themselves. FOSS licenses don't restrict who can copy your code and where they can upload it, nor does GitHub ToS require the uploader to own copyright on the code uploaded.
2
u/djav1985 Jul 26 '21
Doesn't matter where you move the open source project they're going to be in a environment that isn't shielded from external reading. So you could just point the AI in the new popular place in scan the code. Short of hiding your code behind a wall and authorization it was still be usable by something like that.
1
u/DeliciousIncident Jul 26 '21
Open source licenses don't restrict any use. Your code can't be FLOSS and disallow being used in GitHub's Copilot at the same time.
1
u/Kare11en Jul 26 '21
Free Software/copyleft licenses restrict making derivative works which are not licensed under the same (or compatible) terms.
1
u/DeliciousIncident Jul 26 '21
Yep, that's right. What's annoying about Copilot though is that the users of it are a lot less councious of where the generated code comes from than if they were manually checking source code of different repos. They don't know which projects the code comes from (Copilot doesn't tell that) and might not even know that the code is a derived work. Copilot is unusable for any purpose (other than license violation lol) as it is right now. So literally useless. No idea why Microsoft has released it.
5
u/LcuBeatsWorking Jul 26 '21
I do not get it:
I publish my code under a free license because I want others to do stuff with it. I do not limit specific use cases.
If Copilot copies chunks of my code into a project with an incompatible license, that would obviously be a license violation, but it doesn't matter if it is done by a coder or via copilot.
Software licenses are about distribution of code, not about what it is used for.
If you believe that copilot is a violation of GPL/MIT/Apache etc then point out how, otherwise migrating elsewhere does not change anything.
1
Jul 27 '21
Issue is that Github is telling people that they own the code generated by Copilot (see their faq on this page). Depending on one's interpretation, that statement is either likely to be false, or it's basically saying "you're responsible for any license violations you commit," without providing any reliable way for users to ensure that they are abiding by the correct license terms when Copilot generates code for them.
1
3
u/Zipdox Jul 25 '21
I have quite a bit of stuff on GitHub that I'd have to migrate.
4
u/karafili Jul 25 '21
Git clone Git remote remove origin Git remote add origin <new git repo url here>Done
3
u/sumduud14 Jul 25 '21
Can just do
git remote set-url origin <new url>instead of removing and re-adding.2
1
1
u/talkingsackofmeat Jul 25 '21
If only there existed a utility that stored branched and version controlled copies of your efforts so you wouldn't need to retype everything.
1
u/necheffa Jul 25 '21
Sadly, uploading your git repository elsewhere isn't the end of the story. I suspect a lot of folks that use the issue tracker and project management tools would have a pretty significant investment to migrate.
Some competitors offer tooling to ease the migration as an enticement but not everyone does.
-2
u/talkingsackofmeat Jul 26 '21
I've seen raw code projects on github that back up your issue tracker / wiki to git repos. Theoretically, at that point, it's structured data that can be migrated with your standard ETL pipeline.
-1
u/Zipdox Jul 25 '21
Yeah but effort is effort still.
1
u/talkingsackofmeat Jul 25 '21
Yeah, I may not get to it this year either. It's on the todo list, but like 40 items down.
0
-1
u/karafili Jul 25 '21
Been using gitlab for a while. Had gitlab runners integrations for free the last 4 years
2
u/CalcProgrammer1 Jul 26 '21
GitLab has been pretty great for me. I still mirror my stuff to GitHub though.
-5
Jul 26 '21 edited Jul 26 '21
GitHub Copilot is an AI that is being trained on the publicly available source code and texts in the GitHub repositories. The AI produces code suggestions to programmers in real time.
This is what scares me the most. I thought that this technology was a lot further away. I am traditionally opposed to government regulation, but the lack of regulation of AI is extremely foolish and may do us all away with our jobs (at the very least) in the end. Elon has warned us about this for years:
https://www.youtube.com/watch?v=B-Osn1gMNtw
EDIT: Elon is more worried about the existential threat of digital super intelligence, not narrow AI such as Copilot. However, job security is still at risk for programmers.
-17
u/KeepLicking Jul 25 '21
Too bad this won't fly on /r/linux, those nazi mods will come up with all kinds of excuses to remove it
0
Jul 25 '21
[deleted]
5
u/necheffa Jul 25 '21
I think it comes down to licensing and how you interpret derivative work.
If you've gone and licensed your code MIT or similar then you probably don't care either way. But if you've licensed GPL2/GPL3 and consider code generated by an AI trained on your code a derivative work then you might be a little angry if someone uses that AI to generate code under a proprietary license. OP is looking at it as the new "tivoization".
2
u/LcuBeatsWorking Jul 26 '21
But if you've licensed GPL2/GPL3 and consider code generated by an AI trained on your code a derivative work
This would be a massive stretch to interpret the GPL like that.
2
u/necheffa Jul 26 '21
Normally I might agree. However gifs of Copilot straight up copying code line by line from training data and slapping a different license on it are infamous at this point.
2
u/DeliciousIncident Jul 26 '21
Copilot basically washes away all the license and copyrights of the code it generates, exploiting open source projects without respecting their licensing. Someone might be writing a proprietary software and use Copilot to generate code which is heavily based on your GPL code, yet they don't have to respect the GPL license, they can completely ignore it and treat tne code as if it was public domain instead. That's the problem. And it's not only GPL, most licenses require some things out of derivative works, like MIT requires copy of the license and copyrights to be included, yet Copilot washes that requirement away too.
So there is very much a lot of wrong and unintended with this.
24
u/VelvetElvis Jul 25 '21
Upload a bunch of faulty code just to fuck with the AI.