News for hackers. Stuff that matters.
Re:CockroachDB License Change by andrewmutz on Thursday August 15, 2024 @10:48AM (#41256788)
It seems that whenever an open source project is run by a VC-backed company, it sooner or later ends up like this. Increasingly it seems that "open source" is just the teaser to get people interested and then when investors want revenue growth, the rug gets pulled.

IMO, it's not really open source if its run by a company that will eventually use its position to squeeze its users for cash.

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.

Re:CockroachDB License Change by candiddevmike on Thursday August 15, 2024 @10:50AM (#41256813)
Like other folks have said, anytime you see a CLA, you see the true intentions of the project. A project that will always be FOSS won't have a need for a CLA.
Re:CockroachDB License Change by _benedict on Thursday August 15, 2024 @11:08AM (#41256979)
The ASF requires a CLA for all regular contributors or large contributions, so I don’t think this is a particularly good barometer.
Re:CockroachDB License Change by remram on Thursday August 15, 2024 @11:36AM (#41257283)
That's a good point. The ASF's FAQ [1] states that "All software developed by all projects of The Apache Software Foundation is freely available without charge" and that it "is specified in the Foundation's Articles of Incorporation [2]", however I see no such specification in the linked incorporation. Is there some actual legal guarantee there?

[1]: https://www.apache.org/foundation/license-faq.html#IsItFree

[2]: https://www.apache.org/foundation/records/incorporator.html

Re:CockroachDB License Change by fweimer on Thursday August 15, 2024 @11:41AM (#41257336)
I think it's mentioned in this document: https://www.apache.org/foundation/records/certificate.html
Re:CockroachDB License Change by remram on Thursday August 15, 2024 @12:05PM (#41257556)
Thanks!

It seems a little short of the claim in their FAQ though, but it's something:

> The purpose of the Corporation is to engage in any lawful act or activity [...] including the creation and maintenance of "open source" software distributed by the Corporation to the public at no charge

Re:CockroachDB License Change by ted_dunning on Thursday August 15, 2024 @12:24PM (#41257756)
I don't think that falls short.

The reason for the "any lawful act" language is to allow the ASF to do things like run a conference, accept donations, sell t-shirts and other activities. If the statement was only "develop open-source software" there are all kinds of important activities that support open source development that would be impossible.

The fact is, however, that certificates can be changed by the people who can vote. IN the case of the ASF, the members are the ones who vote. Getting those ~800 members to radically trash the traditional goal of the foundation is not going to be possible as long as the current membership is active.

Re:CockroachDB License Change by remram on Thursday August 15, 2024 @03:27PM (#41259486)
What I mean is that, if they made some software non-free alongside some free ones (to make money to finance the free ones, for example), that still seems valid as to the current certificate of incorporation.

Their FAQ says "all software free no exception" and this document says something weaker.

Re:CockroachDB License Change by immibis on Friday August 16, 2024 @03:33AM (#41264031)
Look up who is the foundation's secretary and their Mastodon page (their new one, not infosec.exchange) and look for any post about Israel or Gaza. I'm not sure what power a secretary has, but this is concerning.
Re:CockroachDB License Change by remram on Friday August 16, 2024 @04:50PM (#41270276)
If you're trying to say something, say it, and point to proof. I don't know where to even find what you are trying about.
Re:CockroachDB License Change by saurik on Thursday August 15, 2024 @11:36AM (#41257296)
The difference with the ASF/FSF is that they are non-profits with a mission statement (and, if we don't trust that enough--due to OpenAI, as I don't entirely understand what happened there--with clearly-mission-aligned board leadership) that prevent them from pulling the rug out from under their license. (...and, right as I pushed this comment, I see that someone else looked into it, and maybe the ASF fails to have such a clause anywhere ;P but hopefully it is there and just a bit hidden.)
Re:CockroachDB License Change by cortesoft on Thursday August 15, 2024 @11:54AM (#41257445)
Sure, but that contradicts the statement made in the comment they are replying to:

> anytime you see a CLA, you see the true intentions of the project. A project that will always be FOSS won't have a need for a CLA.

If there are conditions to the statement, it isn't "anytime you see a CLA".

Re:CockroachDB License Change by saurik on Thursday August 15, 2024 @12:14PM (#41257642)
Sure, but now we would need to find another epicycle for why giving a for-profit corporation this dangerous power over its licensees is safe/benign. There is, at times, some logic to "the exception that proves the rule".
Re:CockroachDB License Change by ziddoap on Thursday August 15, 2024 @12:21PM (#41257730)
For those of us not in-the-know about licensing acronyms.

CLA = Contributor License Agreement

Re:CockroachDB License Change by fweimer on Thursday August 15, 2024 @11:47AM (#41257394)
It depends on the CLA. In some countries, you cannot not have a CLA because there's always an implied contract.

Many CLAs are just a hassle (basically, DCO that has to be reviewed by the legal department). But a lot are asymmetrical in a substantial way and the original developer gets to play by different rules than the rest. CLAs in the second category tend to be problematic.

Even that is not a completely clear indicator because in some cases, the asymmetry is only intended to help with potential future relicensing in alignment with the project's goals, and not to enable commercialization (either today or at some point in the future). Some organizations have resisted direct commercialization of the code they have been entrusted with for decades, so that can happen even with an asymmetrical CLA.

Re:CockroachDB License Change by kodablah on Thursday August 15, 2024 @12:54PM (#41258051)
This is not necessarily true. Sometimes it's needed to pivot to a better/different open source license without going through the pain of contacting every contributor ever. I have seen that pain in some projects that want to go from LGPL to MIT or something.

For many contributors, they're ok giving full ownership of their contributions to a project owner on the owner's terms. Some contributors may not be ok with that of course, but it doesn't mean that every project owner has nefarious plans with said code ownership.

Re:CockroachDB License Change by drdaeman on Thursday August 15, 2024 @01:35PM (#41258486)
> better/different open source license

And that's why "open source" is a really bad term that no one should use unironically, unless they want to confuse the hell out of people.

There are protective (copyleft) licenses, and there are permissive licenses - and they're very different beasts. And it's, like, software licensing 101.

> that want to go from LGPL to MIT or something

I find this extremely weird.

In a sane world, picking a copyleft license must mean that you care about user freedoms and want to make sure they're respected no matter what happens. Because that's the whole point of picking a copyleft license - not about letting people peek or tweak some code, not about social brownie points, and most certainly not about marketing campaigns - but about granting users their freedoms.

Either people get confused about "open source" and pick... I don't know, whatever looks cool, without even understanding what they're doing; or they're giving up on their principles when they smell the money.

I can understand wanting to go from, say, GPL to AGPL, or GPLv2 to GPLv3[+] - it would make sense, as it all goes in line of protecting freedoms. But LGPL to MIT is truly a weird one.

Re:CockroachDB License Change by riffraff on Thursday August 15, 2024 @05:28PM (#41260551)
(L)GPL to MIT is a choice many projects made when they decided they cared more about their code being used than about it staying free.

Copyleft licenses were the default choice at some point in time, but then in the '10s most big projects seemed to pick a permissive license, and many switched.

Re:CockroachDB License Change by drdaeman on Thursday August 15, 2024 @06:04PM (#41260906)
Yea, and the point is that they really should not have picked LGPL in the first place. If you pick a copyleft license, please don't do it because it's cool - do it if and because you care for what it stands for.

However, I thought about it and I think I can get the cases where monetary opportunities started to outweigh what's essentially are political ideals. Happens all the time, heh. I guess I can imagine person not being honest with themselves until the temptation really comes. Especially if it's about casual developers trying to have some money to live comfortably (as opposed to lowering their standards of living), rather than getting rich.

I can only hope it's that and not a simple ignorance.

Re:CockroachDB License Change by kodablah on Thursday August 15, 2024 @06:38PM (#41261199)
> picking a copyleft license must mean that you care about user freedoms [...] they're giving up on their principles

This is a personal bias and disregards others' definition of true do-whatever-you-want freedom. Different project owners may think differently on what free means and alter the license to respect their principles (and may consider copyleft to be the restrictive/anti-free mistake made early on based on these same kinds of personal biases).

And many contributors don't really care what the project owner does with their code and the CLA lets them delegate responsibility.

Re:CockroachDB License Change by immibis on Friday August 16, 2024 @03:38AM (#41264060)
It's been popular in the last decade and a half to think that freedom is when everyone, including massive corporations, can do anything they want with your software, including closing it and taking away everyone else's freedom. Don't people think it would be better if they couldn't do that?

People who value attention over principles are known as "pick mes" apparently.

Re:CockroachDB License Change by chii on Friday August 16, 2024 @05:59AM (#41264884)
> including closing it and taking away everyone else's freedom.

unless the corp owns the rights, they cannot "close it", nor take away everyone else's freedom. The old version that was open source licensed is always going to be available.

Unless you're talking about the additions these corporations made, which they keep closed, and charge you for it. But if they are able to charge for it, they deserve it.

Re:CockroachDB License Change by sgarland on Friday August 16, 2024 @08:12AM (#41265621)
> But if they are able to charge for it, they deserve it.

This is an extremely black-and-white view. If I make a competing product to you and it’s superior to yours, then yes, I deserve profits (though of course consumers may still choose yours for a litany of other reasons). If a trillion-dollar corporation becomes a competitor, that’s not exactly fair. They can, if they want, spin up an entire team dedicated to the product, and by sheer numbers, they will win. Is it legal? Yes. Is it ethical? That’s subjective.

Re:CockroachDB License Change by immibis on Friday August 16, 2024 @06:34AM (#41265087)
Embrace, extend, extinguish - AGPL makes it harder and SSPL even harder still.
Re:CockroachDB License Change by graemep on Thursday August 15, 2024 @05:39PM (#41260657)
That example is exactly why many people will not want to sign a CLA.

Someone who is has a strong preference for copyleft licences may not want to contribute to a project with a permissive license.

The intent may not be for the project owners to use the code in proprietary software, but it would be to allow someone to do so.

Re:CockroachDB License Change by kodablah on Thursday August 15, 2024 @06:31PM (#41261151)
Sure, and I think the CLA is a good signal to those that care about how their contribution is used to stay away. But for everyone else that's not concerned with that, the CLA is not inherently evil.
Re:CockroachDB License Change by shagie on Thursday August 15, 2024 @06:31PM (#41261156)
I wonder... if you do something with AGPL that requires releasing the changes back ... you don't need to sign a CLA to do that.

However that would also mean that the core project couldn't accept your changes without the CLA since that would also bind them to never switching the license or relicensing your contributions for an enterprise license.

... I think. My head hurts when trying to consider the implications for CLAs and AGPL and the endless debates that lawyers could have over this.

Re:CockroachDB License Change by immibis on Tuesday August 20, 2024 @06:39AM (#41298711)
That's the core project's own fault and problem, not yours.
Re:CockroachDB License Change by orthecreedence on Thursday August 15, 2024 @01:45PM (#41258583)
I think that's a bit reductive. It's possible to have a CLA because you want to sell a non-GPL version of your app to some corporation that's worried about the legalities of the license. This is an additional revenue stream that open-source projects make use of, and it's not fair to say "any project with a CLA is selling out."

There's this balance between being a project forever run out of someone's garage and actually growing into a larger and more used system. I'd say the line is dilineated by many factors: who is the project's primary user? Enterprise? Devs? How much money is changing hands? What's the business model? Is there investment involved? How restrictive is the primary license? How restrictive is the CLA?

I think any open-source project that has aspirations to actually make money for the creators is shooting themselves in the foot without a CLA. And it's fine to judge them for this, but we live in a system where people have to extract value out of this shit even if it's against their ethos.

If people truly and ultimately believe in open-source, then the most logical conclusion is that capitalism does not allow for open source and that must be changed. Fighting things at the license level can only delay the inevitable. But people want to have their cake and eat it too: "I want the system to stay the same AND I want open-source creators to keep pumping out stuff for free forever."

Re:CockroachDB License Change by lacker on Friday August 16, 2024 @12:35PM (#41267899)
This is not true. Many companies want a CLA because their lawyers are worried about unclear patent law. They don't want someone to contribute some code, and then later claim the contributed code violates their patents.

Good examples are React from Facebook, and TypeScript from Microsoft. Both require a CLA. But these projects are never going to go closed-source. They are complements to the companies' core business strategies.

Re:CockroachDB License Change by stubish on Friday August 16, 2024 @09:40PM (#41271750)
Imagine a world where GPLv2 was found to be unenforceable in a major jurisdiction such as the US. It has been a serious worry in the past. A CLA lets a project survive that situation. But I don't know if it is possible to have a CLA that also cannot be used to fork a project into a commercial license. So the trick would seem to be a CLA that assigns copyright to some sort of non-profit that is legally bound to be unable to take that path.
Re:CockroachDB License Change by rpaik on Saturday August 17, 2024 @01:09AM (#41272273)
Even if a project/company doesn't have a CLA, I don't think that is any sort of guarantee that their license won't change in the future.
Re:CockroachDB License Change by JohnDeHope on Thursday August 15, 2024 @11:46AM (#41257386)
Maybe we will have to replace "open source" with "spec driven". As you point out, open source can be just as bad as closed source, given future changes in direction by the project team. But "spec driven" means that anybody can come along and compete, and you can switch to them, regardless of how the original developers feel about it.
Re:CockroachDB License Change by graemep on Thursday August 15, 2024 @12:02PM (#41257522)
Is it not more about who does the development?

If cone entity does the development, they can change direction or licensing and it is hard for anyone to fork.

If you have more of a bazaar form of development with many contributors neither is as easy (even less so if you do not have a CLA). Even if you have a small core team of developers, a really bad direction is likely to lead to a split.

Re:CockroachDB License Change by evantbyrne on Thursday August 15, 2024 @12:23PM (#41257740)
I think you are right to think of it in terms of who is doing development. The plus of a non open-source license is well-funded development. The downside is fewer outside contributions. In this specific instance, I think Cockroach was BSL? So, it can be forked into a community project where new contributions are open-source. Another corporation just wouldn't be able to profiteer off the fork directly until the changeover date.
Re:CockroachDB License Change by acedTrex on Thursday August 15, 2024 @11:43AM (#41257348)
Open source and profit go together like oil and water
Re:CockroachDB License Change by valyala on Friday August 16, 2024 @10:18AM (#41266674)
Open source works great for for-profit companies. Take a look at RedHat.
Re:CockroachDB License Change by yawboakye on Thursday August 15, 2024 @10:56AM (#41256869)
start open/source available has become a trend among yc-backed startups lately. one wonders how long before a “well, actually, we need a business-y license.”
Re:CockroachDB License Change by brianwawok on Thursday August 15, 2024 @11:24AM (#41257145)
Lately? This was cool like 12 years ago. Then you turn commercial once you get enough users. It’s the open source chameleon model.
Re:CockroachDB License Change by karmakaze on Thursday August 15, 2024 @12:50PM (#41258010)
Opensource is opensource: CockroachDB Core up until Nov 24, 2024 is, and not afterward. Anyone who wants to fork it can do so. Mind you this will be a hard fork as there's no way to keep in sync with their enterprise product.

What you say is true in that you shouldn't view a VC backed opensource offering as 'permanently' opensource by the same group.

Re:CockroachDB License Change by geenat on Thursday August 15, 2024 @12:54PM (#41258056)
Kind of... Certain extensions such as basic backups are closed source and have never been in the OSS version.

Many things would have to be re-added from scratch in a fork.

Re:CockroachDB License Change by a-robinson on Thursday August 15, 2024 @01:54PM (#41258661)
"Basic" (i.e. full) backups have been included in the OSS version since its November 2020 release (20.2): https://www.cockroachlabs.com/blog/backup-restore/

They are still pretty limited compared to what's in the enterprise version, but it's not right to say basic backups are closed source and have never been there.

Re:CockroachDB License Change by geenat on Friday August 16, 2024 @12:45PM (#41268017)
CockroachDB Core uses 3 licenses: CCL, BSL, Apache

CCL, BSL = "source available"

Apache = open source

Parts of CockroachDB under CCL that do NOT transition to Apache OSS: https://github.com/cockroachdb/cockroach/tree/master/pkg/ccl

    > the sub-tree under pkg/ccl is under a different license (CCL) that does not transition to APL2 after a set duration.
https://github.com/cockroachdb/cockroach/discussions/127140#...
Re:CockroachDB License Change by karmakaze on Thursday August 15, 2024 @01:22PM (#41258342)
I'm having trouble parsing/making sense of this. Was basic backup in Core? If you were running anything more than Core you weren't running an OSS version and had already crossed that line before this announcement. If you were running an OSS version there's nothing to add, just fork, no?
Re:CockroachDB License Change by gerwim on Thursday August 15, 2024 @02:14PM (#41258865)
Core only has the "full backup". Incremental and other types are available to enterprise. I run the Core edition (with full backups) for my personal projects.
Re:CockroachDB License Change by geenat on Friday August 16, 2024 @12:36PM (#41267920)
CockroachDB Core uses 3 licenses: CCL, BSL, Apache

CCL, BSL = "source available"

Apache = open source

Parts of CockroachDB under CCL that do NOT transition to Apache OSS: https://github.com/cockroachdb/cockroach/tree/master/pkg/ccl

    > the sub-tree under pkg/ccl is under a different license (CCL) that does not transition to APL2 after a set duration.
https://github.com/cockroachdb/cockroach/discussions/127140#...
Re:CockroachDB License Change by nazka on Thursday August 15, 2024 @02:46PM (#41259146)
What happens the day where the only way to fork it realistically is to pay people. And I mean good people to even keep up? And what if on top of that the bests in the game are already in the corporations that you want to fork from?
Re:CockroachDB License Change by jen20 on Thursday August 15, 2024 @01:56PM (#41258683)
CockroachDB Core has not been offered under an OSI (i.e. Open Source) license since 2019 - everything subsequently has either been under Business Source License or the Cockroach Community License.
Re:CockroachDB License Change by karmakaze on Thursday August 15, 2024 @07:44PM (#41261682)
I searched github and thought this[0] was it.

> Source code in this repository is variously licensed under the Business Source License 1.1 (BSL), the CockroachDB Community License (CCL), the MIT license, BSD-style licenses, and other licenses specified in the source code. Source code in a given file is licensed under the BSL and the copyright belongs to The Cockroach Authors unless otherwise noted at the beginning of the file.

Is the caveat in this part (that I didn't catch before)? "Source code in a given file is licensed under the BSL and ..." That is sucky.

[0] https://github.com/cockroachdb/cockroach?tab=License-1-ov-fi...

Re:CockroachDB License Change by nsm on Thursday August 15, 2024 @12:52PM (#41258032)
Yep! I actually far prefer closed source software, made by non-VC funded companies, where there business is to create good software that actually adds value for the license I'm paying for. Something like Sublime Text or JetBrains.

Sure <VC funded editor company> can have people spend years of their life working on something, but release it as open source because VCs are paying for it, and that leads to more mindshare, but it leaves a bad taste in my mouth. Similar reasons to not use VSCode (commoditizing the complement by using billions of dollars from other products).

The "must be open source (I think they actually mean free as in $$) at all costs" crowd baffles me because the money to support the humans creating the software in the real world doesn't just magically appear.

Re:CockroachDB License Change by ElijahLynn on Thursday August 15, 2024 @02:17PM (#41258882)
I'm imagining that those closed source softwares wouldn't be possible without open source libraries and tools...
Re:CockroachDB License Change by pasc1878 on Thursday August 15, 2024 @04:07PM (#41259853)
I would imagine there is a lot on Windows possibly macOS.

Many c/C++ libraries are not open source - even more .Net ones

Re:CockroachDB License Change by sauercrowd on Friday August 16, 2024 @03:27AM (#41263998)
Open source as a byproduct of a company absolutely works - it's been proven by tons of tech companies.

But if you open source your revenue-generating parts, and only charge for support/managed version/enterprisey features you'll end up with quite weird incentives, particularly with infrastructure tools, in which the big cloud providers will happily compete with you, using the version you open sourced and providing and ecosystem to their customers that one simply cannot compete with

Re:CockroachDB License Change by swiftcoder on Friday August 16, 2024 @04:53AM (#41264528)
In the sense that most modern programming languages and compilers are open-source, sure, nothing outside the embedded world can truly be built without relying on open source.

There are still native shops that rely on very little open source, though at this point probably only in niches like gamedev or defence.

Re:CockroachDB License Change by Conan_Kudo on Saturday August 17, 2024 @06:27AM (#41273343)
This is not true even in those spaces anymore. Games these days require libraries like SDL, or (increasingly) use engines like Godot.

Defense is a weird place, but open source is used quite a lot there, it's often required to do so and to record the open source consumed to produce a product. And often times, it must be commercial open source where you can get engineering support for the lifetime of the product's existence.

Re:CockroachDB License Change by pjmlp on Saturday August 17, 2024 @12:08PM (#41275509)
Not at all, when talking about game consoles.
Re:CockroachDB License Change by Conan_Kudo on Saturday August 17, 2024 @02:02PM (#41276541)
Game consoles use them too, it's just mostly permissively licensed stuff.
Re:CockroachDB License Change by pjmlp on Saturday August 17, 2024 @02:11PM (#41276621)
Sure.
Re:CockroachDB License Change by sgarland on Friday August 16, 2024 @08:06AM (#41265569)
Correct. This is what makes me feel guilty about releasing a closed-source product, or even one with a non-OSI license. It’s irrational, but I feel like I’ve benefited so massively from FOSS that I owe it to the community to contribute back.
Re:CockroachDB License Change by pjmlp on Saturday August 17, 2024 @12:07PM (#41275502)
They were possible for quite some time, I guess people born after Linus created Linux have no idea how we used to pay for everything, or pirate.
Re:CockroachDB License Change by jaaron on Thursday August 15, 2024 @01:43PM (#41258559)
> IMO, it's not really open source if its run by a company that will eventually use its position to squeeze its users for cash.

I know it's not as popular or sexy as it used to be, but the whole point of a foundation like Apache was to avoid these situations, even more than the way the Linux Foundation is setup. Apache _explicitly_ manages projects to avoid these downsides.

- Single corporation ownership. Projects cannot get out of the Incubator unless they demonstrate a diverse and healthy community. That doesn't mean popular, it doesn't necessarily mean best-in-class, but it means that there shouldn't be just one entity backing a project.

- Membership in Apache is _personal_ not a seat for a given company. If you're a committer on an Apache project and you move jobs, you're _still_ a committer on that project

- The Foundation owns the trademarks. There have been fights about this in the past, but the whole idea is that the _community_ owns the name, so some corporation can't claim to be the sole or official owner by naming their company or product after the open source product.

The core premise of the Apache Software Foundation is community over code, that healthy, diverse communities have a better chance of standing the test of time than open source projects backed by a single individual or company. That's the thesis at least.

The is starkly different from several other foundations, notably the Linux Foundation or Eclipse Foundation which are modeled more around industry consortiums.

Both models have their place, but I believe Apache better models the core values many of us feel strongly about when it comes to free and open source software.

Re:CockroachDB License Change by timcobb on Thursday August 15, 2024 @10:37PM (#41262640)
What is more popular than the Apache Foundation? I thought Apache was top... Is there a cooler/better Apache? If so, please let me know.

And when was Apache more popular? I thought it was the uncool place where stuff was written in Java, that became popular because people's conception of Java (and the language/ecosystem itself) changed.

Re:CockroachDB License Change by mcpherrinm on Friday August 16, 2024 @01:10AM (#41263329)
I think CNCF is home to most of the big projects I’ve been contributing to or using lately.
Re:CockroachDB License Change by mikeyouse on Friday August 16, 2024 @01:40AM (#41263471)
CNCF is a project of the Linux Foundation - which has become absolutely massive: https://www.linuxfoundation.org/projects
Re:CockroachDB License Change by timcobb on Saturday August 17, 2024 @09:45AM (#41274559)
Ah yes, thank you! But would you say they more about infra/platform while Apache is more about application?
Re:CockroachDB License Change by immibis on Friday August 16, 2024 @03:27AM (#41264001)
Unfortunately the Apache Foundation structure has some (an unspecified number greater than zero) "kill all the Muslims now!" Israeli extremists in executive positions. I'm not exaggerating their positions for comedic effect. I'm not telling you their names because it would be harassment not allowed on HN. I emailed a couple of board members about this a few months ago and nothing seems to have happened, so I assume they condone it, and it may be time to boycott the foundation.
Re:CockroachDB License Change by worik on Friday August 16, 2024 @03:49AM (#41264130)
> Unfortunately the Apache Foundation structure has some (an unspecified number greater than zero) "kill all the Muslims now!"

Yuk.

It is a trap to condem the foundation because of some people who are nasty outside the foundation

If they were enabled to stand in the way of Mahdi Islam, or their mates participating then there would be a problem

We have a problem in tech with naive fascists and fascist enablers. We must deal with it, but condemning the person, not the behavior, is not the way

Mahdi Islam is made up

Re:CockroachDB License Change by immibis on Friday August 16, 2024 @06:35AM (#41265095)
I'm sorry but I cannot trust an organisation headed by people who want to exterminate Muslims. If you feel differently, that's on you, and I urge you to reconsider your feelings.

At first the behaviour should be condemned. If the person refuses to change the behaviour, the person is now at fault for choosing the behaviour which they know to be condemned.

Re:CockroachDB License Change by anonfordays on Friday August 16, 2024 @11:06AM (#41267073)
>We have a problem in tech with naive fascists and fascist enablers.

No we don't.

Re:CockroachDB License Change by immibis on Saturday August 17, 2024 @06:59AM (#41273510)
We have a problem with "he may be a really shitty person but we ignore that because he does the work". In some cases where that person does a lot of work, it may be unavoidable. In other cases where the person does only a small amount of work, it's a mistake not to push back on their bad beliefs.

A similar but opposite problem is pushing back too much on things that don't matter. E.g. a core python developer and inventor of Timsort just got a 3 month suspension for liking a comedy skit that used the word "slut", and for thinking that it's possible to discriminate against white people.

Re:CockroachDB License Change by anonfordays on Monday August 19, 2024 @10:45AM (#41291498)
>We have a problem with "he may be a really shitty person but we ignore that because he does the work".

Social human endeavours where different people of different backgrounds come together to work towards a common goal universally suffer from this. This is in no way specific to software development communities. So I disagree, it's not a problem specific to the aforementioned domain.

>In other cases where the person does only a small amount of work, it's a mistake not to push back on their bad beliefs.

Therein lies the issue: no one person has a say on what is considered a "bad belief." This is exceedingly difficult when you work with persons whom are not from or steeped in west coast SV culture. Europeans do not have the same sensibilities as someone from San Francisco.

>E.g. a core python developer and inventor of Timsort just got a 3 month suspension for liking a comedy skit that used the word "slut", and for thinking that it's possible to discriminate against white people.

Just read about this. Incomprehensible.

Re:CockroachDB License Change by worik on Sunday August 18, 2024 @03:26PM (#41284726)
Peter Thiel

Elon Musk

There's two

Re:CockroachDB License Change by anonfordays on Sunday August 18, 2024 @04:27PM (#41285212)
>Peter Thiel

Not a fascist nor fascist enabler.

>Elon Musk

Not a fascist nor fascist enabler.

Swing and a miss. Glad I could clear that up.

Re:CockroachDB License Change by Someone on Friday August 16, 2024 @05:36AM (#41264760)
Apache is both popular and “the place where projects go to die”. They have many, many projects that see limited development activity and aren’t well-known (how many projects in https://projects.apache.org/projects.html?name do you even vaguely know of what they’re about?)

I also think the popularity of the Apache license is part of what makes Apache popular.

> I thought it was the uncool place where stuff was written in Java

They have lots of projects running on the JVM, but “written in Java” isn’t a requirement, nor is “running on the JVM”. See https://projects.apache.org/projects.html?language

Re:CockroachDB License Change by cmrdporcupine on Friday August 16, 2024 @09:39AM (#41266330)
EDIT: wrote something stupid here before my morning coffee
Re:CockroachDB License Change by pquerna on Friday August 16, 2024 @10:10AM (#41266600)
This is an Eclipse foundation project, not an Apache Software Foundation (ASF) project?

it's all volunteers/open source, but this isn't an ASF project.

Re:CockroachDB License Change by cmrdporcupine on Friday August 16, 2024 @10:13AM (#41266632)
I'm sorry, I hadn't finished my coffee yet.

I'm gonna go embarrasingly delete this thread tail between my legs...

Re:CockroachDB License Change by caniszczyk on Friday August 16, 2024 @11:59AM (#41267530)
Apache isn't a silver bullet... there are plenty of Apache projects where the individuals are compromised mostly from one company and hide behind the veneer of the ASF... where they are working on the projects per their employment. Gerrymandering is definitely possible and has happened in the past, that's why you have to look at governance and ownership of the marks/build systems etc: https://www.aniszczyk.org/2019/10/08/open-source-gerrymander...

I actually prefer the approach of LF, EF or CNCF where it's transparent where folks work for and your affiliation is disclosed upfront. In the CNCF for example, we separate out technical project decisions (maintainers) from funding decisions (members). That is healthier than blending it all in one at the ASF imho and having no idea where person is working for imho.

Re:CockroachDB License Change by FireBeyond on Friday August 16, 2024 @12:43PM (#41267989)
Agreed. Red Hat isn't perfect, but when I worked there we had a few products that were CNCF under my umbrella, including a few incubator projects. Even though we had several developers working full or part time on those projects, it was always something I was meaningful of, not stacking the project board Red Hat-heavy, to not make it a defacto RH project.
Re:CockroachDB License Change by KetoManx64 on Friday August 16, 2024 @02:22PM (#41268935)
After the RedHat/Hyprland fiasco, it feels like RedHat is corrupt with SJW that are focused more on polics than on actual code
Re:CockroachDB License Change by eikenberry on Thursday August 15, 2024 @09:39PM (#41262316)
This is one reason to avoid any company run software that requires a CLA to contribute. No CLA makes it a lot harder to do this, at least if they have very much in the way of community contributions. Distributed ownership would keep them honest.
Re:CockroachDB License Change by gsich on Friday August 16, 2024 @05:22AM (#41264685)
EEE all over again.