5 ms·
Absolutely nothing would happen. If Google put Citus (for example) on their servers, they would have to release the source code for Citus and everything it's l
by bryanlarsen 9y ago
Absolutely nothing would happen.
If Google put Citus (for example) on their servers, they would have to release the source code for Citus and everything it's linked to, which might include PostgresSQL but wouldn't include anything else.
It's a pretty big stretch to believe that just checking Citus into their monorepo, exposing it to the world and accessing it from an internal service would constitute a link and require release of any of their proprietary code.
Google may not want to take that risk, but that risk is miniscule IMO. IANAL.
- onli 9y agoRight. Any other interpretation is the "GPL is cancer"-FUD propagated by enemies of free licenses, like Microsoft under Balmer. Though lawyers like to err on this side of license interpretation.
- CogitoCogito 9y agoWhy is this being down-voted? It's totally correct. GPLed code linked into a program doesn't magically make the program GPLed. The GPL guarantees that as long as you provide the source code of your code under the GPL, you automatically get a license to use other GPLed code in your code. If you use GPLed code, but don't provide your code under the GPL, then you are probably infringing copyrights. That can be mitigated (assuming you're honorable and don't just hide it) by possibly paying the authors of the GPLed code to get a license under different terms, or possibly removing the code in question and maybe paying the original authors, or by fighting in court and possibly being forced to stop distributing the code and then removing the code and paying fines, or (as many assume is the only option) releasing their own code under the GPL as well. The details of what would occur almost certainly depend on the circumstances (was it known, when was it known, was it on purpose, did it have any real effect or was it a random bit of source code that was basically unused, etc.) and jurisdiction as well. Regardless it's definitely not the case that the GPL just magically infects any code it touches. That is a ridiculous simplification that is mostly spread by ignorance or those spreading FUD. Hell the GPL doesn't even do anything at all until the programs themselves is distributed. It's perfectly reasonable to prefer other licenses over the GPL, but let's not make up reasons to dislike it.
- bryanlarsen 9y ago"GPLed code linked into a program doesn't magically make the program GPLed" Lots of people for debatable but legitimate reasons believe that GPLv2 does this. They don't realize that this doesn't apply to GPLv3, nor to the AGPLv3.
- CogitoCogito 9y ago> "GPLed code linked into a program doesn't magically make the program GPLed" > Lots of people for debatable but legitimate reasons believe that GPLv2 does this. > They don't realize that this doesn't apply to GPLv3, nor to the AGPLv3. Honestly I simply think you're not understanding me. Let me summarize: linking GPLed code without GPLing your own code and without having any other license to do so is copyright infringement. There are multiple ways to avoid infringement. You can pay the authors for another license, you can possibly remove the code and pay the authors enough so they're drop the matter, you can go to court, or you can release your own code under the GPL. You do understand that that is not the same as saying that "linking GPLed code to your code makes your code GPLed" right? edit: Apologies if I misunderstood you when you said: "Lots of people for debatable but legitimate reasons believe that GPLv2 does this." Maybe you don't believe this yourself (which is what I assumed when drafting my reply here). I agree with you that lots of people believe this, but it basically isn't debatable and certainly is wrong. Put another way: What is the legal rationale for the claim that linking GPLed code immediately makes the linking code GPLed?
- ghaff 9y agoAssuming that linked code is distributed. You can use it internally as much as you want. (With the caveat that distribution has a broader meeting under AzGPL.)
- CogitoCogito 9y agoYou are 100% correct that you can execute/link/etc. GPLed code without following the terms of the license when you're not distributing your code. But I'm not referring to distribution. I'm saying that if you were to link your own non-GPLed code to GPLed code _and_ you were to distribute it, your code would not automatically become GPLed code. You would be infringing upon copyright. There are multiple options to stop that infringement which do not involve GPLing your code.
- derekp7 9y agoSo does that mean that AGPL code isn't suitable if you need to interface it to, for example, an Oracle DB as you don't have the source or rights to release Oracle (as an example)? If that's the case, then I could see why it would be on the no-list. Google has a bunch of internal secret sauce that may need to be called on by an external-facing app.
- bryanlarsen 9y agoNot at all. You don't have copyright permission to modify Oracle DB, yet you are using it lawfully, therefore via the definition of "modified work" in the AGPL it's not covered by the AGPL.