Hi Nyall, Well, my point is that it's not terribly difficult to make a contribution, but it does require some hard work, which few are willing to expend. But, this isn't specific to JPEG 2000 - it's the case for any FLOSS project. The JPEG 2000 standard is difficult, but it can be grokked, if I may use that expression, after a few months of study and consulting with existing developers. I received quite a bit of help from one of the JPEG committee members when I was getting started, and I would be happy to answer questions about the standard, except none have been asked so far :)
Cheers, Aaron On Sun, Feb 28, 2021 at 6:03 PM Nyall Dawson <nyall.daw...@gmail.com> wrote: > Hi Aaron! > > I'm honestly a little confused reading your reply, as it seems to > contradict itself: > > > As for the scarcity of open source expertise along with JPEG 2000, I > also agree. But the bar to entry > > isn't as high as it used to be - we have high-quality open source > implementations, so anyone > > who wants to spend a few months, (or years :) ) reading and re-reading > the big blue JPEG 2000 book > > and looking through the code is welcome to do so -it's not that tough. > They should then be able to contribute. > > if they have the time and interest. > > vs > > > to be honest, I've done 98% of the work on the library over the past 5 > years. > > This is partly just the nature of open source, > > especially for maddeningly complex standards like JPEG 2000. Many have > opinions but few are prepared to roll up their > > sleeves and do the work. > > Doesn't this clearly demonstrate that the available pool of developers > with the expertise required to work on JPEG2000 is extremely small, > and show the pressing need for a coordinated approach to JPEG 2000 > development rather than further fragmentation? > > Nyall >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev