News for hackers. Stuff that matters.
Re:Copyright vs. Copyleft (2007) by cdogl on Saturday November 07, 2020 @06:44AM (#25014538)
I think the standard framing of copyleft as all about the user's rights is flawed. What we call copyright is a deeply flawed legal framework that helps to entrench rent-seeking and anti-competitive behaviour, but there's another side of the coin: the intent of the law is genuinely to guarantee access to the fruits of one's intellectual labour.

Of course, copyleft licenses such as the GPL _can_ be used to protect the authors' rights to compensation for commercial use of their work - but the framing matters. I think that's the fundamental reason open source licenses such as BSD and MIT have caught on - they centre on the need of the developer to get productive work done, not on the far more abstract principle of the home PC user being able to recompile their own software stack from source.

Re:Copyright vs. Copyleft (2007) by throwaway50203 on Saturday November 07, 2020 @08:41AM (#25015004)
> far more abstract principle of the home PC user being able to recompile their own software stack from source.

I contributed hundreds of hours of work into libraries. They are used by the same companies that sell me locked-down devices that I cannot modify or even inspect. They even invade the my privacy and I cannot disable that.

At least GPL tries to mitigate this problem. MIT turns volunteering into unpaid labor for some billionaires.

Calling it "far more abstract principle" is quite absurd.

These companies try hard to push the narrative that MIT is "practical" and GPL is "political" - guess why.

Re:Copyright vs. Copyleft (2007) by pmoriarty on Saturday November 07, 2020 @10:00AM (#25015416)
I release all my code under the AGPL.

However, I'm under no illusion that it'll prevent my unpaid work from being used by billionaires.

Setting aside those people/companies that are willing to violate the AGPL, even the ones that respect it are free to use it as long as they redistribute the source to modifications they make.

Anyone (including billionaires) could do that, and not every business model relies on keeping their source code secret.

Re:Copyright vs. Copyleft (2007) by throwaway50203 on Saturday November 07, 2020 @10:16AM (#25015515)
> However, I'm under no illusion that it'll prevent my unpaid work from being used by billionaires.

There's plenty of evidence that AGPL is reasonably effective at that. SaaS providers are clearly afraid of it.

> not every business model relies on keeping their source code secret.

I was never talking about secrecy and business model.

It's about allowing end users (including myself) to have some reasonable chances to inspect / update / reflash their devices.

Re:Copyright vs. Copyleft (2007) by est31 on Saturday November 07, 2020 @10:25AM (#25015568)
Note that the definition of "use" is important here. Many MIT advocates regard shipping parts of MIT licensed code inside a proprietary product as "using" it. And yes, in some ways they are right, but it's definitely not the only meaning of the term.

The GPL has a different usage definition: run and execute. E.g. think of an image manipulation program under the GPL. If you design a game, you run the program to create assets, but none of the created assets contain a trace of the original program any more. The game you ship doesn't either. The GPL doesn't affect you. However, if you tried copying one of the algorithms implemented in the program into your own proprietary competitor, you infringe on the copyright now.

Re:Copyright vs. Copyleft (2007) by geofft on Saturday November 07, 2020 @01:36PM (#25017253)
Are you happier with locked-down devices that you cannot modify or even inspect that invade your privacy as long as they don't use your code?

Anyway, I certainly think the MIT license is political - I also believe in the political position of free education for all people, even if they're billionaires (or children of billionaires), and in the political position that I should be taxed to provide these services for people richer than me. I donate to charities that help people who do not repay me. And so forth.

If some billionaires want to profit off of unpaid labor, don't think you can stop it by using the GPL, which relies on the legal system and copyright laws that made them billionaires in the first place. If you sue them for infringing the GPL, you might have a great strategy to win their game, but you're still playing their game in their courts. There's a saying from a totally different context that applies here too, I think: the master's tools will never dismantle the master's house. We've had the GPL for decades now and the result is there's a lot of billionaires whose fortunes were made via GPL'd software like Linux.

If you want to get rid of billionaires, or of freeloading billionaires, or of locked-down devices, or of invasions of privacy, take action against that thing. Do not fall into the trap of "Something must be done, and the GPL is something."

Re:Copyright vs. Copyleft (2007) by carapace on Saturday November 07, 2020 @11:53AM (#25016220)
This. I try to remind folks that the whole GPL thing got started when RMS wanted to fix his printer and Xerox said "no" despite having (IIRC) used some of his work to write the printer software he wanted to edit.
Re:Copyright vs. Copyleft (2007) by qsort on Saturday November 07, 2020 @09:10AM (#25015155)
> MIT turns volunteering into unpaid labor for some billionaires.

Um... no? The idea behind MIT/ISC and the like is to let other people use your software, which they aren't automatically allowed to do because copyright is broken by default.

There's a lot of software that I would like to use in my day job that I can't touch because it's GPL. This is by design.

> These companies try hard to push the narrative that MIT is "practical" and GPL is "political" - guess why.

I have no sympathy for FAANG, but that happens to be correct. GPL is explicitly political in its intent.

Re:Copyright vs. Copyleft (2007) by throwaway50203 on Saturday November 07, 2020 @10:33AM (#25015622)
> There's a lot of software that I would like to use in my day job that I can't touch because it's GPL. This is by design.

Good: the license is working as intended.

> I have no sympathy for FAANG, but that happens to be correct. GPL is explicitly political in its intent.

Don't be cheeky. The sentence was [ push the narrative that MIT is "practical" and GPL is "political" ]

The MIT is equally political - just siding with the freeloaders.

Re:Copyright vs. Copyleft (2007) by dnautics on Saturday November 07, 2020 @12:30PM (#25016570)
For some people the fundamental problem with the GPL is that it is entirely dependent on the political structure that they believe to be flawed. If you are for copyright abolishment, using the GPL is cynical at best, hypocritical at worst.
Re:Copyright vs. Copyleft (2007) by throwaway50203 on Saturday November 07, 2020 @04:53PM (#25019891)
> GPL is cynical at best, hypocritical at worst

It's not different from soldiers taking weapons from the enemy they are fighting. A pretty common tactic.

Fighting fire with fire. Where's the hypocrisy?

Re:Copyright vs. Copyleft (2007) by dnautics on Saturday November 07, 2020 @05:10PM (#25020055)
Sure, but in war there is at least an exit plan (a way for eventually not having to kill anymore), even if it's shitty and ill-planned. If you are in software freedom for the purposes of abolition and you pick the GPL, you are allying yourself with people who NEVER want to give up copyright, because it lets them "exert control" over the end user, e.g. corporations, so your ally has a very strong real vested interest against what you take as a desired end goal.

What does the endgame look like for an abolitionist?

Re:Copyright vs. Copyleft (2007) by 2Gkashmiri on Saturday November 07, 2020 @12:53PM (#25016813)
One quick question. GPL forces downstream users to disclose their source code and changes. Does it also force them to push those changes or improvements upstream or not ? As in, I make an improvement to a software and I am selling and also giving source code but am I supposed to push my changes back up or not?
Re:Copyright vs. Copyleft (2007) by codeguro2 on Saturday November 07, 2020 @01:10PM (#25017006)
The restrictions of the GPL only kick in when you distribute your binaries. You have the freedom to run and modify the source as you wish. The only rule is, "The source code travels with the binaries" - meaning /if/ you choose to distribute it, and you may choose who you distribute it to, that those who receive the binaries must also receive the source code and can take full advantage of the GPL just as you have.
Re:Copyright vs. Copyleft (2007) by a1369209993 on Saturday November 07, 2020 @01:13PM (#25017029)
It specifically doesn't require that for logistical reasons. See, eg, the "desert island test" from DFSG. If you aren't able to contact upstream to send them your changes, such a requirement would effective forbid you from making changes to the software.
Re:Copyright vs. Copyleft (2007) by amw on Saturday November 07, 2020 @09:52AM (#25015371)
MIT ends up just as political, it just does so by assuming society's default politics. It "just so happens" those default politics are great for billionaires.
Re:Copyright vs. Copyleft (2007) by crankyoldcrank on Saturday November 07, 2020 @11:29AM (#25015993)
Ugh, they're also great for anyone that wants to feed themselves with their software, whether self employed or not.

God forbid people use a license that makes it easier to turn a profit so they don't have to beg to stay afloat.

Re:Copyright vs. Copyleft (2007) by wizzwizz4 on Saturday November 07, 2020 @11:51AM (#25016203)
MIT actually makes it harder for people to profit from their software than GPL, because the developer of GPL-licensed code has the exclusive right (by law, as author) to produce proprietary forks of that code; if the code's MIT'd, somebody else could fork, clone the proprietary features and add a few more (preferably going against the original program's general philosophy in doing so, to reduce the chances of those features being introduced into the original), aggressively market, and basically steal the whole project and its user base… then the developer's unemployed, the whole thing's proprietary and some unethical organisation is profiting off the work of another.

The “rolling release” model, where the latest version's proprietary but six months ago's version is libre, simply cannot be done with something like MIT unless you're willing to risk somebody else taking it all for themselves.

Re:Copyright vs. Copyleft (2007) by dnautics on Saturday November 07, 2020 @12:32PM (#25016589)
> MIT actually makes it harder for people to profit from their software than GPL, because the developer of GPL-licensed code has the exclusive right

Can you name an IC that profits from their software with the GPL?

By contrast I know of a very well-known IC that profits (handsomely) from their software with an even looser license than the MIT - SQLite.

Re:Copyright vs. Copyleft (2007) by cercatrova on Saturday November 07, 2020 @12:45PM (#25016734)
MongoDB, Sentry, Plausible Analytics et al. use GPL, AGPL or even stronger proprietary versions such as SSPL to prevent cloud vendors from using their products. Now imagine they used MIT instead, cloud vendors could rip them off without any contributions back.

This is exactly what happened even when they used AGPL, something that was thought to scare cloud vendors, but instead it wasn't scary enough, so these companies had to invent new proprietary licenses.

Re:Copyright vs. Copyleft (2007) by dnautics on Saturday November 07, 2020 @01:00PM (#25016886)
I was under the impression that the implication of the parent comment was IC in the literally "individual" coder sense. If you're going to be that broad there are PLENTY of well known frameworks, not even worth listing, under both MIT and GPL, that are built by organizations, or VC-backed startups, and it's hard to compare "ease of making money".
Re:Copyright vs. Copyleft (2007) by cercatrova on Saturday November 07, 2020 @02:01PM (#25017595)
Perhaps, but each of these organizations were started by a single person and then grew. Plausible is only 2 people if I recall correctly. So I'm not sure counting purely individuals makes sense. Sqlite even isn't one person, multiple people make pull requests.
Re:Copyright vs. Copyleft (2007) by wizzwizz4 on Saturday November 07, 2020 @06:30PM (#25020874)
> Now imagine they used MIT instead, cloud vendors could rip them off without any contributions back.

Plausible used to be MIT, and exactly this happened to them.

Re:Copyright vs. Copyleft (2007) by cercatrova on Saturday November 07, 2020 @06:51PM (#25021070)
Yep, that's why I mentioned them specifically. It's happened to a lot of companies too.
Re:Copyright vs. Copyleft (2007) by wizzwizz4 on Saturday November 07, 2020 @09:56AM (#25015391)
> There's a lot of software that I would like to use in my day job that I can't touch because it's GPL.

But my day job's fine with me using that software. Why? It's not using the law to restrict people's ability to use their computers when that software is installed.

Re:Copyright vs. Copyleft (2007) by rhamzeh on Saturday November 07, 2020 @07:09AM (#25014624)
I believe copyleft stands for and invisions a better world where all code is free/libre and available to everyone. And the GPL family of licenses is trying to get us there.

MIT and the like, while being good open source licences, allow anyone to break the chain and not release their code to the public. So it is good in terms of being open source and free/libre now, but does do anything for the future, and does not do enough to bring about the vision of a fully free world.

Personally, I'd prefer the GPL licenses unless there's an good reason not to.

Re:Copyright vs. Copyleft (2007) by mimixco on Saturday November 07, 2020 @09:28AM (#25015236)
The good reason is that GPL's requirement that I make my source code and build instructions available to my licensed customers (paid customers only, btw, if I want) doesn't actually help the original developer at all. Is he or she supposed to dig into my doc and diff my changes?

The idea that there is some wonderful "community" on GitHub and all this code just flows back into a beautiful, better place simply isn't how programming works. No one would do that.

Re:Copyright vs. Copyleft (2007) by kubanczyk on Saturday November 07, 2020 @12:02PM (#25016295)
Who cares about GitHub? Your paid user can take the code and go to the original dev (or any other) and become their paying customer, if they need more work done.

Therefore GPL helps both users and devs.

Re:Copyright vs. Copyleft (2007) by zelphirkalt on Saturday November 07, 2020 @08:42AM (#25015007)
> I think that's the fundamental reason open source licenses such as BSD and MIT have caught on - they centre on the need of the developer to get productive work done, not on the far more abstract principle of the home PC user being able to recompile their own software stack from source.

That is reducing what GPL is about quite a lot.

For example it is equally important, if not more, that modifications in most cases have to be contributed back to the community, which means getting companies to take part in the action, instead of simply using work of others, profitting from it and never contributing anything back.

Re:Copyright vs. Copyleft (2007) by xyzzy_plugh on Saturday November 07, 2020 @08:47AM (#25015030)
> For example it is equally important, if not more, that modifications in most cases have to be contributed back to the community, which means getting companies to take part in the action, instead of simply using work of others, profitting from it and never contributing anything back.

This is wrong. There is no requirement to contribute back to the community, just the requirement that changes (or rather, the source with your changes) be made available to your users. This means they could mail CDs of their code to their paying customers only, if they so choose. A far cry from "contributing back to the community", closer to something like "a pain in the ass."

Re:Copyright vs. Copyleft (2007) by tsimionescu on Saturday November 07, 2020 @10:56AM (#25015751)
That is a distinction without a difference, mostly - since those paying customers are free to then publish the source code they got from you for free for everyone.

The theoretical possibility of charging money for distributing GPL software has not materialized for any company. You can get RHEL for free if you want, for example, and build sell your own devices with it.

Re:Copyright vs. Copyleft (2007) by njarboe on Saturday November 07, 2020 @11:35AM (#25016038)
You can't charge money for distributing GPL software because with high speed internet that is very cheap and easy to do. Competition will and has brought that cost to about zero. And that is a good thing. Everyone now has free access to a huge amount software with source code.
Re:Copyright vs. Copyleft (2007) by tsimionescu on Saturday November 07, 2020 @02:09PM (#25017723)
So how can a software company make money, in an ideal world where all code is free?
Re:Copyright vs. Copyleft (2007) by njarboe on Monday November 09, 2020 @06:12PM (#25041118)
In software support, training, and adding/fixing bugs for a fee. Redhat was a large company that did this.

If the world stabilized on a few software products that did what people wanted to do, like and office suite, that would be great. No more work needs to be done on it. Just a little maintenance going forward. Like roads. They cost a lot to build, but little to allow someone to drive on them.

Re:Copyright vs. Copyleft (2007) by dec0dedab0de on Saturday November 07, 2020 @09:38AM (#25015292)
And really that's a beautiful thing. If I'm going to rely on your software. I want a way to keep supporting myself if you go out of business or you deem my suggestions unworthy.
Re:Copyright vs. Copyleft (2007) by mimixco on Saturday November 07, 2020 @09:54AM (#25015380)
Surely. We can have both. Red Hat, for example, gives you the source after you pay for a license. This is how it was at IBM years ago in the mainframe world.
Re:Copyright vs. Copyleft (2007) by codeguro2 on Saturday November 07, 2020 @01:16PM (#25017053)
This is precisely why I love the GPL.
Re:Copyright vs. Copyleft (2007) by mimixco on Saturday November 07, 2020 @09:26AM (#25015228)
Exactly. I don't know where the phrase "contribute to the community" came from but it's not in the GPL license text.

All you have to do to comply is make your own source code available on request to users who accept your license, along with installation instructions to build the running product. That's not contributing anything to the other dev's community.

Re:Copyright vs. Copyleft (2007) by zelphirkalt on Saturday November 07, 2020 @09:40AM (#25015301)
As far as I know, when you make modifications, you need to release the modified source code together with the product. That means, that you can not keep it a secret, that only you know, unless no one ever buys your product.

I am not so sure about what you say about releasing it to only paying customers. That might be true. In that case one of the original developers could buy 1 license or the community could pay for 1 license and this way get the source code. Then the developers of the modification would get some pay and the original developers would get the source code.

Re:Copyright vs. Copyleft (2007) by est31 on Saturday November 07, 2020 @10:16AM (#25015513)
The GPL gives you multiple options to comply with it. Roughly summarizing, either you put the source code onto the same medium that contains the object code, which is what xyzzy_plugh is alluding to, or you can put it onto a web server and accompany the object form with a written offer that it's on that web server. See section "6 Conveying Non-Source Forms" of the GPL.

The GPL only requires you to make the source code accessible to those people who also get the binary from you, not everyone, but most entities just allow downloads for anybody. It's more expensive to implement checking than it's to just allow downloads for everyone. xyzzy_plugh is splitting hairs here.

Re:Copyright vs. Copyleft (2007) by xyzzy_plugh on Saturday November 07, 2020 @12:42PM (#25016702)
I'm really not splitting hairs.

"Contributing back to the community" sorta implies you're opening a PR, following coding guidelines, writing tests even perhaps. What happens in practice is corps just hack everything together and rush stuff out the door -- no communities want those contributions. It's rare that these sort of releases contain anything novel or useful. Take a look at the OSS releases for Amazon's products (Echo, FireTV) and be prepared to be underwhelmed.

Re:Copyright vs. Copyleft (2007) by mimixco on Tuesday November 10, 2020 @11:38AM (#25047875)
Exactly this. Most of the software others will build with GPL'd stuff isn't interesting to the owner of the original code. They're not doing it to fix bugs. They're doing it to add stuff for their own products. No community of the original software's devs is going to want the output of everyone else's surrounding code or customizations.
Re:Copyright vs. Copyleft (2007) by codeguro2 on Saturday November 07, 2020 @01:14PM (#25017036)
There is nothing preventing those users to publish that exact thing for the world to see. The GPL ensures that they can absolutely do that, so your point is moot.
Re:Copyright vs. Copyleft (2007) by asimovfan on Saturday November 07, 2020 @08:45AM (#25015024)
You are comparing GPL to a product as if it should aim to reach some sort of market penetration.

GPL is not necessarily for developers to get productive work done. It is for people to ensure maximum benevolence with their work for everyone and take the highest moral position. I believe what needs market penetration is this ideal, rather than the GPL itself. GPL is for people who already hold this kind of ideal. They are looking for exactly this.

I don't say you shouldn't ever make money from your work or never use any copyright/MIT/BSD licenses. Most people are not filthy rich and need the money. What I am saying is GPL is not for this, and does not have the requirement to be convenient or framed in a different way than the heroic selfless endeavor it is, in any sense.

Re:Copyright vs. Copyleft (2007) by codeguro2 on Saturday November 07, 2020 @01:19PM (#25017068)
> GPL is not necessarily for developers to get productive work done.

Try getting some productive work done without the source. Like fixing a printer of a proprietary driver, for instance. No, the GPL is about exactly about getting practical work done. That's why it emphasizes so much on the 4 essential freedoms, and why 3 of those 4 freedoms are essentially the same thing "the freedom to tinker with the source code and share that information with other developers who can tinker with it some more and do the same".

Re:Copyright vs. Copyleft (2007) by theobeers on Saturday November 07, 2020 @07:53AM (#25014792)
IMO it makes more sense to look at the rising popularity of a license like MIT, as opposed to the GPL, in terms of the acceptability of each license to different groups of individuals and institutions.

What is the range of opinion regarding the MIT license? From what I’ve seen, people are either fine with it, or mildly disgruntled. Exceptions are rare. And of course, corporations love having access to software libraries under this license.

How about the GPL? Individual developers seem to be either ok with it, or enthusiastically in support. That’s cool—I’m sure we can all relate to those feelings. But a lot of, ahem, for-profit institutions simply will not get involved in GPL-licensed software. We’ve seen repeatedly the effects of their willingness to walk away, to invest in alternatives, etc.

It seems obvious, if depressing, how things will move over time.

Re:Copyright vs. Copyleft (2007) by zelphirkalt on Saturday November 07, 2020 @08:51AM (#25015066)
But then again it is also obvious that greedy people will have more emotions involved when it comes to something that forces them to contribute back, so no surprise there.

I think this is painting the picture in a too one-sided way. Here is another way to see it: While for-profits might develop their own alternatives, they will fail to make those GPL licensed in most cases, because that is what they wanted to avoid: Giving back to the society, that allows them to exist. So they will have proprietary code. The next company will do the same and so on, all while slowly the GPL licensed alternative creeps up on them, until finally it has caught up. It gets ever more expensive to not use GPL software, as free software slowly gains ground.

Re:Copyright vs. Copyleft (2007) by indymike on Saturday November 07, 2020 @12:37PM (#25016638)
Plenty of for-profits use, support and contribute to GPL'd software. I suspect that those who will not are a smaller set than companies who prefer not to.
Re:Copyright vs. Copyleft (2007) by bergstromm466 on Saturday November 07, 2020 @08:50AM (#25015054)
> the intent of the law is genuinely to guarantee access to the fruits of one's intellectual labour

This seems a naive take when considering that it's Corporations who hold the most Intellectual Property[1] (Patents and Copyrights) and are the 'customers' or beneficiaries of Intellectual Property laws and systems.

It's Corporations who focus on IP acquisition (and thus monopolization) strategies (e.g. Google buying smaller startups to add their Intellectual Property to it's repertoire).

...in other words, the likelyhood of average Joe being helped by the Intellectual Property system to get access to the fruits of his labor is not a common situation at all. Most new innovations are the result of access and engagement with existing Corporate Intellectual Property (plus an expensive education).

[1] https://www.gnu.org/philosophy/not-ipr.en.html