On Mar 2, 2010, at 22:12 , Fritz Zaucker wrote:
> On Tue, 2 Mar 2010, Raul Gutierrez Segales wrote:
>
>> Hi Jean,
>> On Tue, 2010-03-02 at 15:27 +0100, Jean-Baptiste BRIAUD -- Novlog wrote:
>>> Hi
>>> First of all, congratulation for your application. It was difficult to
>>> understand the meaning as I didn't got the English messages, but I walk
>>> throw the app and it's great.
>>> One remark about the hourglass. why not showing it in the building window
>>> itself ? This would allow more fluid workflow for the user instead of
>>> blocking the main "start menu".
>>> Now a question : does GPL allow us to copy/paste some of your code in our
>>> code ? I'm not talking about reusing the project itself or a "binary"
>>> module, but some piece of code. After that copy/paste, no link would be
>>> maintained.
>>
>> Please, help yourself :) I would really like to package some of our high
>> level widgets (for example the listing window - used to list/add/delete
>> different entities) so they could be reusable in other projects.
>> Cheers, Raúl
>> P.S.: strictly speaking, I think the GPL says you should do some type of
>> reference to the original source.. But I never quite understood how do
>> derivative works really work.
>
> I think GPL implies that the program using your code must give the reference
> including the GPL license description and also implies that when the program
> is being distributed (sold or otherwise) must include the source of the
> program as well. But there are certainly people more knowledgable about
> licensing issues than I ...
>
> Anyway, if you really want to allow cut/paste without any strings attached,
> you'd have to put your code under some other licensing model.
>
> Cheers,
> Fritz
>
> P.S.: LGPL might better fit your intentions.
>
Yes, that's exactly the point. If I cut/paste some code, I have to license my
own code with GPL.
GPL is like glue.
GPL also force to report any modification done on the "included" GPL code.
I'm not sure if including under GPL term mean cut/paste of source code or some
library linkage.
LGPL allow more freedom, so my question would be more precise :
* would you mind licensing your code under other license than GPL ?
* or would you mind give us a "special" license ?
To let you have a clear and complete vision for the decision, I have to let
know we will not put all our code in open source.
Only some technical module will be open source. For example, we are about (a
question of hour now) to release a Java RPC for qooxdoo in open source.
The "business" code on top of that tech lib won't be open source and are own by
our customer.
Feel free to have a look at www.novlog.com
Hope all that is not too confusing :-)
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
