News for hackers. Stuff that matters.
Re:CockroachDB License Change by haolez on Thursday August 15, 2024 @12:13PM (#41257639)
Old(?) school open source with GPL licenses doesn't seem to suffer from this, on a first glance. Maybe Stallman was right. Would love to hear from someone more knowledgeable on this. I'm not trying to troll.
Re:CockroachDB License Change by ghshephard on Thursday August 15, 2024 @01:06PM (#41258174)
GPL is actually a great license for this scenario. The software advances to a particular level of development, inertia, market penetration - then the company that owns the software dual licenses with GPLv3 - which no company can risk to have on their premise, distribute, or use/touch, etc... - ergo you then have to pay for a commercial license to avoid the GPLv3 taint.
Re:CockroachDB License Change by graemep on Thursday August 15, 2024 @04:05PM (#41259833)
Why can companies not use GPL3 software? I cannot see how its so different from GPL 2 for companies that are users.

I can see it has some disadvantages for companies incorporating GPL software in their products, but none for companies merely using GPL 3 software.

Re:CockroachDB License Change by ghshephard on Thursday August 15, 2024 @04:27PM (#41260014)
I can't say for certain why they can't use GPLv3 - just that no company I've ever worked for (n=4 since GPLv3 came out) - will allow it on premise. It's probably why Apple stopped updating all their GNU binaries, and you have to sideload stuff with brew to use anything released in the last 10 years.

If I had to guess - The patent rights clause weirds out a lot of lawyers. Obviously anyone who works with hardware doesn't like the anti-tivoization clause. Another possibility is the AGPL (which IS lethal for obvious reasons) is often conflated with GPLv3.

All I know is GPLv2 is fine, GPLv3 is usually not, and AGPL is never possible in corporations that I've worked for.

Re:CockroachDB License Change by trws on Thursday August 15, 2024 @06:06PM (#41260937)
A small refinement here, your statements are largely my experience dealing with people linking against gpl3 software because of the vitality and the patent exemptions. Most places run gpl3 stuff just fine. The one organizations won’t touch with a ten foot pole, even to run it, is AGPL.
Re:CockroachDB License Change by graemep on Friday August 16, 2024 @03:47AM (#41264115)
> A small refinement here, your statements are largely my experience dealing with people linking against gpl3 software because of the vitality and the patent exemptions

In the context of the thread (the claim GPL 3 provides more of a motive for people to by paid licences for dual licensed software) I think that "small refinement" covers most of what we are talking about though.

Re:CockroachDB License Change by worik on Friday August 16, 2024 @03:52AM (#41264150)
> won’t touch with a ten foot pole, even to run it, is AGPL.

I feel out of touch

Why?>

Re:CockroachDB License Change by swiftcoder on Friday August 16, 2024 @04:37AM (#41264449)
The AGPL has a significantly stronger viral clause than the plain GPL. You must offer the source code to anyone who connects to the AGPL-covered code via a network connection (i.e. must open source the entire server if it is using any AGPL code)
Re:CockroachDB License Change by orthoxerox on Friday August 16, 2024 @09:43AM (#41266366)
Releasing the whole server sounds more like the Commons Clause or the SSPL. AGPL requires you only to provide the source code of your fork to its users.
Re:CockroachDB License Change by swiftcoder on Friday August 16, 2024 @04:47PM (#41270234)
> AGPL requires you only to provide the source code of your fork to its users

The AGPLv3 is exactly the same as the GPLv3, except with the added clause that connecting to a server counts as distribution for the purposes of triggering the right to obtain source code.

That means all the usual GPL copyleft rules apply: if you include an AGPL library in your server binary, the entire binary becomes subject to the AGPL. And being subject to the AGPL, you are obligated to provide access to the source code for your entire server binary to anyone who connects to and interacts with your service across a network.

Quoting from https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-t... :

> Simply put, the AGPLv3 is effectively the GPLv3, but with an additional licensing term that ensures that users who interact over a network with modified versions of the program can receive the source code for that program...

> These terms cover the distribution of verbatim or modified source code as well as compiled executable binaries. However, they only apply when a program is distributed, or more specifically, conveyed to a recipient...

> The AGPLv3 does not adjust or expand the definition of conveying. Instead, it includes an additional right that if the program is expressly designed to accept user requests and send responses over a network, the user is entitled to receive the source code of the version being used.

Re:CockroachDB License Change by orthoxerox on Friday August 16, 2024 @05:38PM (#41270614)
Yes, but are there any AGPL-licensed libraries? I've only seen runnable binaries licensed under AGPL. I can theoretically imagine one, "if you want to build a server application using my binary, I don't want you hiding my source code from your users", but even GPL-licensed libraries are rare, LGPL is more common.
Re:CockroachDB License Change by swiftcoder on Saturday August 17, 2024 @05:26AM (#41273045)
Not a whole lot, at any rate. The poster child was probably BerkleyDB, but the current version is vended from a fork which still uses the pre-AGPL license terms
Re:CockroachDB License Change by worik on Sunday August 18, 2024 @03:25PM (#41284718)
> Not a whole lot, at any rate. The poster child was probably BerkleyDB, but the current version is vended from a fork which still uses the pre-AGPL license terms

It is "dual licensed". AGPL and proprietary license according to Wikipedia

I am unsure how that works...

Oracle

Re:CockroachDB License Change by aftbit on Friday August 16, 2024 @09:52PM (#41271780)
Ah but what if you bundle both your application binary and some (unmodified) AGPL software into a single Docker container? Do you then need to provide source code for your entire application?
Re:CockroachDB License Change by swiftcoder on Saturday August 17, 2024 @04:45PM (#41277822)
That's the kind of question that only really gets answered when a judge rules on it. The pertinent question here is roughly whether the combined docker image constitutes a "derived work" of the AGPL software
Re:CockroachDB License Change by camgunz on Sunday August 18, 2024 @05:41AM (#41281285)
This was probably true of v2, but v3 doesn't refer to derived works. In OP's scenario they didn't modify the AGPL code, so there's nothing to release.
Re:CockroachDB License Change by swiftcoder on Sunday August 18, 2024 @05:23PM (#41285619)
The FSF has substituted the phrase “modified works” in place of “derivative works” in v3 of the license, yes, but not to narrow the definition - the intent was to broaden the definition to cover additional classes of modification.

From the FSF’s licensing FAQ:

> Where's the line between two separate programs, and one program with two parts? This is a legal question, which ultimately judges will decide. We believe that a proper criterion depends both on the mechanism of communication (exec, pipes, rpc, function calls within a shared address space, etc.) and the semantics of the communication (what kinds of information are interchanged).

Re:CockroachDB License Change by camgunz on Monday August 19, 2024 @04:14AM (#41288949)
> The FSF has substituted the phrase “modified works” in place of “derivative works” in v3 of the license, yes, but not to narrow the definition - the intent was to broaden the definition to cover additional classes of modification.

Eben Moglen wrote a little about the intent here [0], I'll excerpt a little:

"This form of explanation was unfortunately unhelpful. It led to years of fruitless discussion about the role of “derivative works” doctrine (a US concept) in software (where US courts have largely failed to provide any guidance). So in GPLv3, we and our clients at the Free Software Foundation decided to drop all illustrative reference to US “derivative works,” returning to the base concept only: GPL covers the licensed work and all works based on the work, where “based on the work” is defined as any modification or combination with the licensed work that requires copyright permission to make."

I don't know if that broadens or narrows, but I think that's the point: case law on "derivative works" was pretty vague (I'm unfamiliar but I'll take Moglen's word). But, to me it sounds like an effort to be more concrete rather than an effort to broaden the conditions under which you have release obligations.

> From the FSF’s licensing FAQ: ...

A couple things.

First, this FAQ entry is about aggregation; the paragraph above what you quoted is this:

"An “aggregate” consists of a number of separate programs, distributed together on the same CD-ROM or other media. The GPL permits you to create and distribute an aggregate, even when the licenses of the other software are nonfree or GPL-incompatible. The only condition is that you cannot release the aggregate under a license that prohibits users from exercising rights that each program's individual license would grant them."

This isn't some kind of "I run a Kubernetes cluster" situation, it's a "I ship a Linux distribution on ISOs" situation.

Second, I was in a different GPL thread [1] discussing some similar things, but all contracts, licenses, statutes, and founding documents have ambiguity in them. I listed a couple reasons (authors can't/don't want to exhaustively enumerate every scenario, human language is imprecise) but I realized I omitted a third reason: times change. You generally want whatever you're authoring to last a little while, not only because legal fees are expensive, but also because relicensing isn't always easy (GPLs have clauses in them letting you additionally license them under any later version, I would assume this is why).

And finally, there's a real double standard--or at least cargo culting--when it comes to the GPLs here. Here's some ways other licenses are ambiguous or potentially unbounded in their coverage:

- Apache License version 2: refers to "derivative works", also: "'Object' form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types." (i.e. does minification count?)

- BSL: also refers to notoriously vague "derivative works"

- SSPL: defines propagation partially with the phrase "in some countries other activities as well."

It's true the GPLs are more complex and ambitious than something like the ISC license (the favorite comparison around here, I think) but that license is something like 100 words. It's not comparable.

[0]: https://softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL...

[1]: https://news.ycombinator.com/item?id=41277241

Re:CockroachDB License Change by frant-hartm on Friday August 16, 2024 @05:16AM (#41264651)
I remember that Neo4j Enterprise used to be available under AGPL. They pulled it and now it's available only under a commercial license.

AGPL is not a problem for server-side software if you don't need to modify it. Your application (talking to the server) doesn't become infected by AGPL.

Re:CockroachDB License Change by graemep on Thursday August 15, 2024 @05:55PM (#41260822)
I can see it makes sense for Apple (anti-tivoization is something they do not want).

> I can't say for certain why they can't use GPLv3 - just that no company I've ever worked for (n=4 since GPLv3 came out) - will allow it on premise

So they do not allow the use of things like Bash or GNU coreutils? That seems quite restrictive and difficult.

Re:CockroachDB License Change by swiftcoder on Friday August 16, 2024 @04:38AM (#41264456)
They often use older version of things like Bash and Coreutils, or equivalents from other ecosystems (i.e. Apple ships the BSD versions thereof)
Re:CockroachDB License Change by graemep on Friday August 16, 2024 @08:52AM (#41265948)
So, for example, if they use RHEL version 6 or later they will install it without the default shell?

Apple is different as they produce their own OS. I am asking about non-software companies avoiding GPL3 which would be necessary for (as the comment I responded to earlier in the tread claims) the use of GPL3 providing a motive to pay for licenses for dual licensed software in a way GPL2 does not.

Re:CockroachDB License Change by coldpie on Friday August 16, 2024 @09:41AM (#41266346)
> I can't say for certain why they can't use GPLv3 - just that no company I've ever worked for (n=4 since GPLv3 came out) - will allow it on premise

My limited experience with IP lawyers at big software companies is that they have zero understanding of software licensing and patent law. They just seem to parrot some line they learned in college 10 years ago, even when the plain text of the license or law sitting in front of them proves them wrong. It's honestly baffling how they get these jobs.

Re:CockroachDB License Change by PeterCorless on Friday August 16, 2024 @05:53PM (#41270724)
I used to work for a company that used AGPL. For databases, in particular, it's not as noxious as people make it seem, other than if you are a hyperscalar trying to commercialize someone else's hard work and run them out of business, or a bottom feeding hosted service company also trying to commercialize someone else's hard work and coattail on their success.

Otherwise it works great for end-user adoption.

Re:CockroachDB License Change by omoikane on Thursday August 15, 2024 @01:26PM (#41258390)
Old school open source projects don't seem particularly profitable. The projects themselves might thrive, but that seem to rely on altruistic developers with other sources of income.

Richard Stallman himself doesn't seem to make money from any software he made directly, but from various grants and such, for example:

https://web.archive.org/web/20220123032418/http://tech.mit.e...

I thought he was on the payroll for FSF, but his reportable compensation has been zero from 2002 to 2022 according to:

https://www.fsf.org/about/financial

Re:CockroachDB License Change by wussboy on Thursday August 15, 2024 @02:50PM (#41259191)
> Old school open source projects don't seem particularly profitable.

And is also subject to survivorship bias. For every OSS project that makes it, tens of thousands do not.

Re:CockroachDB License Change by bigiain on Thursday August 15, 2024 @08:52PM (#41262054)
You're kinda saying the same thing there.

As a developer, I don't want to rely on code from a project that "seems particularly profitable", because one day it's 100% certain they're going to start making their profit off me.

I'm _extremely_ wary of any "open source" projects that're VC funded, because the entire VC industry exists to make rich people richer at everybody else's expense, throwing a few bones at a few of the founders and a vanishingly small portion of the startup employees. As soon as they think that can get away with it because they have enough "free" open source users locked, they're gonna turn all the screws to chase the "100x or bust" exit strategy the VCs rely on. At the expense of everybody who foolishly built something on to of that project without an easy way to replace it.

Re:CockroachDB License Change by omoikane on Thursday August 15, 2024 @10:43PM (#41262663)
I am saying that old school projects aren't paying the developers' bills because they aren't profitable. The developers realize this too, there is only so much altruism to go around but you got mouths to feed and rents to pay.

As an alternative to working on a second job to fund their passion, we are seeing developers trying various things to make their one passion job pay, such as licensing tweaks or VC funding. These don't seem to work out very well, I think it's best explained here:

https://apenwarr.ca/log/20211229

   "So it is with free software. You literally cannot pay for it. If you do, it becomes something else."
Re:CockroachDB License Change by haolez on Friday August 16, 2024 @12:45AM (#41263235)
You are correct, but there is also an interesting phenomenon going on here: old school open source projects last longer. They end up being more reliable in the long term. It's kind of weird that the unprofitable option is the stable one.
Re:CockroachDB License Change by immibis on Friday August 16, 2024 @03:29AM (#41264009)
It's almost like capitalism is a destructive force and a poor way to organise a society.
Re:CockroachDB License Change by graemep on Friday August 16, 2024 @05:03AM (#41264570)
Capitalism works fine under certain conditions: free markets, which implies competition.

The problem is that these conditions do not always prevail.

I used to think this was fixable: https://pietersz.co.uk/2009/11/fix-capitalism

I now think it is more complex and we need a mixed economy.

Re:CockroachDB License Change by ath3nd on Friday August 16, 2024 @06:23PM (#41270926)
> Capitalism works fine under certain conditions: free markets, which implies competition. The problem is that these conditions do not always prevail.

Eventually, on the free market there are winners, and these winners form a monopoly. See Nestle, Tyson foods, Apple. The big corps, having cornered the market, then squeeze the hapless users (and the ecosystem, in Apple's case) into exorbitant prices, because there is no competition. You started with your beloved "free market", ended up with a monstrous monopoly. Surprise, this is how any "free market" story ends.

If you want to avoid the trash situations that we are in today, you need to regulate the shit out of companies with antitrust, breaking them down when they become too big, not allowing them to acquire others under certain conditions and forcing them to treat their workers and customers well. This is the opposite of "free markets", and is the only way if you want a stable society.

Re:CockroachDB License Change by satvikpendem on Tuesday August 20, 2024 @04:15AM (#41297948)
Yes, which is also what Milton Friedman said. I am not sure anyone notable in capitalistic thought actually professed full unbridled capitalism.
Re:CockroachDB License Change by chii on Friday August 16, 2024 @05:54AM (#41264859)
> They end up being more reliable in the long term.

you're just seeing survivorship bias.

Plenty of them would've also disappeared, because their core contributor no longer wanted to give out free labour and moved on.

Re:CockroachDB License Change by FireBeyond on Friday August 16, 2024 @12:46PM (#41268027)
> I thought he was on the payroll for FSF, but his reportable compensation has been zero from 2002 to 2022 according to:

He resigned in 2019 following allegations of inappropriate behavior towards women (https://news.ycombinator.com/item?id=20990583).

Re:CockroachDB License Change by lucianbr on Thursday August 15, 2024 @02:39PM (#41259103)
Maybe? Every day it seems clearer that Stallman is right. Mouse subscription? Windows displaying ads in start menu and recording everything you do? How many devices have become useless when the servers shot down, or games became unplayable? How many times books or songs or movies have disappeared from "online collections" after being paid for? "The right to read" seems more and more realistic as time passes.

In my opinion, Stallman has been proven right many times over.

Re:CockroachDB License Change by monero-xmr on Thursday August 15, 2024 @09:23PM (#41262231)
Well what do you expect to maintain the mouse’s cloud servers, if not subscription revenue? The greed here!
Re:CockroachDB License Change by chii on Friday August 16, 2024 @05:51AM (#41264846)
if the server was integral to the running of the service then yes, it makes sense to discontinue it when there's no more profit to be made.

However, increasingly more and more services which could've been an on-premises deployment become SAAS. This includes games (live services they call it). It is _designed_ to end, and designed to not be able to run locally.

Tell me who's the greedy one.

Re:CockroachDB License Change by jokethrowaway on Saturday August 17, 2024 @06:33PM (#41278565)
I don't think it's designed to end, they're just trying to:

- Prevent piracy

- Extract more money per user (subscriptions, repeated purchases in-game)

Look, you can live perfectly fine without all of those services, there are indie games and there are old games and, according to some, they're much better than any online crapware from today.

Make it a point not to buy Free to play online crap, forbid your kids from playing that crap. Absolutely don't give them any money for this crap.

If enough people stop buying the we'll see a shift to the DRM & no hassle approach of indie games. I'd also prefer giving my money to a small team of devs than some corporate ladder who happend to purchase the latest AAA game built by a studio of overworked and underpaid devs.

Re:CockroachDB License Change by linker3000 on Friday August 16, 2024 @11:52AM (#41267471)
1. Create a mouse that needs Cloud services.

2. Need revenue to pay for the Cloud services.

3, Charge mouse users for the Cloud services.

It's the (stupid) circle of life.

Re:CockroachDB License Change by ubedan on Wednesday August 21, 2024 @10:52AM (#41310887)
It's scary to have you say that when logitech recently looked a computer mouse that needs a subscription:

https://arstechnica.com/gadgets/2024/07/logitech-has-an-idea...

Re:CockroachDB License Change by spion on Friday August 16, 2024 @07:26AM (#41265320)
Was he though? If we didn't have GPL perhaps at least our software and data would've still been on our computers instead of a privately owned cloud...
[dead]
Re:CockroachDB License Change by spion on Saturday August 24, 2024 @05:25AM (#41336807)
Not really blaming, more like wondering how things would turn out.

Probably would only delay the move to the cloud a little bit, and perhaps make AI less capable.

Re:CockroachDB License Change by eikenberry on Thursday August 15, 2024 @09:47PM (#41262358)
FSF requires signing of a CLA. A CLA would let them change the license to whatever they want, just like these companies. Some people were not happy with GPL3 yet that didn't stop the FSF from changing the licenses on their software.
Re:CockroachDB License Change by teddyh on Friday August 16, 2024 @10:59AM (#41267010)
The FSF does not require a CLA.
Re:CockroachDB License Change by eikenberry on Friday August 16, 2024 @05:51PM (#41270712)
If they don't that is something new. Do you know when that started (or rather, stopped)?
Re:CockroachDB License Change by Conan_Kudo on Saturday August 17, 2024 @06:24AM (#41273331)
This stopped a long time ago. Many older GNU projects still have them, but newer ones are not required to have them. Some have even made their usage optional.

An example of a project making it optional is GCC itself: https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html

Re:CockroachDB License Change by eikenberry on Thursday August 22, 2024 @08:03PM (#41325263)
That's great news! I've always been a big supporter of the FSF and that they stopped this toxic practice it awesome!
Re:CockroachDB License Change by mschae23 on Saturday August 17, 2024 @01:56PM (#41276467)
They explain that without it, they can't effectively enforce the copyrights on their projects: https://www.gnu.org/licenses/why-assign.html.en

I highly doubt that the FSF, who developed the GPL licenses and values free software above anything else, would change the licensing of their projects like "these companies" do.

Re:CockroachDB License Change by SoftTalker on Thursday August 15, 2024 @10:59PM (#41262740)
What is the GPL-licensed product that is comparable in functionality and scalability to CockroachDB? If there is one, you're free to use it.
Re:CockroachDB License Change by tsimionescu on Friday August 16, 2024 @12:45AM (#41263234)
MongoDB switched from AGPL to their own license when they couldn't compete with others offering their software as SaaS, so I don't think the GPL is any kind of protection from this. It's just that the GPL is less popular than alternatives for this type of business model.
Re:CockroachDB License Change by haolez on Friday August 16, 2024 @01:42PM (#41268564)
That's a very good counter example. Although, I'd imagine, the latest AGPL version will be useful for a long time and any further progress in the code base would also be under AGPL, which would not be under risk of becoming an open core project.
Re:CockroachDB License Change by pjmlp on Friday August 16, 2024 @03:22PM (#41269493)
Which is exactly why we are back into Public Domain/Shareware kind of models, and GPL is an endangered license model, only some old school projects keep it around.

It will be even worse after the GPL developer generation is gone.