I Changed My License

jjllyhill about 2 hours ago 78 commentsRead Article on bergie.iki.fi

⚡ Community Insights

Discussion Sentiment

68% Positive

Analyzed from 3356 words in the discussion.

Discussion (78 Comments)Read Original on HackerNews

apt-get•about 1 hour ago

Worth noting that the "escape hatch" clauses in the EUPL that allow converting it into other licenses mean it's only ever as strong as the weakest license it names for such an operation, AKA EPL/MPL/LGPL.

Any actor that wants to mess around with providing a closed extension on a network service can exercise that option with an EUPL codebase, so if you care about that, you're better off explicitly naming the AGPL or whatnot.

EUPL is built for government agencies first, and most of the focus is ensuring that nobody has to worry about mix-and-matching it with other copyleft licenses, plus legal language that covers and harmonizes variations in notions of copyright/patents/intellectual property across EU countries, not so much waging war against hyperscalers. (But it's still great to have around!)

dotancohen•about 2 hours ago

This article would do better if it simply enumerated the problems with the LGPL and addressed how this new license which I've never heard of addresses those problems. This hinting and alluding might make great SEO, but that's fit for neither the audience of people producing software, nor for HN.

KronisLV•about 2 hours ago

Here's the license text if someone wants to do the work: https://spdx.org/licenses/EUPL-1.2.html#licenseText

LoganDark•about 1 hour ago

This is the actual license text, in English: https://interoperable-europe.ec.europa.eu/sites/default/file...

Other languages can be found here: https://interoperable-europe.ec.europa.eu/collection/eupl/eu...

LoganDark•about 1 hour ago

The article seems pretty clear that the LGPL is too weak compared to the EUPL for this author, and one of the main concerns is the "SaaS loophole" which I assume would be addressed by the AGPL but also seems addressed by the EUPL.

brainwad•about 1 hour ago

But the EUPL itself says that derivative works may be distributed under the LGPL instead, as long as those works are derived from both a EUPL and LGPL parent. This seems kinda trivial to abuse and the author should have noticed this clause if that was their main concern.

LoganDark•about 1 hour ago

Huh, that's a pretty massive loophole. Pretty much makes the whole license irrelevant.

mnahkies•about 1 hour ago

What are people's thoughts/experiences about dual licencing?

Eg: is there a clean way to dual license such that hobbyist, and exploratory work (eg: a proof of concept done in a commercial setting) are allowed, but using it in production requires a fee?

If you've done this, has it been successful? Obviously there's been many projects relicense over recent years (terraform, redis, etc) - but it's less clear to me if this is a viable path for new projects starting out, or if it just kills adoption from the beginning.

mihaelm•about 1 hour ago

I think it definitely hurts adoption. No hobbyist or experimenter wants to delve into legalities head first by first having to understand the licensing terms of software, whereas permissive licenses like MIT and Apache 2.0 are easily-understood and familiar.

The solution is probably to be more selective what you're open sourcing if you're planning to build a business. And what you open source, you do it under a permissive license so people don't feel limited should they wish to play around with it.

A more restrictive license might be more apt if you don't really want to open source, but you must for regulatory reasons.

idontneedcoffee•16 minutes ago

"The solution is probably to be more selective what you're open sourcing if you're planning to build a business."

Fully agree, FOSS maintainers are - in the grand economic scheme of things - beggars high on altruism. The whole model of FOSS from the position of a non-corporate sponsored developer was already broken and with the advent of AI is now most probably broken beyond-repair. Buy-me-a-coffee with a <0.01% hit rate compared to open feature requests/gh issues on some of the more popular projects out there, all while companies like atlassian - using FOSS to run their business on for free - can charge 50k EUR for a single 1h migration call. Time is the most valuable resource one can waste, something you get to realize once all the mental gymnastics wear off(either by itself or due to less fortunate life situations)

Brian_K_White•about 1 hour ago

Excuse me but as both a hobbyist and commercial software developer I say that the gpl (any version) is quite simple enough. There is no need to go all the way to bsd/mit just to get safety and clarity and freedom from encumberance.

The only people who avoid gpl and talk about mit as being the only safe option, are exactly the people no one should care about. They are the people for whom free isn't free enough, and they must steal even when it's already free.

That is not "adoption" anyone needs to care about.

throawayonthe•37 minutes ago

right but the GPL explicitly allows commercial use, which isn't what the original comment was about ("use in production requires a fee"); i agree with the previous comment that such a license is hard to assess for a hobbyist, but the GPL is not such a license (hence yes it's simple enough)

