News for hackers. Stuff that matters.
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.