Aristedes Maniatis-2 wrote:
>
>> Also an important step would be to switch the license from Apache
>> to LGPL.
>> It seems that the Apache license is not too GUI friendly: just
>> looks how few
>> projects on Apache.org have GUI's and how many good GUI oriented
>> libraries
>> or tools are LGPL.
> ... you could still keep the Apache
> license on the core code. The restriction for including GPL code is
> all about code released by Apache: that is, code which is part of an
> official release.
>
Now thats a very very good point.
Maybe many problems could be simply solved by having "unofficial releases"
(and servers).
E.g. for some projects where LGPL code would be required, to simply have
"officialy" only the "src" release, and the "binary" (with the LGPL jars in
the packege) to be "unofficial" (but still available so that not to force
every user to build).
Thank you,
Demetrios.
-- View this message in context: http://www.nabble.com/DataViews---Proposal---move-to-sourceforge%21-tf4743504.html#a13572628 Sent from the Cayenne - Dev mailing list archive at Nabble.com.
This archive was generated by hypermail 2.0.0 : Sun Nov 04 2007 - 07:55:22 EST