News for hackers. Stuff that matters.
Re:HashiCorp Did It Backwards by gobins on Tuesday September 05, 2023 @06:23PM (#37398618)
This is probably going to get a lot flake but what did we expect when big tech started eating up open source solutions and competing with the companies who started the work . MongoDB and AWS is a good example. Hashicorp probably realised that they should preemptively change the licensing before bigger players started using the products to directly compete with them.

I want Hashicorp to survive and be profitable. Fact is, for the majority of the users who use terraform, the change in licensing does not impact them.

Re:HashiCorp Did It Backwards by galenmarchetti on Tuesday September 05, 2023 @06:28PM (#37398675)
True...it's just difficult to draft a license that says something along the lines of "If you're Big Tech, we have the right to go after you, if you're small startup, you're safe".

I think there's a swath of Terraform users (likely minority) who find themselves in a legal gray area, or a legal black-and-white area, where they're directly at risk. Even if Hashicorp never intended to target small startups with this, the wording of the license unfortunately applies and is enough to make anyone nervous.

I think MongoDB had a similar issue when they went source-available, they seemed to intend to only protect themselves from big tech but unfortunately a lot of smaller players got spooked. I think (?) it's fine now though

Re:HashiCorp Did It Backwards by solomatov on Tuesday September 05, 2023 @06:33PM (#37398727)
> True...it's just difficult to draft a license that says something along the lines of "If you're Big Tech, we have the right to go after you, if you're small startup, you're safe".

Take a look at the license of LLAMA2 by FB. It has a clause just like this. I.e. limit by number of users.

Re:HashiCorp Did It Backwards by galenmarchetti on Tuesday September 05, 2023 @06:41PM (#37398801)
wow, didn't know about this. very cool + would be interesting to see this in more places. Just checked it out. for those lazy:

"If, on the Llama 2 version release date, the monthly active users of the products or services made available by or for Licensee, or Licensee's affiliates, is greater than 700 million monthly active users in the preceding calendar month, you must request a license from Meta, which Meta may grant to you in its sole discretion, and you are not authorized to exercise any of the rights under this Agreement unless or until Meta otherwise expressly grants you such rights."

Re:HashiCorp Did It Backwards by woah on Tuesday September 05, 2023 @06:31PM (#37398703)
yea, that makes all the difference. If it was almost all Hashicorp, the open source was a marketing gimmick and I don't blame them for not risking the entire business on it. If there was heavy involvement from external contributors, then removing open source is more of a rug pull.
Re:HashiCorp Did It Backwards by derobert on Tuesday September 05, 2023 @07:27PM (#37399216)
I don't know if it'd really be hard (you could list them, or have various limits on users or total revenue among all related companies). You could broadly include all subsidiaries, contractors working for Amazon, companies effectively under their control, etc. (Ultimately it'll be interpreted by a judge, not an algorithm, that probably makes it harder to get around.) There is nothing illegal about offering a license to everyone except Amazon, Microsoft, and Google.

But none of those licenses would be open source licenses. That's the problem with doing it — you can't do that in an open source license.

The no discrimination clauses are a requirement of the open source definition, not the law. (The law of course does have some non-discrimination requirements, not sure how many of those apply to copyright licenses. But none of the normal ones would prohibit "everyone but Amazon may use this".)

Re:HashiCorp Did It Backwards by arianvanp on Tuesday September 05, 2023 @06:32PM (#37398710)
AGPL it.

Big tech hates it and bans it outright. Which means it's the correct choice.

Re:HashiCorp Did It Backwards by Znafon on Tuesday September 05, 2023 @06:40PM (#37398796)
It's not just big tech that hates AGPL. If Terraform was under AGPL a lot of companies might have to release their source code as AGPL too because of its virality. Where it stops is not exactly clear from the license.
Re:HashiCorp Did It Backwards by jen20 on Tuesday September 05, 2023 @06:49PM (#37398895)
Where AGPL stops is actually very well defined.
Re:HashiCorp Did It Backwards by eduction on Tuesday September 05, 2023 @07:37PM (#37399320)
Not really. The lawyer Kyle Mitchell said of the agpl,“Inebriated aliens might as well have beamed it down from space as a kind of practical joke.” Even lawyers have trouble understanding when its provisions are triggered.

https://writing.kemitchell.com/2021/01/24/Reading-AGPL

Use OSL3!

Re:HashiCorp Did It Backwards by Znafon on Tuesday September 05, 2023 @07:26PM (#37399213)
The AGPL defines "Corresponding Source" as "all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities".

Then in section 13 it says that "your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge".

Isn't "scripts to control those activities quite vague? Under those terms wouldn't AWS Proton, IBM Schematics, Env0, Digger, Spacelift, etc. be required to open-source a very large part of their product as well?

Re:HashiCorp Did It Backwards by galenmarchetti on Tuesday September 05, 2023 @08:04PM (#37399571)
I think, if Terraform was licensed under AGPL, then not only would all of those folks would have to also open-source their products, but also that would be the intent of the license in the first place
Re:HashiCorp Did It Backwards by chc on Tuesday September 05, 2023 @07:09PM (#37399050)
AGPL is almost exactly the same as GPL except that SAAS counts as distribution. That's the entire purpose of the license — to preserve the copyleft protections of the GPL in a world where most software people use is hosted.
Re:HashiCorp Did It Backwards by galenmarchetti on Tuesday September 05, 2023 @07:25PM (#37399208)
Love this framing of the license...as Stallman said, who does that server really serve? https://www.gnu.org/philosophy/who-does-that-server-really-s...
Re:HashiCorp Did It Backwards by ninkendo on Tuesday September 05, 2023 @08:02PM (#37399558)
Except it’s not just hosting the covered work itself as SAAS that triggers a distribution, but any derived work. If you use (say) AGPL MongoDB in your SAAS bug tracker, your bug tracker now needs to be AGPL too. The virality doesn’t stop at hosting a SAAS MongoDB.
Re:HashiCorp Did It Backwards by candiddevmike on Tuesday September 05, 2023 @08:06PM (#37399588)
That's probably not correct. While the AGPL is a little ambiguous, it probably does not infect other apps. That's why I created the Candid Public License (CPL): https://github.com/candiddev/cpl
Re:HashiCorp Did It Backwards by ninkendo on Tuesday September 05, 2023 @08:30PM (#37399789)
Every lawyer I’ve talked to takes my interpretation. It may be overly cautious of them, but in practice, if something becomes the prevailing legal view, it de facto is the correct interpretation, at least until it is tested in court.
Re:HashiCorp Did It Backwards by candiddevmike on Tuesday September 05, 2023 @08:42PM (#37399885)
I would find new lawyers, the AGPL is just the GPL with the addition that network access counts as distribution:

https://www.gnu.org/licenses/why-affero-gpl.html

https://fossa.com/blog/open-source-software-licenses-101-agp...

Re:HashiCorp Did It Backwards by ninkendo on Tuesday September 05, 2023 @09:04PM (#37400077)
Recall that the GPL (non-affero) categorizes runtime linking to GPL’d binaries as a derived work. (This is why the LGPL exists, to allow for what the regular GPL restricts.)

The logic of the lawyers I’ve talked to (2 different companies on multiple occasions with different lawyers) is that the same wording that causes network access to count as “distribution” in the AGPL, also causes networked API access to count as a derived work.

It’s not all that crazy of an interpretation, IMO. My lawyers may suck and be overly cautious, but I’d wager this uncertainty is exactly why any sane company stays as far away as possible.

Re:HashiCorp Did It Backwards by dragonwriter on Tuesday September 05, 2023 @09:07PM (#37400102)
> Recall that the GPL (non-affero) categorizes runtime linking to GPL’d binaries as a derived work

If its not a derived work under copyright law requiring a license, a license offer can’t transform it into a derived work requiring a copyright license.

Re:HashiCorp Did It Backwards by ninkendo on Tuesday September 05, 2023 @09:24PM (#37400264)
So, thought experiment: say I do want to take AGPL MongoDB, alter its source code, and host my modifications as a SAAS without releasing my modifications, and get away with it.

One way I could do this is by completely implementing its wire-format API of MongoDB as a proxy server to my derived MongoDB, and offer that up as my SAAS.

I could use a defense that I’m not distributing MongoDB, I’m distributing my proxy service I wrote myself. It just happens to be that my proxy service talks to MongoDB to do its job, but according to you that’s not a derived work, because network access doesn’t count.

For AGPL to still protect MongoDB in this scenario, the proxy-plus-mongoDB combo would have to count as the derived work, and I think the only way to do this is to count any API access as deriving a work. I think this is at least how the lawyers I’ve talked to described it.

GPL has already established that runtime linking counts as a derived work. If what you’re saying is true about “not a derived work under copyright law requiring a license”, then I don’t understand why the LGPL exists.

Re:HashiCorp Did It Backwards by tzs on Tuesday September 05, 2023 @10:26PM (#37400708)
GPL's source disclosure requirements trigger on distribution.

AGPL's trigger on distribution or on allowing remote user interaction over a computer network.

> I could use a defense that I’m not distributing MongoDB, I’m distributing my proxy service I wrote myself

You aren't distributing either of them. When you run code on your server and people interact with it over the network that's not a distribution. If it was a distribution there would be no need for AGPL. GPL would be sufficient.

> It just happens to be that my proxy service talks to MongoDB to do its job, but according to you that’s not a derived work, because network access doesn’t count.

It's not a derivative work because it doesn't incorporate copyrighted elements of MongoDB (assuming you didn't actually copy code from MongoDB).

> For AGPL to still protect MongoDB in this scenario, the proxy-plus-mongoDB combo would have to count as the derived work, and I think the only way to do this is to count any API access as deriving a work.

AGPL would protect MongoDB in that scenario because you are allowing remote users to interact with MongoDB over a computer network. That this interaction happens to be taking place through a proxy shouldn't be relevant.

Re:HashiCorp Did It Backwards by taway1237 on Wednesday September 06, 2023 @05:50AM (#37403086)
Doesn't it prove GP's point? If you use MongoDB in your commercial software it gets infected with AGPL, because people interact with it over the internet - just like linking does with GPL.
Re:HashiCorp Did It Backwards by ninkendo on Wednesday September 06, 2023 @07:07AM (#37403505)
> You aren't distributing either of them. When you run code on your server and people interact with it over the network that's not a distribution. If it was a distribution there would be no need for AGPL. GPL would be sufficient.

I think you’re misreading this part of my comment: MongoDB is (or at least, was) AGPL, and AGPL defines network access as distribution. So I would have to justify whether offering my proxy service to network access counts as distributing MongoDB, or if laundering it through a proxy works around this. Remember that in my example, I did modify mongoDB. But I’m not technically offering this modified mongoDB as a service, I’m offering my proxy as a service, and hoping that it doesn’t count as “distribution” of my modified mongoDB. (i.e. I’m not distributing mongo, I’m distributing my proxy, and my proxy is not AGPL.)

> AGPL would protect MongoDB in that scenario because you are allowing remote users to interact with MongoDB over a computer network. That this interaction happens to be taking place through a proxy shouldn't be relevant.

Well, that’s the thought experiment that my example is intended to provoke… it seems obvious that my dumb proxy is a way to work around the AGPL, but what if we tweak the example? What if I make a web UI where you type mongo commands and it gives you the result? (Still pretty obvious, no?) What if I make a simple dumb CRUD app that happens to use MongoDB? (Less obvious…) what if the CRUD app is itself an extremely thin wrapper, and although it doesn’t implement any MongoDB protocols, it leverages built-in mongoDB functionality for 99% of the logic?

The point is, it’s not hard to imagine a legal theory that says “if network access equals distribution, then network access equals a derived/combined work”. It’s the theory that the legal departments of several companies I’ve worked for have taken. And I’d argue that if you have a proprietary product that uses an AGPL service as part of the backend, you have a rather large reason to be worried.

Re:HashiCorp Did It Backwards by assbuttbuttass on Wednesday September 06, 2023 @08:45AM (#37404311)
By my reading, the AGPL doesn't define "distribution" at all. It defines "conveying":

    To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying
This definition specifically excludes networked API access.

Here's what the AGPL says about network access:

    Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
It only applies if you "modify" the program. Does creating a proxy service count as modifying the original program? I think it could count as a derived work, but I would be very surprised if that counts as a modification.
Re:HashiCorp Did It Backwards by dragonwriter on Tuesday September 05, 2023 @10:55PM (#37400846)
> GPL has already established that runtime linking counts as a derived work

No, whether runtime/dynamic linking (or even static linking) creates a derivative work under copyright (as is when, to the extent it does, such a use would nonetheless be fair use and still not require a license) is still a contentious topic, and AFAIK there are no cases strongly suggesting a general answer.

A license offering permission cannot itself resolve when the law requires such permission. Arguing that it can is like saying my offering terms of permission to use my home and claiming that they apply to use of the public street out front establishes that I own the street.

Re:HashiCorp Did It Backwards by ninkendo on Wednesday September 06, 2023 @07:25AM (#37403595)
If your argument is that AGPL can’t restrict me from using mongo in a proprietary product because copyright law itself does not restrict this, then you may or may not be right, I don’t think any of us know for sure until this is tested in court. I will say that the AGPL is written with the assumption that this is restricted by copyright law, so I don’t think your interpretation is the common one.
Re:HashiCorp Did It Backwards by kiratp on Wednesday September 06, 2023 @12:22AM (#37401324)
> One way I could do this is by completely implementing its wire-format API of MongoDB as a proxy server to my derived MongoDB, and offer that up as my SAAS

This is what Cosmos DB for Mongo DB is (wire format endpoint that talks to Msft’s own DB backend.)

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/in...

Re:HashiCorp Did It Backwards by Znafon on Tuesday September 05, 2023 @09:18PM (#37400206)
The AGPL says "including scripts to control those activities" but if I understand what you are saying properly it means that the text of the AGPL is overreaching and some parts of it wouldn't be applicable?

Would the details depend on the country? Like it might be one thing under US law, and another in another country?

Re:HashiCorp Did It Backwards by tzs on Tuesday September 05, 2023 @10:02PM (#37400554)
> Recall that the GPL (non-affero) categorizes runtime linking to GPL’d binaries as a derived work.

Generally a bug tracker (SAAS or not) that uses a database does not need to link to the database unless the database is SQLite.

Re:HashiCorp Did It Backwards by ninkendo on Wednesday September 06, 2023 @07:27AM (#37403602)
If the AGPL defines network access as distribution, it stands to reason that network access also counts as linking. See my other comments about a hypothetical proxy that thinly wraps mongoDB as an AGPL workaround, for why this gets hairy very quickly.

https://news.ycombinator.com/item?id=37400264

Re:HashiCorp Did It Backwards by imtringued on Wednesday September 06, 2023 @04:40AM (#37402695)
You guys will do everything and anything except read the license terms and then make up whatever lies you want, to make the AGPL look bad.
Re:HashiCorp Did It Backwards by imtringued on Wednesday September 06, 2023 @04:37AM (#37402668)
AGPL does not add any distribution clause... all distribution clauses are taken from the GPL...

The AGPL adds a modification clause so that if you ever modify the code even if you do not distribute the application, you still have to share the code or at least link to the version of the source code that you use. The loophole that AGPL fixes is that there are ways to avoid distribution.

This AGPL/GPL virality urban legend should have ended years ago.

Re:HashiCorp Did It Backwards by imtringued on Wednesday September 06, 2023 @04:33AM (#37402654)
There is no such thing as "virality". It doesn't exist. The worst thing you can do is violate the license terms and not be allowed to use the software that is AGPL licensed.
Re:HashiCorp Did It Backwards by taway1237 on Wednesday September 06, 2023 @05:52AM (#37403107)
And yet everyone understands what this term means when applied to software licensing. Pretty good argument that this word, in fact, exists and has a well defined meaning.
Re:HashiCorp Did It Backwards by tzs on Tuesday September 05, 2023 @08:18PM (#37399685)
AGPL doesn't address the issue that is driving many of these license changes.

The problem they are trying to deal with is that they have some product that is useful on servers that they have released under a license like Apache or GPL, and they make their money by selling hosting and support, and big hosting companies like AWS start including the product for free as part of their own hosting offerings or start selling support.

AGPL would only discourage that if the big hosting company wanted to make modifications to the project and keep those private. But the threat to the project is not that say AWS is going to make a better version of the product. It is that they are going to make it more convenient and cheap for their hosting customers. They will either not need to make any changes for that, or the changes they make would probably not be useful to anyone else and releasing them won't bother them.

Look at MongoDB. That was under AGPL for several years and they switched away because it was not stopping cloud providers from competing with them on MongoDB hosting.

Re:HashiCorp Did It Backwards by jzb on Tuesday September 05, 2023 @08:56PM (#37399997)
Why isn’t the AGPL sufficient here? Also, should we be rethinking adopting vendor-led projects overall?
Re:HashiCorp Did It Backwards by wongarsu on Tuesday September 05, 2023 @09:30PM (#37400315)
offtopic, but it's "getting a lot of flak". As in "heavily being fired on by German anti-air guns" (called FlaK, short for Flugabwehrkanone, literally anti-aircraft cannon)
Re:HashiCorp Did It Backwards by dragonwriter on Tuesday September 05, 2023 @10:21PM (#37400680)
> This is probably going to get a lot flake but what did we expect when big tech started eating up open source solutions and competing with the companies who started the work

Big tech started doing that when open source as fairly young, and it was never a problem, because no one was launching a business centered around making open source software and being better than big established firms at selling services around it.

What actually created the crisis is when, a couple decades later, people started to launch VC backed startups with the growth demands that involves and business plans that centered around creating open source software and selling hosted access to it.

Re:HashiCorp Did It Backwards by gobins on Tuesday September 05, 2023 @11:53PM (#37401160)
Even for VC backed startups, I think it was never a problem until cloud providers started competing with them. It is not a level playing field if your competitors are big players like Amazon who can take away a lot of your possible customers.
Re:HashiCorp Did It Backwards by dragonwriter on Wednesday September 06, 2023 @10:20AM (#37405553)
> Even for VC backed startups, I think it was never a problem until cloud providers started competing with them.

Cloud providers (and SaaS providers before the dynamic provisioning for which “cloud” was coined existed) have been offering commercial hosted OSS solutions since before there were VC-backed “our whole business model is developing OSS and selling hosted access to it” startups.

The thing that changes was the startups trying to trade on OSS' cultural impact with a business model that made no sense, not the practices of cloud providers.

Re:HashiCorp Did It Backwards by xign on Friday September 08, 2023 @06:40PM (#37440211)
Fair enough, but it was never a problem because most software like Terraform would not have been open source to begin with in the good old days. So in a way yes, what you said is true, but I don't think the takeaway is "open source used to work just fine", but rather "sometimes a non-open-source license is really what works in this scenario".
Re:HashiCorp Did It Backwards by bewo001 on Wednesday September 06, 2023 @07:59AM (#37403826)
I am working for a Big Corp. I have see many instances where we made expensive contracts with small companies maintaining open source solutions. It fits existing processes and we have somebody who will fix stuff. Most of the time, it would be much more expensive to keep a team to maintain the software ourselves.