Fwd: KDiff3 maintenance

[Lisandro Damián Nicanor Pérez Meyer]

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:
> Hey,
[snip]
> > I've been maintaining the Debian package of KDiff3 for over 15 years now.
>
> thanks a lot for maintaining it for such a long time!

Same here :-)
 
> > It's been low effort in the last years; the original developer didn't do
> > more than some maintenance. But with the imminent removal of KDE 4 from
> > Debian, I moved it to a not-really-ready package by a new developer
> > overtaking and porting it to KF5: https://cgit.kde.org/kdiff3.git
> > Therefore, unfortunately KDiff3 in Buster is not well working.
> 
> It is good to hear, that there is a new active upstream and it is moving 
> again.
> 
> > Meanwhile, in real life, I got father of twins, who eat up all my time
> > and are my priority of course.
> 
> I hope the parts that eats your time are things you enjoy!

And believe me I know, I'm a father of 3 ;-)

> > 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.

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.

**Thanks** For all your work :-)