Hacker News new | ask | show | jobs
by Eridrus 3543 days ago
I'm not sure how the legal details play out, but it seems like they licensed their client drivers as Apache, so the intent seems to be that the AGPL is intended to make sure they get patches, even if you're selling hosted RethinkDB, not just using RethinkDB in your commercial SaaS software. Or at least that's what I gather from the FAQ https://rethinkdb.com/faq/

I don't know if this is a sound legal interpretation of the AGPL though. My obvious concern would be that the AGPL extends to the rest of our production code.

1 comments

> I don't know if this is a sound legal interpretation of the AGPL though.

Exactly. AGPL was explicitly created to make all clients of the software be bound by its license. To say that the drivers have a different license makes no sense at all.

> Exactly. AGPL was explicitly created to make all clients of the software be bound by its license. To say that the drivers have a different license makes no sense at all.

huh? AGPL puts no requirements on clients of the software. Otherwise I wouldn't be allowed to use IE to connect to AGPL webapps. AGPL puts extra requirements on people using the software on servers.

My layman's understanding of the AGPL was that it essentially extends the concept of linking to connecting to the software that interacts over the network, so that you can't do something like take a library, wrap it in a microservice and just call the microservice in your product without opening your entire software stack to AGPL claims.

Maybe I am misunderstanding it, but I would want a lawyer to tell me that before using any AGPL code.

That's completely different from my understanding.

My understanding is that it somewhat extends the concept of "distributing" to providing remote access over a network:

"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.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License."