5 ms·
> refutes this claim I do not think that word means what you think it means. "disputes" might be more accurate, but that still wouldn't invalidate the title.
by JoshTriplett 13y ago
> refutes this claim
I do not think that word means what you think it means.
"disputes" might be more accurate, but that still wouldn't invalidate the title. This is an entirely legitimate bug report; the maintainer of Capistrano seems to hold a very unusual view on Open Source licensing, and one at odds with just about everyone else in the Open Source community.
- mintplant 13y agoOn the contrary. "refute" is defined as: > refute - v, prove (a statement or theory) to be wrong or false; disprove. I contend that this section does disprove the theory that Capistrano cannot continue to be licensed under the MIT License: > that in this circumstance the copy-left of the GPL does not cross the boundary of Rubygems (Capistrano hints to Rubygems that it would like to use SSHKit). And that even using the LGPL with it's provision for "dynamic linking" being an exception adds nothing to the discussion for scripting languages. Of course, this is all semantics.
- argonaut 13y agoYou forgot to claim that you know more about digital IP than Capistrano's digital IP lawyer. Oh wait...
- tzs 13y agoNo, refutes is entirely correct. The lawyers for the company that owns SSHKit say there is no licensing issue.
- JoshTriplett 13y agoEither the company in question is creating some strange implicit exception to the GPL, or proprietary/GPL-incompatible products derived from Capistrano are in violation of the GPL and the company in question simply declines to pursue those violations. Here's the statement from the folks who wrote the GPL, on this exact point: https://www.gnu.org/licenses/gpl-faq.html#GPLWrapper https://www.gnu.org/licenses/gpl-faq.html#GPLWrapper
- tzs 13y agoThe statement you quote is not on point, since there is no "module B" here. What they are trying to describe in that is the situation where someone takes a GPL piece of code, and writes a wrapper module (module B) that adds some kind of interface that their proprietary module (module C) knows how to interface with, and then they distribute this whole mess. As far as I can see, Capistrano has not wrapped SSHKit or modified it. It just invokes SSHKit through its public interfaces. In particular, Capistrano does not seem to be a derivative work of SSHKit. If it and SSHKit are distributed together, this would be what the GPL calls mere aggregation. Conceptually, it is no different than distributing bash along with a bash script that is not under GPL.
- JoshTriplett 13y ago> The statement you quote is not on point, since there is no "module B" here. What they are trying to describe in that is the situation where someone takes a GPL piece of code, and writes a wrapper module (module B) that adds some kind of interface that their proprietary module (module C) knows how to interface with, and then they distribute this whole mess. Other than flipping C and A around, what you describe exactly matches the situation from the GPL FAQ. Apart from that, I'm not going to argue GPL, derived works, and linking here; suffice it to say that the interpretation of the GPL authors is that code calling into GPLed code (directly or indirectly) is a derived work and subject to the GPL, and thus may not be proprietary. That's the interpretation and intention of the FSF in writing the license, and it's the standard interpretation in the broader FOSS community.
- tzs 13y agoIn all the cases I'm aware of where courts have considered code calling into other code, they have found that this does not make the caller a derivative work of the callee. Here's a good quick and dirty test. If I write code that interfaces to your code, and I do this without looking at anything of yours other than things that are not copyrighted (such as your publicly documented interfaces), then my code cannot be a derivative work of your code. If I want to distribute my code (in source or binary), and I'm not distributing your code with it, then I don't have any reason to care what license your code is using. Now, if I've going to take my code, and your code, and compile and link them together and distribute the result, then (1) I've actually copied your code into something I'm distributing, and (2) I'm distributing your code. In this case, your license is very relevant. This is the kind of situation the FSF was mostly thinking of when they wrote most of that FAQ. I think they were caught off guard by the explosive rise of the so-called scripting languages, which do away with the whole linking things together into a package to distribute thing. This is very good for free software. If calling into code (directly or indirectly) made the caller a derivative work of the callee, then it would be a copyright violation to make and distribute apps for jailbroken iPhones. These apps call into Apple's system software, and so would be derivative works and require Apple's permission to distribute, and Apple has not given that permission. It would be similar for desktop operating systems--application writers would need permission from the OS copyright owner to make applications that run on that OS. Capistrano is distributed in source form (and as far as I can see that is the only form in which it is distributed). Looking at the source, I don't see them including anything copyrighted from SSHKit. I'm not a Ruby guy, so maybe I missed some tricky Ruby thing that would make it non-obvious. Any Ruby users want to take a look?