I recommend in prior to make a release of the library quickly, to push a very important information to the community : the project is alive !
Well, actually it is not really alive. I probably will not do any more bigger contributions or maintenance tasks. Torsten Bronger is having a hard job keeping up with the calibrations. So my message is: If the community wants to keep Lensfun alive, there's a need for 1-2 regular contributors that also develop a vision how Lensfun should evolve. As said in my first post of this thread, there are a lot of challenges regarding release schedules, database updates, compatibility testing and new features that have to be organised and tackled.
The second stage is to migrate quickly the project outside Sourceforge due to the long time criticism of the platform and to migrate to github : the goal is to attract new contributors and use github tools to process unit and regression tests.
That's right and is mostly done now. Source code and website are already migrated. Bug tracker is still missing, though. New bugs and requests should be reported in GitHub. I will prepeare a mailing and news post in the next days.
The next stages are API : let's the current one as well and isolate the part which must be changed. Process step by step use deprecated flags and release the library with changes all the 2/ months. The goal : show to the community that the project is alive again and evolve int the right way with a LTS like.
Yes that's important, but again it needs people to do it :) I couldn't find the time to do it for the last two years and my personal priorities for the next years likely don't allow to spend much time on Lensfun, too.
Sebastian _______________________________________________ Lensfun-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lensfun-users
