Hi, >From my side, as long time digiKam coordinator and opens source contributor, Lensfun is a very important piece of software and very popular in users base.
Since we propose digiKam as ready to use bundles for Linux (AppImage), MacOS (package), and Windows (Installers), we inlude as well the Lensfun git/master code since a long time. 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 ! 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. 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. Best Gilles Caulier Le dim. 21 avr. 2019 à 10:24, <m...@sebastiankraft.net> a écrit : > > > > I still don’t see how this can be made in smaller steps. The good > > news is that most of the path to the next release is behind us, at > > least in my estimation. > > Yes, it was necessary to refactor these parts of Lensfun although it > stalled the project for quite some time. In the end we got a much > cleaner codebase. We got rid of a lot of dependencies and proprietary > implementations of code which is now based on standard C++. So the entry > threshold for new contributors hopefully is lowered considerably... > > > > > The goal should be to get a working release, possibly together with > > patches against Darktable to use the new API. It needn’t implement > > all planned things. Just working. Then, we can take a deep breath > > and move on. > > I agree partly, from my perspective the most important thing missing > before a release is to check if the changes of the API make sense in the > context on applications. Ideally, we would get feedback from the app > programmers what they need so we can avoid further tweaking the API in > the next versions. The API should be stabilised as soon as possible. > Maintaining compatibility throughout API changes is a nightmare in an > open source libary and already is in Lensfun. And it is also a problem > for the app programmers. > > > > > > > Help is welcome, especially senseful in the following areas: > > > > [...] > > I have added a milestone to GitHub to track what I think is still to be > done: https://github.com/lensfun/lensfun/milestone/1 > > Feel free to add more items or edit and work on the exsiting ones! > > Sebastian > > > _______________________________________________ > Lensfun-users mailing list > Lensfun-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lensfun-users >
_______________________________________________ Lensfun-users mailing list Lensfun-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lensfun-users
