« Return to Thread: [scala] Collections performance

Re: [scala] Collections performance

by Sean McDirmid :: Rate this Message:

I wasn't talking about stealing code. Just copy it, label it as a derived work, and make sure the appropriate license is used. GPL definitely allows for that, there is nothing wrong with creating a derived work as long as the original work is attributed and the derived work is released under GPL. Isn't that what GPL is for? Also, you can link your applications to a GPL library and still have the application be commercial, you just can't modify/create a derivative of the library that is closed source.

OK, I see I've entered into a license hell discussion, but better to have it now then after we've actually ported code :)

On Wed, Jul 30, 2008 at 8:46 PM, David Pollak <dpp@...> wrote:

Sean McDirmid wrote:

I'm not sure about the licensing implications of that. The source code
for the Java collections is GPLed, and that would definitely count as
a derivative work.

Just put it out under the same license.

Copyright violations are code theft. It's wrong, not matter what the purpose is. Further, if parts of Scala are licensed under the GPL, lift's license becomes incompatible. And it means lots of corporations can't use it.

If RMS wants to sue us, we can burn that bridge when we get to it.

RMS is not the copyright holder, Sun is and they take their IP very, very seriously.

We aren't selling Scala or being commercial in anyway, so I don't see any liability there.

The GPL imposes significant burdens on the licensee. It's not about being open, it's about being free. The GPL means that all other software that's linked to it must also be free.

We just make sure our stuff is as open as the stuff we are copying.

Once again, copyright violation is theft. It's no different than stealing a car. Being part of the FOSS community means respecting that.

David

« Return to Thread: [scala] Collections performance