From: Erik K. <eri...@gm...> - 2007-02-02 20:05:09
|
On Friday, February 02, 2007 at 10:42, rog...@ro... wrote: > 1. Continue to support development of PanoTools as an open source effort > 2. Provide commercial developers a reasonable option to share the > benefits of PanoTools while contributing something back to the core > effort, either through funding or code sharing > 3. Prevent forking PanoTools > 4. Create the incentive to formalize an organization designed to > protect and promote PanoTools IP What about the following details: 1. Provide a core library that is intended as a pano stitching engine (similar to an operating system) where well defined system calls can be made. This library could be dual licensed, LGPLed or something else. Ideally it would be interface compatible to pano12. This library would be the basis for both open source and commercial programs. 2. Put the new projections into a separate program or a separate library that is GPL. 3. Put the new programs PTMender, PTOptimizer, PTBlender etc. under GPL. This way it would be possible to avoid the fork of the library and the GPL would apply to most of the new code. And there would be no licensing issue with the plugins... Unfortunately I don't know whether this is possible technically and what it implies... best regards -- Erik Krause Resources, not only for panorama creation: http://www.erik-krause.de/ |