Re: New 3DS Importer-Exporter and License question

[James W. W. <os...@jw...>]

On Mar 24, 2007, at 5:21 AM, Jose' Cruanyes wrote:

> I'm reading a new 3DS importer-Exporter, built using the lib3ds
> library <http://lib3ds.sf.net>
>
> actually I've got the same functionality that the old 3DSreader, but
> the file is fully parsed, so adding things like colors, normals, uv
> params and so is just a matter of complete the trimesh creation  
> function
>
> from monday I,ll begin creating the exporter, always using the
> lib3ds, and packaged in the same plug-in

Sounds good!

>
> actually is only as Xcode project, Visual Studio project will follow
> soon.
>
> the problem is:
> -lib3ds is released as LPGL, so the new plug-is has to be LPGL too
> -I'd like to release the plug-is as part of Quesa
> 	How about releasing parts with different licenses?

I don't see a problem with that.

> -the new plug-in uses Code of Quesa, part written by me but
> attributed to Quesa, part written by J. Walker as the VRML plug-in
> and attributed to Quesa too
> 	so the authors had to release the code in a new license , for me
> there's not a problem (of course :-)
> 	I need also the J.Walker license...
>
> but, is enough?, having attributted the code to Quesa, may be I need
> permission of more people...

Since LGPL is more restrictive than BSD, I think that would be OK.  I  
have seen some open source code covered by 2 licenses, but I don't  
know if that would be needed.

>
> anyone has any thought?
>
> How about releasing the code as LGPL also (as originary) so anyone
> can choose the most compelling license case, by case)?

You mean all of Quesa as LGPL?  I don't see why anyone would want that.