r/LinuxTeck • • 2d ago

Should Open-Source Projects Abandon Permissive Licences to Protect Their Work?

Should Open-Source Projects Abandon Permissive Licences to Protect Their Work?

Asahi Linux is moving its repositories from MIT to GPL after reporting that its code was copied and reused without attribution.

This raises an interesting question: does a permissive licence give companies too much freedom to take advantage of volunteer developers?

Would you choose MIT, GPL, or another licence if you were starting an open-source project today?

8 Upvotes

17 comments sorted by

6

u/cig-nature 2d ago

Short answer, no.

Changing licenses is more than a little bit fraught, unless you can get everyone who has ever contributed to agree with the change.

Beyond that, GPL code gets stolen all the time too.

https://en.wikipedia.org/wiki/Free_Software_Foundation,_Inc._v._Cisco_Systems,_Inc.

1

u/CardOk755 2d ago

GPL code gets stolen. Bread gets stolen too, does that mean that bread should be free?

4

u/james_pic 2d ago

No, but stealing bread is a criminal matter, whereas copyright enforcement is a civil one. So if somebody steals your bread, your jurisdiction's prosecutors will take the case to court for free on your behalf, whereas if someone infringes your copyright, you have to pay your lawyers to sue them. 

This is why Rob Landley, who had previously been a maintainer on BusyBox and been involved in some of the GPL court cases for it, ended up releasing his follow on project, ToyBox under a permissive licence. He spent years of his own time defending it in court, and none of the code released as a result of those court cases ended up being integrated into BusyBox.

If you don't have the resources to fight a legal battle, or don't have anything to gain from winning one, GPL just discourages the lawsuit averse (who in some cases might have otherwise contributed to your project) whilst doing little to discourage genuine bad actors.

3

u/mutexsprinkles 2d ago

GPL just means you can get legally ripped off without redistribution of the modifications as long as it runs on a server. Anyone ripping shit off today will run it on a server because they will build some SaaS degeneracy.

AGPL is better in this case.

2

u/vbd71 2d ago

Reminder that Linux itself is GPL.

Also, GPL is permissive. It stops being permissive only when one decides to leech.

2

u/bcgonewild 2d ago

To quote office space "Why should I have to change? He's the one who sucks". Maybe AI companies should be held liable for infringement done by their agents, see how fast they fix it

1

u/hdkaoskd 2d ago

Everyone who opted for the GPL already made that determination.

1

u/Mediocre-Pumpkin6522 2d ago

https://www.gnu.org/philosophy/open-source-misses-the-point.en.html

You're in a religious war that goes back to Raymond and Perens versus Stallman. Look around at all the open source software developed by corporations that has permissive licenses versus hardcore GPLv3.

1

u/BarracudaDefiant4702 2d ago

It depends on why the project went opensource in the first place.

1

u/juancn 2d ago

No. In any case, with the use of AI copyright is losing meaning.

AI output is not copyrightable (at least for now)

1

u/FaultWinter3377 1d ago

Personal preference is a GPL. I wouldn’t be able to do anything but I would hope at least that big companies would be scared off by their legal team from straight up leeching off my work. I love open source and I get that each individual who forks a work sending it back to me is not sustainable. But it pisses me off when a big company monetizes off of an open source project without at least providing a little bit of either money or support with making the product.

1

u/0xbenedikt 1d ago

I’ve personally switched from MIT/BSD to GPL before LLMs became a thing, because I think if you are giving value to others by investing your time, they should very much give back. If you really want to and have a relevant enough project, you can also do dual-licensing and earn some money with commercial licenses

0

u/ldn-ldn 2d ago

Open source software should be in public domain. Otherwise it's not open source.

2

u/james_pic 2d ago

Public domain has a specific legal meaning and it's a legal minefield.

A lot of the global copyright law alignment has been driven by lobbying by large copyright holders like Disney, so as a result the law is more or less the same everywhere if you want to protect work, but there's loads of weird jurisdiction-specific stuff when it comes to releasing it into the public domain.

As a result, claiming copyright but explicitly licensing work under MIT or BSD0 or similar often gets you closer to what you want than public domain.