Exiv2 bug reports

[Gilles Caulier]

There is something that i don't understand well...

If the release depend only of the credential of Exiv2.org web site, there
is only a right access to the website to only post and register the new
release as well.

Releasing source code has nothing to do with a website !

For me it's a wrong problem :

1/ release the source code
2/ post the announcement

If 2/ cannot be done due to lack of credential, create a new web site as
well.

But as i already recommended to Robin, the source code is the big priority.
I have a big exprience in open source, i know Exiv2 source code also to
have already contributed, and this is the main goal. Fix the problems with
client applications :

1/ list all main problems
2/ order by priority
3/ fix step by step.
4/ release more frequently the library (not all the 2 years, but all 6
month)

I already talk with Robin about this topic. The feedback was been
catastrophic. To resume : digiKam project is the heel and badly manged and
implemented.

This is why, for now, you can forget to talk about Exiv2 project to me...

I seriously plan Exiftool migration. It will take a while but at least
Exiftool is alive and constructive... I'm in contact with Exiftool team...

Voilà. This is just the viewpoint from an human who code a little bit at
free time...

Gilles Caulier



2017-04-25 8:39 GMT+02:00 NeiNei <neinei at gmx.net>:

> Dear all,
> in addition to Pat's mail, Robin Mill made a new posting on the future of
> exiv 2 a few hours ago: http://dev.exiv2.org/boards/3/topics/2830
> As Pat noted, it seems that we still have to keep our fingers crossed.
>
> NeiNei
>
> On 25.04.2017 03:00, Pat David wrote:
>
>> All,
>>
>> I've been in touch with Robin about this, and in fact we have a
>> presentation at LGM this past weekend together.
>>
>> He and Andreas have come to hopefully resolve the problems, and he
>> expects to have a release out as soon as possible (the GIMP team is also
>> watching this).
>>
>> Robin is also planning on moving away from the project at the end of the
>> year to go back to school, so he is actively looking for a new engineer
>> to transition into the project and continue the work. It might be worth
>> holding off for a little bit to see if releases start coming. I
>> understand that the work is done on 27, it's just awaiting Andreas to be
>> released, which should be soon (fingers crossed).
>>
>> Pat
>> On Mon, Apr 24, 2017 at 3:33 PM Jim Gomi <gomi at mailup.net
>> <mailto:gomi at mailup.net>> wrote:
>>
>>     On Sun, 2017-04-09 at 12:37 -0600, aegoreev at gmail.com
>>     <mailto:aegoreev at gmail.com> wrote:
>>     > I think we need to leave exiv2 as is for still images and find
>>     > something else for video files if possible...
>>
>>     I agree with this. For me the biggest problem with digikam is that I
>>     cannot store metadata inside video files.
>>     The digikam4.db database file is good but from experience I know that
>>     it can get corrupted and I relied on the image file metadata to
>> restore
>>     it.
>>
>>     > Once we know what we want to do for video files I can volunteer and
>>     > check every single tool availble on the web and come up with some
>>     > kind of report.
>>
>>     That would be great.
>>
>> --
>> https://patdavid.net
>> GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170425/1c5c0548/attachment.html>