<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>I don't think the community will let exiv2 disappear. There are too many good projects that use exiv2, e.g. digiKam and darktable.</div><div><br></div><div>At the same time I don't believe exiv2 will ever support video files well. Metadata of still images and metadata of video files are just way too different. </div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Gilles Caulier <caulier.gilles@gmail.com> </div><div>Date: 2017-04-09 3:11 PM (GMT-07:00) </div><div>To: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users@kde.org> </div><div>Subject: Re: Exiv2 bug reports </div><div><br></div></div><div dir="ltr">Robin talk about Andreas, the original author of Exiv2. He is a very good developer. I meet him in the real life, through a digiKam developer reunion.<div><br></div><div>For a work opportunity, he is less and less available to maintain Exiv2 since few years now. Robin take the role of manager as well, but i suspect that the communication is not perfect between both. Robin management is special, and personalty, i don't like how he communicate with the team members the other client project using Exiv2.</div><div><br></div><div>But this is just my viewpoint.</div><div><br></div><div>Gilles Caulier</div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-04-09 22:58 GMT+02:00 Simon Frei <span dir="ltr"><<a href="mailto:freisim93@gmail.com" target="_blank">freisim93@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Take it slowly. We don't know the history behind all this (at least<br>
that's the impression I get from the votes so far).<br>
The way I interpret that post is, that there is a founder or other kind<br>
of leader that is only partially involved in maintaining exiv2, but has<br>
all the keys to the infrastructure in his hand. This needs to be somehow<br>
resolved between this person and the people doing the heavy lifting on<br>
the code.<br>
Calling for taking over exiv2 either as a fork or integrating in digiKam<br>
(very bad option in my opinion) is certainly not a good idea. The core<br>
team working on digiKam is doing a great job, but certainly has enough<br>
on its plate as it stands. digiKam isn't the only software to use exiv2,<br>
so going ahead unilateral is anyway inpractical.<br>
<div class="HOEnZb"><div class="h5"><br>
On 09/04/17 22:50, jdd wrote:<br>
> Le 09/04/2017 à 22:44, Gilles Caulier a écrit :<br>
>> A fork is a possibility. Typically, i proposed to the rest of the team<br>
>> to directly integrate Exiv2 core somewhere in digiKam core, with some<br>
>> part removed that we don't use, as ssh and web support.<br>
>><br>
>> Forking Exiv2 will be not simple to maintain. Even if all the image<br>
>> support is well implemented in Exiv2, there are always tags list to<br>
>> improve. For the video support a lots of code need to be review and<br>
>> stabilized. So, it's a long work to do, and we have also a lots of bugs<br>
>> to fix in digiKam.<br>
>><br>
>> So the decision is not simple to take. I'm shared...<br>
>><br>
><br>
> reading the post it looks like the author is ready to do the task, may<br>
> be needs only support and infrastructure?<br>
><br>
> did you contact him directly?<br>
><br>
> sorry, I'm in no way able to help you on programming :-(<br>
><br>
> jdd<br>
><br>
<br>
<br>
</div></div></blockquote></div><br></div>
</body></html>