bob1029•14 minutes ago

If you are trying to monetize your software, the biggest factor is whether or not your customer trusts you.

MIT and source out on GitHub is the easiest way to build trust. You will find that some people simply "steal" your work in this arrangement, but much like with movie piracy I don't think they ever intended to compensate you or anyone else.

So, we wind up alienating all potential customers because we are so worried about preventing ideological crime.

People will steal your ideas and they will get away with it. The more you react to this in first order terms, the more it will destroy you.

Most money in software is made with support contracts, not the initial sale.

graemep•26 minutes ago

In practice AGPL might achieve that. It does allow commercial use, but a lot of big businesses, especially big tech, will not use it. On the other hand it is a clear, OSI approved, FOSS license.

ricardobeat•about 1 hour ago

No success yet, but I recently found BUSL - used by Terraform: https://en.wikipedia.org/wiki/Business_Source_License

It stops companies from building high-revenue products for free, while not being as scary as AGPL/LGPL from the business perspective, and completely unrestricted for everyone else (despite not being technically an open-source license).

xorcist•15 minutes ago

Once you decide on a non-free license, in the FSF sense, in the DFSG sense, and in the open source sense, does the details of the license matter much? You want as many people to pay as possible, and you do not wish for others to compete with you providing this software.

It's pretty much a standard non-free commercial license, which exact wording will matter only to purchasing department of your customers. It will be inconsequential to the broader open source community. Literally thousands of those exist and the specific wording matters very little.

ricardobeat•9 minutes ago

It doesn’t have to be binary. A license like this allows for 99% of the personal and commercial use that a project will ever see, while giving the author leverage over large corporations - which is the main gripe people have. It is not ideal for libraries or things that would be redistributed, but then you have other options.

mihaelm•about 1 hour ago

You might also be interested in the O'Saasy license (https://osaasy.dev/) which is in the similar vein, but simpler.

HashiCorp switched to BUSL license for their products/tools when they already had substantial market share, and they still faced MPL-licensed forks (Terraform -> OpenTofu, Vault -> OpenBao). It will be interesting to see in a few years if those tools notably cut into their share.

I'm not sure a new tool with a BUSL license will get adoption as easily.

ricardobeat•about 1 hour ago

Looks nice. Two main differences:

- BUSL is OSI-approved and listed in SPDX, so corporate lawyers won't be scared away by it: https://spdx.org/licenses/BUSL-1.1.html

- With BUSL the restriction is revenue-based. You can still create competing products, but would have to pay a licensing fee.

ghaff•about 1 hour ago

The heat around this particular issue has cooled down a bit and I'm not sure anyone is especially happy with the state of affairs. But questions around AI have sucked a lot of the oxygen from the room for now.

addandsubtract•about 1 hour ago

Isn't that what Epic, MiniMax, Z.ai, and others are doing, where a license is free for personal use / low revenue projects, but cost a (steep) fee for commercial use? They don't use dual licenses, but rather a tiered license.

Daegalus•42 minutes ago

https://github.com/daegalus/daegalus/blob/main/licensing-phi...

I created something like this on my github and then i relicensed what i could that was purely mine, and kept other stuff unchanged and only used those licenses as default going forward mostly.

I chose EUPL also for pure AGPL style OSS work. and I plan to use other licenses as needed.

kzrdude•about 1 hour ago

Using EUPL is mostly a way to signal that you want to use a license grounded in EU law, not in US law. That's at least the way I've looked at it.

throawayonthe•31 minutes ago

