Fwd: KDiff3 maintenance

[Aurélien COUDERC]

Hi,

Le 12/09/2019 à 16:09, Lisandro Damián Nicanor Pérez Meyer a écrit :
> Hi! Replying inline to what Sandro already wrote, I'm switching MUA and I'm kind
> of lost here :-)
> 
> On 19/09/10 01:15, Sandro Knauß wrote:

[…]

>>> I'd be happy if the Debian QT/KDE team could take the responsibility
>>> for KDiff3 (and move it to more modern means of packaging than Eike's
>>> Computer ;) ). I'd be even more happy if I could keep upload rights for it,
>>> but that's second. But, wait...
>>
>> Well this sounds mostly, that you want to move all the work from your 
>> shoulders to ours. Unfortunately our team is not that well staffed... I'm more 
>> thinking about, that we can work together to get kdiff3 package in a better 
>> shape for Debian and manage it together under the team umbrella. Sure the team 
>> umbrella gives other team members the ability to take over easily. 
> 
> We can surely move it to extras and try to team-maintain it there. Maybe even
> file a RFH bug.
> 
>> You didn't used any VCS to manage kdiff3 packaging?
> 
> Indeed, that would be awesome.
> 
>>> But, wait... second would be someone backporting the remedys for the most 
>> imminent crashes of KDiff3 in Buster and "make KDiff3 great again". ;)
>>
>> My workload is already quite high, I won't be able to do backports for kdiff3. 
>> I checked BTS and I even do not see what bugs hit kdiff3, so I can't even see 
>> what issues to address and what needs to be backported.
> 
> Same here but we can certainly try to have it team-maintained. We have new
> people from time to time and maybe this is a nice package for them to work on.

As an new people from time to time, and occasional user of kdiff3 I’m willing to
maintain it. :)
I created a Salsa repo for that:
https://salsa.debian.org/qt-kde-team/extras/kdiff3

> 
> Eike: if you kept the versioning in some VCS, please share it with us (can be a
> tarball somewhere). I'll happily import it into our team's salsa instance.

Indeed, if there was an existing source code repository for the packaging work
it would be useful.
Otherwise I’ll use the current source package and import it into git.


Cheers,
--
Aurélien