Hi Damian,
> The use of AGPL means that your OpenJPEG fork will not be used for > commercial projects and any enhancements you make will not make there way > into OpenJPEG. > Correct. > > You may have a good reason for choosing this licence and as such it is > your choice. > Yes. > > Either way good luck. > Thank you. Cheers, Aaron > > > On 3 February 2016 at 19:28, Aaron Boxer <[email protected]> wrote: > >> Dear GDAL Developers, >> >> I am developing a new open source JPEG 2000 toolkit, based on OpenJPEG. >> >> It is a drop-in replacement for OpenJPEG, but features: >> >> - fast precinct-level decode >> - lower memory usage >> - better performance - currently it is roughly 1/3 the perf of Kakadu, >> (tested on windows), and I am hoping to get it down to around 1/2 >> >> I was originally hoping to merge these changes into OpenJPEG. For a >> number of reasons, I decided to start a new project instead. One of my >> main motivations is the fact that OpenJPEG is a reference implementation, >> designed for correctness and portability. My main interest is performance. >> >> I have ported the code to C++14, so developers get access to all of the >> modern C++ goodness such as class hierarchies, lambdas, threading library, >> exceptions, standard template library, etc. >> >> Gone is support for older compilers, including VS 2010. >> >> The code is licensed under the AGPL, to ensure that all code >> modifications get contributed back to the community. >> >> It you find this useful, please visit >> >> https://github.com/GrokImageCompression/ronin >> >> For those who need a more permissive license, or who prefer using the >> reference implementation, there is always good old OpenJPEG. >> >> Kind Regards, >> Aaron >> >> >> >> _______________________________________________ >> gdal-dev mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/gdal-dev >> > >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