if the EUPL actually closes the SaaS loophole (first time i'm hearing about it though) in a legally grounded way i can see it being used by people outside the EU who say the AGPL is unenforceable/is actually nonfree/is too hard to actually comply with

pelagicAustral•18 minutes ago

Perfect, I've been looking for a license I can get behind for new projects. I just made a few tweaks https://aeupl.org/

jimnotgym•44 minutes ago

If one licences open source under a strong copyleft licence (say AGPL3) presumably one can open up later and issue under weaker licences (say MIT) if one chooses?

Presumably you can also sell access to it with a full commercial licence if one chooses?

emersion•37 minutes ago

This works as long as you're the only copyright holder. If other developers contribute, weakening the license requires their approval.

fluoridation•11 minutes ago

It's also possible if contributors agree to waive rights to their contributions, thus having multiple contributors and a single rights holder.

BlackRabbit1•about 1 hour ago

For hardware/electronics I also recommend looking at the CERN OHL licenses.

They cover a very specific niche GPL/AGPL/etc. do not cover properly.

1294899•32 minutes ago

The license still allows AI training theft. What is needed is an OSS EULA that forbids IP theft, since the governments are corrupt and still allow it.

The EULA needs a clause that 10% of the market cap of a company will be paid to the IP holder upon violating it.

alturp•about 1 hour ago

> "Over the years it has been clear that we in the “open source” camp (as opposed to the “free software” camp) were wrong all along. We won the debate, and gained little for users or developers. All that our efforts did was to make it easier for big corporations build things more cheaply and for billionaires to become trillionaires."

Claiming this and afterwards deciding to use a weak copy left license like EUPL (which can be integrated with proprietary software without disclosing source code) instead of AGPLv3, which really closes SaaS loop is a bit lost to me.

codemog•about 1 hour ago

Also there’s only one trillionaire and that varies by the stock that day. And it’s not because he abused open source, he’s just the greatest huckster of all time.

jruohonen•about 2 hours ago

CC BY-NC-ND is what I'm also increasingly using (for non-code), though not always, and disheartenedly. (And as commented, the non-code context is different.)

hypfer•about 1 hour ago

ND is usually a bit sad, as it makes the thing a dead-end.

The magic of the web has always been that things would continuously morph through being reinterpreted and all, and that just doesn't happen with ND.

I can of course see the valid reasons why one would pick that license, but it's still.. kinda sad that it's culturally dead.

ghaff•about 1 hour ago

I discussed NC in my other comment. But, yes, ND is arguably counter the whole remix culture that was supposedly part of the impetus for Creative Commons in the first place. I do kind of see the logic behind prohibiting, say, a remix of a video or photo in a way that misrepresents the subject. But I also don't particularly like it.

jruohonen•about 1 hour ago

True enough; philosophically, I am still in the BY camp (a.k.a. BSD/MIT/etc.), and I do not particularly care about the NC part, but ND is increasingly important for non-code. But if they could do even the BY properly, it would be a step to the right direction (and, to some extent, I think they're doing that).

hypfer•about 1 hour ago

Huh. Can you elaborate why you view ND as increasingly important, whereas NC bothers you less?

Because for me, it would be the exact other way round.

ghaff•about 1 hour ago

The problem is that not even Creative Commons was able to come up with a real definition for non-commercial when they last (I think) revised the license. Essentially it means trivial uses (a photo in a grade school assignment) or its contentious in a way that reasonable people can disagree about. What constitutes acceptable usage of a properly attributed photo? Personally, I just properly attribute and stopped worry about whether most presentations constituted commercial use or not.

Joel_Mckay•about 2 hours ago

For FOSS I personally prefer Apache 2.0 license, as 10 years from now I have no idea what people will need for their projects.

Personally, it makes me happy if people can make a business using a bit of my work. Just don't redirect commercial support tickets onto community projects, or get neglected customers to contact authors.

The way I see it... is symbiotic commercial relationships are important, as people can get their time sponsored to work on FOSS code. Also, having community projects form reliable long term infrastructure opens additional opportunity for people to work with FOSS options.

Telling people how they should have fun is always lame... whether it is Sony/Microsoft... or just some disillusioned dude convinced their work won't be obfuscated by an LLM in 30 seconds. =3

broodbucket•about 1 hour ago

>Personally, it makes me happy if people can make a business using a bit of my work

Copyleft doesn't say that they can't, it says they have to make their changes available

Joel_Mckay•23 minutes ago

I am mostly just an anti-contaminating license proponent. Porting to multiple platforms gets complicated if you include a 3rd party commercial library with a project that on linking demands it also become publicly accessible.

For example, if someone wants to do something creative... they shouldn't have to cite 400 different peoples licenses. That isn't sustainable or fun.

I will stick with Apache 2.0, but understand different folks have other use-cases =3

xorcist•4 minutes ago

> it makes me happy if people can make a business using a bit of my work

It's an idea as old as any:

The freedom to restrict the freedom of others, is it really a freedom?

It is a tiresome debate. People can argue about it until the sun sets without reaching an agreement. Better to be clear about which kind of freedom you mean, and respect the choice of others.

Plenty of businesses have been started around free software without necessarily restricting the freedoms of others. It is often argued that this constitutes a better approximation of a truly free market than the entry barriers intellectual property law can put up.

zelphirkalt•28 minutes ago

I think people getting time sponsored working on FOSS is quite rare. Would like to do that myself, but instead I just develop in my free time.

Joel_Mckay•19 minutes ago

You mean you have never written or used FOSS applications at work?

I find that very surprising, but I have seen some shops practice clean room coding policies. =3

ricardobeat•about 1 hour ago

This, for some reason, has become a controversial idea — as evidenced by your comment being downvoted.

I don’t understand what angle people are coming from, when they disregard the community effects of open-source software entirely. If your main goal is to make money, there is absolutely nothing wrong with building a business instead.

Joel_Mckay•31 minutes ago

If people have a rational self-interest in helping build great works, than the projects simply manifest out of necessity. There is zero benefit in assuming everything is a zero-sum game.

With billions of people online someone is always having the best or worst day of their lives. I rather people be honest about what they think, and trust respectful disagreement is welcome. Have a great day =3

LoganDark•about 2 hours ago

I don't like the phrasing of the EUPL because it says you have rights full stop and then in a later section it says there are actually conditions. For that reason I would not immediately be sure the conditions are even enforceable, other than "this was surely made by lawyers and therefore also surely valid".

Aside from that, it is nice to see Communication counted alongside Distribution; this should have been done from the start IMO.

jraph•about 2 hours ago

> I don't like the phrasing of the EUPL because it says you have rights full stop and then in a later section it says there are actually conditions. For that reason I would not immediately be sure the conditions are even enforceable.

Full right to use no conditions ≠ full right on what you can do with the code

LoganDark•about 1 hour ago

> Full right to use no conditions ≠ full right on what you can do with the code

    2. Scope of the rights granted by the Licence
    
    The Licensor hereby grants You a worldwide, royalty-free, non-exclusive,
    sublicensable licence to do the following, for the duration of copyright vested
    in the Original Work:
    
    - use the Work in any circumstance and for all usage,
    - reproduce the Work,
    - modify the Work, and make Derivative Works based upon the Work,
    - communicate to the public, including the right to make available or display
      the Work or copies thereof to the public and perform publicly, as the case may
      be, the Work,
    - distribute the Work or copies thereof,
    - lend and rent the Work or copies thereof,
    - sublicense rights in the Work or copies thereof.
    
    Those rights can be exercised on any media, supports and formats, whether now
    known or later invented, as far as the applicable law permits so.
    
    In the countries where moral rights apply, the Licensor waives his right to
    exercise his moral right to the extent allowed by law in order to make effective
    the licence of the economic rights here above listed.
    
    The Licensor grants to the Licensee royalty-free, non-exclusive usage rights to
    any patents held by the Licensor, to the extent necessary to make use of the
    rights granted on the Work under this Licence.

This is a lot more rights than just to use and there is absolutely nothing about conditions in this entire section.

There's not even a hint of conditions until three sections later where it starts modifying section 2, which feels sloppy to me.

ricardobeat•about 1 hour ago

> We won the debate, and gained little for users or developers. All that our efforts did was to make it easier for big corporations build things more cheaply and for billionaires to become trillionaires.

As a long-time developer and consumer of OSS I have to disagree. Open-source software has had an enormous effect on the world, and that... was kind of the point? When we licensed things as MIT we knew that corporations would use it. We wanted them to use them, adopt them and bring new users into the community. You take some, you give back. There was no expectation of turning your late-afternoons JS framework into a business. And not having access to it would absolutely not have stopped corporate behemoths from getting where they are, but would have killed many small businesses and startups.

That said, I've started licensing some of my code with the BUSL license [1] - unrestricted use, unless you are a large company. The code becomes MIT-licensed automatically after a set window to remove maintainability concerns.

[1] https://en.wikipedia.org/wiki/Business_Source_License

zelphirkalt•19 minutes ago

The complaint here is, that those business are not necessarily "bringing people into the community", unless you are talking about passive users, who do not contribute. The businesses simply use the stuff built at no cost to rake in big money, while the person, who did the actual work does not see a cent. This is different with copyleft licenses like AGPL. Only that many businesses are so afraid of contributing anything at all, that they often don't want to use AGPL or even GPL licensed software.

LtWorf•about 1 hour ago

But why should I work for free so that companies can fire my fellow human beings?

brainwad•about 1 hour ago

The causality is wrong here. You chose to work for free with no reward, and _then_ companies found your work and used it. Presumably you started out working for free because it was intrinsically rewarding (otherwise: stop doing work you hate for free?).

amazingamazing•about 2 hours ago

Do these types of things really matter anymore? If you have tokens, given the source is available pretty easy to reimplement with plausible deniability.

KronisLV•about 1 hour ago

https://malus.sh/ (I think it was intended to be satire/critique)

andxor•about 2 hours ago

It's a quixotic crusade, in perfect European style.

janfoeh•14 minutes ago

Yes, how quixotic of them. They really should have foreseen this when they published the license … checks notes … close to twenty years ago.

lionkor•about 1 hour ago

If you think an LLM can just implement e.g. an alternative to the Linux kernel from scratch (or any other GPL licensed software), you might be falling for the marketing.

Have you seen LLMs build large, stable, pieces of software, that work well, with your own eyes? I have not. I have seen LLMs build small, well-understood things, and I've seen LLMs do super well with extremely well specified problems, but all the rest seems to be marketing (i.e. I couldn't observe or reproduce it).

Edit: I'm not talking about throwaway slop that just needs to run long enough to get funding.

f311a•43 minutes ago

A lot of open source that we used to use as dependencies is trivial. Sometimes you only need 10% of the library. No one is talking about kernel.

Also, changing license does not prevent you from forking the source code before the change. There are no new libraries with kernel level effort that use uncommon license.

amazingamazing•about 1 hour ago

Bun was rewritten for software used by millions.

meindnoch•26 minutes ago

Mechanical translation.

sham1•about 1 hour ago

Then again, it's not like even before the plagiarising slop machines you couldn't just get around licenses if you were dedicated enough to evil and was comfortable lying about the provenance of the code you're using.

Sure, it'd make all the lawyer types nervous for obvious reasons, but that's why you'd also need to be comfortable with the evil deed. But you're correct that the evil plagiarism machine makes it way easier.

Joel_Mckay•about 2 hours ago

As much as I dislike isomorphic plagiarism, your point is very valid...

It is a viable argument, and people shouldn't bury such insights given the estimated $9Tn worth of opensource work that was appropriated. =3

ChocolateGod•about 2 hours ago

I think there's been a mistake in the thinking that restricting the licensing on open source projects will make the companies that use them as a service would make them contribute.

They don't, the companies just replace the software in question.

franciscop•about 1 hour ago

I hate that some people like to put us all in the same bag. Please don't include me. I don't really care if either my neighbor or Elon Musk used my open source code. I publish it as such because it's a present to the world at large that I can do, and I believe everyone will benefit with my code being MIT.

You're free to have different ideals, but it's silly to claim that my ideals are wrong and that finally "you" realized that my ideals are wrong. I don't even want to have a culture wars, just don't include me in yours please.

logifail•about 1 hour ago

> I don't really care if either my neighbor or Elon Musk used my open source code.

I wish we could spend less (collective) time here on HN talking about/worrying about Elon Musk.

We're (allegedly) here for "anything that gratifies one's intellectual curiosity".

What SpaceX and/or Tesla are doing could certainly satisfy that, worrying about Musk himself certainly isn't.

franciscop•42 minutes ago

Agreed; I mentioned Elon because the post made the reference quite explicit by saying "trillionaires", probably given the context Bezos or Gates would've been better examples though.

charcircuit•about 1 hour ago

>All that our efforts did was to make it easier for big corporations build things more cheaply and for billionaires to become trillionaires.

This is not true. Open source is fundamental to how easy users can create software in the LLM era. Users and developers have gained tremendous value. Saying they have gained little is simply false. And it's a good thing to make it possible for big corporations to make things cheaper. It means more efficient resource allocation for society. And for billionaires to turn into trillionaire they have to provide magnitudes more value to society in order to do so. Enabling people to provide trillions of dollars of value to society is a good thing that open source unlocks.

zelphirkalt•17 minutes ago

Rather feels like post LLMs being everywhere, salary levels for developers are dropping left and right. Where did we gain value?

kypro•about 1 hour ago

Also theres not multiple trillionaires in the world, and the one trillionaire we have did that largely by innovating and creating new stuff rather than just leveraging existing OSS for profit...