3 ms·
Unfortunately the tone I'm getting from many of these comments makes me feel that people see open source projects as a resource to be mined rather than as a pro
by cmrdporcupine 4y ago
Unfortunately the tone I'm getting from many of these comments makes me feel that people see open source projects as a resource to be mined rather than as a product to be respected. A very entitled attitude ("I really don't want to lose my lovely tool")
There seems to be -- on the whole -- little respect for the spirit of the GPL and LGPL and it really is quite a change from, say, 20 years ago, when the 'free software' movement was I think more ascendant.
I think we have a generation of software developers who have only known a world where copious quantities of high quality source code has been made available to them under very liberal licenses -- which they in turn make careers and companies out of using / exploiting.
I, too, do this, and I generally open my modest projects under Apache or MIT or Mozilla style licenses. I do this because I want people to use my things, or to be able to use them as resume / portfolio material. Or because my employer at the time has helped fund construction of them.
But I also occasionally use the GPL/LGPL/AGPL, when I want to explicitly avoid corporate entities from exploiting said material without either consulting with me or in turn making their efforts free.
And in turn, I respect the value and power of the GPL for that purpose.
So many of the comments here are trivializing the value of free software and the licenses which make it possible, and acting like there's just this... natural right... to go out there and build on other people's work without recognition / compensation / contribution.
There are too many examples of CoPilot violating the spirit -- if not the actual legal letter -- of the GPL. This is unacceptable. I'm glad that someone is attempting a legal test.
Free software is not your data to mine. It is the blood sweat and tears of thousands of developers who do their work in community spirit, but under explicitly free software principles.
Putting something out under a free software copyleft-style license is not the same as saying "You can do with this what you want." It's "I made this, you can build on it, but what you made also has to be free. Or you negotiate with me."
And what I'm getting from the whole CoPilot fiasco is: GPL / free software does not belong on GitHub. And it might end up having to be put, generally, behind barriers that explicitly (technically and legally) prevent CoPilot & similar systems from getting access to it.
EDIT: I also fully expect a new version of the GPL to be published that includes clauses against this kind of datamining.
- judge2020 4y agoWhat do you expect when people grant GitHub an extra license to their repos[0]? 0: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#4-license-grant-to-us https://docs.github.com/en/site-policy/github-terms/github-t...
- xyzzy_plugh 4y agoThis can't possibly hold up in court, can it? I have multiple repos that are mirrors of various open source projects. Some are not even Free Software! I have no right to grant such things to anyone let alone GitHub.
- ghoward 4y agoMy code is not on GitHub. If it's there, then someone copied it, and GitHub has no right to claim an extra license to that code.
- nsajko 4y agoThis particular licensing term doesn't seem relevant to Copilot.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- an1sotropy 4y agoAgreed. Something else apparent from the comments is that people seem to think that some things are copyrighted, and some aren't, and that copilot would be better if it could avoid copyrighted code. Actually, essentially ALL code is copyrighted, and was so the moment it was written, and someone owns that copyright [1]. People only start noticing copyright when the terms of how that copyrighted content is licensed affects them. I think people resent reciprocal licenses like LGPL/GPL because the principle of "share and share alike" that they implement comes with real responsibilities and consequences for the user of the code, while they believe that non-reciprocal licenses (BSD) can be ignored with less serious consequences. But the show-stopping problem is that copilot is sometimes producing code that is more than fair use of other code that, and is unable to attribute the code or identify how that code is licensed. It is copilot's (Microsoft's) fault that it auto-generates legal minefields, not the person who made an informed decision about licensing their own code. In spite of the likely downvoting, I'll say that people should be grateful for reciprocal licenses not just because they were and are the foundation of free software (as you point out), but because they shine a light on what it means to license code, and how we are forced to revisit the difference between copyright and licensing when a reciprocal license is violated. [1] https://en.wikipedia.org/wiki/Berne_Convention https://en.wikipedia.org/wiki/Berne_Convention