[kde-community] retiring unmaintained modules?

[Myriam Schweingruber]

On Sun, Jan 11, 2015 at 12:17 AM, Albert Astals Cid <aacid at kde.org> wrote:

> El Diumenge, 11 de gener de 2015, a les 00:10:15, Jaroslaw Staniek va
> escriure:
> > On 11 January 2015 at 00:00, Albert Astals Cid <aacid at kde.org> wrote:
> > > El Dissabte, 10 de gener de 2015, a les 23:37:30, Rick Timmis va
> escriure:
> > >> Hi
> > >>
> > >> Text idea below
> > >>
> > >> On Sat, 10 Jan 2015 23:13:20 +0100, Albert Astals Cid <aacid at kde.org>
> > >>
> > >> wrote:
> > >> > El Dissabte, 10 de gener de 2015, a les 22:56:06, Boudewijn Rempt va
> > >> >
> > >> > escriure:
> > >> >> On Sat, 10 Jan 2015, Albert Astals Cid wrote:
> > >> >> > Some of them like kword and koffice are already in unmaintained
> and
> > >> >> > closed
> > >> >> > for bugs, not much more we can do with them other than deleting
> them
> > >> >> > which i'm not sure it's a good idea.
> > >> >>
> > >> >> Close the bugs as "unmaintained"? There's no reason to keep bugs
> open
> > >>
> > >> for
> > >>
> > >> >> dead projects.
> > >> >
> > >> > In an ideal world you'd have biliions of bug triagers that would go
> > >> > through
> > >> > all the open bugs and move the ones that still exist to calligra for
> > >> > example
> > >> > (meaning i think there's still some sense to keep them there)
> > >> >
> > >> >> > Others like kftpgrabber may be either suggested for new people to
> > >>
> > >> adopt
> > >>
> > >> >> > them and if not moved to unmaintained.
> > >> >>
> > >> >> I don't believe in that -- asking for maintainers never works. It's
> > >> >> vanishingly rare that an unmaintained project gets a new lease of
> > >> >> life,
> > >> >> and it never happens if there's no maintainer around anymore to
> answer
> > >> >> questions.
> > >> >
> > >> > I don't believe in things you belieave and vice-versa ;)
> > >> >
> > >> >> > I guess we should also be really careful, as you said some
> software
> > >>
> > >> is
> > >>
> > >> >> > "done" and the fact that it didn't get any development doesn't
> mean
> > >>
> > >> it
> > >>
> > >> >> > should be killed.
> > >> >>
> > >> >> Of course. But kmail (not kmail2) is _dead_. It's bugs should be
> > >>
> > >> closed.
> > >>
> > >> >> It's silly to see it cluttering up bugzilla's weekly top-twenty
> stats.
> > >> >
> > >> > Same as before, ideally we'd have someone going over the bugs and
> > >>
> > >> deciding
> > >>
> > >> > what still happens and what still not and move over to kmail2.
> > >> >
> > >> > Now one way of doing this is crowdsourcing it to the reporters via a
> > >>
> > >> nice
> > >>
> > >> > bug
> > >> > closing email for every of the unmaintained bugs/apps.
> > >> >
> > >> > In one hand it always pisses me a bit off when that happens (i.e. i
> > >> > reported a
> > >> > bug and the only acknowledgement i get is years later saying that it
> > >> > was
> > >> >
> > >> > against an unmaintained version that i should re-check), in the
> other
> > >> > if
> > >> >
> > >> > someone is able to write a nice text it may not be so bad.
> > >>
> > >> I like this idea... possible text
> > >
> > > It's nice. We would need another version for those bugs that belong to
> > > products that have other products the bug may apply to, say kmail ->
> > > kmail2, kword -> calligrawords, etc.
> >
> > When Calligra appeared bugs have been copied from KOffice for
> > duplicated apps -- IIRC. Or not?
>
> Maybe for calligra, but for kmail? or for kghostview, kpdf -> okular?
>

Last time I was trying to close the kmail 1 bugs as unmaintained, asking
people to reopen if it stilkl applies to kmail2 I was shouted at and told
that somebody has to check if that still applies to Kmail2 before closing,
go figure! I just fear that with 880 open reports this is never going to
happen...

Regards,
Myriam

-- 
Proud member of the Amarok and KDE Community
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20150111/e4f7f975/attachment.htm>