My team is developing a for-profit (if all goes well!) game, and my UI programmer tracked down your library as a way of making life easier for himself. I've dug through the GPL and LGPL, found some semi-plain english translations, and through it all, haven't come across a satisfactory answer that I'm confident would cover us in a worst-case scenario.
So, since I saw that it says in the GPL that enforcement comes down to the developer of the software in question... If we were to go ahead and use xWinForms v3.0 in our game, what all would you want included with the distributable?
I'm assuming, from what I'd picked up, that we'd have to keep the library separate so that anyone else can pull it in, and include the GPL and LGPL licenses with it. It -seems- to say that we need to include the source for the library as well (or provide access to it), so it'd seem to me that a link to your page here at SourceForge would be good enough for that. Does this all check out with you, or are there other conditions you'd want to lay onto this?
- Andrew Hruza
(Dammit, Jim, I'm a programmer, not a lawyer!)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If the library is used as is, without any modification to it's source code, a visible link to it's page on SourceForge is just fine with me. But if the library (DLL) is modified in any way you have to make the new code publicly available under the same license as the original.
I hope this helps..
- Eric Grossinger
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi-
My team is developing a for-profit (if all goes well!) game, and my UI programmer tracked down your library as a way of making life easier for himself. I've dug through the GPL and LGPL, found some semi-plain english translations, and through it all, haven't come across a satisfactory answer that I'm confident would cover us in a worst-case scenario.
So, since I saw that it says in the GPL that enforcement comes down to the developer of the software in question... If we were to go ahead and use xWinForms v3.0 in our game, what all would you want included with the distributable?
I'm assuming, from what I'd picked up, that we'd have to keep the library separate so that anyone else can pull it in, and include the GPL and LGPL licenses with it. It -seems- to say that we need to include the source for the library as well (or provide access to it), so it'd seem to me that a link to your page here at SourceForge would be good enough for that. Does this all check out with you, or are there other conditions you'd want to lay onto this?
- Andrew Hruza
(Dammit, Jim, I'm a programmer, not a lawyer!)
Hi Andrew,
If the library is used as is, without any modification to it's source code, a visible link to it's page on SourceForge is just fine with me. But if the library (DLL) is modified in any way you have to make the new code publicly available under the same license as the original.
I hope this helps..
- Eric Grossinger