muon bug reports

[Harald Sitter]

I honestly don't know, Carlo did do some changes, also in the
underlying libqapt. I haven't used muon in at least half a decade, but
from what I recall it definitely was complete. Of course at the same
time it's a massively feature rich app so there's bound to be problems
and that's what those bugs are by the looks of it. Specifically half
look like weird problems elsewhere that simply happen to manifest in
muon, a quarter are legit issues in weird scenarios and the other
quarter are wishlist items. The more concerning bit is libqapt WRT
maintenance. libapt-pkg does change ABI every once in a while and if
informed porting to the new API doesn't happen then that's bound to
bit rot through uninformed hodgepodge porting eventually.

That being said, if nobody wants to maintain muon I'm fine with sunsetting it.
Equally I'm fine with sunsetting libqapt but as I recall some of the
l10n support tech depends on it (via libkubuntu).

On Fri, Aug 7, 2020 at 3:29 PM Nate Graham <nate at kde.org> wrote:
>
> Is Muon itself still developed at all? From what I can see it has had
> only one substantive commit [1] in the last two years. The rest are
> translations, appdata changes, etc. The bug tracker has tons of bugs [2]
> so it's not as if it's a mature and finished app without the need for
> much development.
>
> Nate
>
> [1]
> https://invent.kde.org/system/muon/-/commit/8453986756bfad695e318c9c147ec55c0b666d06
> [2]
> https://bugs.kde.org/buglist.cgi?component=muon&list_id=1777549&product=muon&resolution=---
>
>
>
> On 8/7/20 4:25 AM, Harald Sitter wrote:
> > elo
> >
> > muon bugs on bugs.kde.org get default assigned to
> > echidnaman at kubuntu.org but I'm sure he's not done any development in
> > years so I would rather change it to something else. any preferences?
> > a mailing list ideally.
> >
> > HS
> >