Exiv2 bug reports

[Simon Frei]

Take it slowly. We don't know the history behind all this (at least
that's the impression I get from the votes so far).
The way I interpret that post is, that there is a founder or other kind
of leader that is only partially involved in maintaining exiv2, but has
all the keys to the infrastructure in his hand. This needs to be somehow
resolved between this person and the people doing the heavy lifting on
the code.
Calling for taking over exiv2 either as a fork or integrating in digiKam
(very bad option in my opinion) is certainly not a good idea. The core
team working on digiKam is doing a great job, but certainly has enough
on its plate as it stands. digiKam isn't the only software to use exiv2,
so going ahead unilateral is anyway inpractical.

On 09/04/17 22:50, jdd wrote:
> Le 09/04/2017 à 22:44, Gilles Caulier a écrit :
>> A fork is a possibility. Typically, i proposed to the rest of the team
>> to directly integrate Exiv2 core somewhere in digiKam core, with some
>> part removed that we don't use, as ssh and web support.
>>
>> Forking Exiv2 will be not simple to maintain. Even if all the image
>> support is well implemented in Exiv2, there are always tags list to
>> improve. For the video support a lots of code need to be review and
>> stabilized. So, it's a long work to do, and we have also a lots of bugs
>> to fix in digiKam.
>>
>> So the decision is not simple to take. I'm shared...
>>
>
> reading the post it looks like the author is ready to do the task, may
> be needs only support and infrastructure?
>
> did you contact him directly?
>
> sorry, I'm in no way able to help you on programming :-(
>
> jdd
>