Re: [kde-community] retiring unmaintained modules?
On 11 January 2015 at 00:17, Albert Astals Cid 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 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 >> >> >> >> 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? > > I think it's still nice to have that text. Yes, No doubt here. So I think we have things sorted out for KOffice products: we don't need to keep them if there are copies already. There were no public releases of KOffice apps after the fork, IIRC. So it can be maybe checked using some query if there are valuable bugs/wishes reported for KOffice products after the fork, either by users who had KOffice installed before or installed it after Calligra was available (installed for any reason, including mistake). I am not too motivated to do that since Kexi and Krita are among apps that are not duplicated. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
On Sun, Jan 11, 2015 at 11:13 AM, Albert Astals Cid 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. > > Anyway before someone does some mass closing of bugs I think we need to take > sysadmins adivce on how to do it, not sure we want to create a huge e.mail > storm. The only way we'd be able to do this is by sending out the emails, otherwise people are unlikely to react to the change as they won't know. I'd recommend starting with one or two smaller products which are maintained but have been forked/duplicated/etc and moving onward from there. Also, as users don't have the ability to reassign bugs to different components, triagers will need to be available to respond to users who do respond to our request to reproduce the issue. > > Cheers, > Albert Regards, Ben > >> >> boudewijn >> ___ >> kde-community mailing list >> kde-community@kde.org >> https://mail.kde.org/mailman/listinfo/kde-community > > ___ > kde-community mailing list > kde-community@kde.org > https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
On Sun, Jan 11, 2015 at 12:17 AM, Albert Astals Cid 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 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 > > >> > > >> 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) ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
On Sun, Jan 11, 2015 at 12:17 PM, Albert Astals Cid 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 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 >> >> >> >> 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? > > I think it's still nice to have that text. Yes, the duplication was only done for Calligra so the text would be necessary for all the other bugs. > > Cheers, > Albert Regards, Ben > > ___ > kde-community mailing list > kde-community@kde.org > https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
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 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 > >> > >> 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? I think it's still nice to have that text. Cheers, Albert ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
On Sun, Jan 11, 2015 at 12:10 PM, Jaroslaw Staniek wrote: > On 11 January 2015 at 00:00, Albert Astals Cid 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 >>> >>> 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? I believe bugs were duplicated - at least to a certain extent. Not sure on the specifics of what was done here though. Thanks, Ben > > > -- > regards, Jaroslaw Staniek > > KDE: > : A world-wide network of software engineers, artists, writers, translators > : and facilitators committed to Free Software development - http://kde.org > Calligra Suite: > : A graphic art and office suite - http://calligra.org > Kexi: > : A visual database apps builder - http://calligra.org/kexi > Qt Certified Specialist: > : http://www.linkedin.com/in/jstaniek > ___ > kde-community mailing list > kde-community@kde.org > https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
On 11 January 2015 at 00:00, Albert Astals Cid 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 >> >> 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? -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
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
>
> 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.
Cheers,
Albert
>
> Hi, Thank you for you contribution towards improving the KDE software
> suite.
>
> Bug reports from active users, merit the highest level of software testing
> because
> your use cases are real world, and not prescriptive.
>
> The lifecycle of individual applications varies as projects develop and
> stabilise, are superceeded or
> simply become unmaintained. Active bug reporting, checking and triaging is
> vital to an application project
>
> In the case of your bug report { insert bug number, perhaps with link }
> this project is no longer maintained
> and there for we can not progress this bug further. We have now closed
> this bug with status unmaintained.
>
> Thanks again for your contribution and support
>
> Best Wishes
> The KDE Bug Tracking team
>
> Just an initial idea, I hope it's helpful
>
> Cheers
> Rick
>
> > Anyway before someone does some mass closing of bugs I think we need to
> > take
> > sysadmins adivce on how to do it, not sure we want to create a huge
>
> e.mail
>
> > storm.
> >
> > Cheers,
> >
> > Albert
> >>
> >> boudewijn
> >> ___
> >> kde-community mailing list
> >> kde-community@kde.org
> >> https://mail.kde.org/mailman/listinfo/kde-community
> >
> > ___
> > kde-community mailing list
> > kde-community@kde.org
> > https://mail.kde.org/mailman/listinfo/kde-community
>
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
Hi
Text idea below
On Sat, 10 Jan 2015 23:13:20 +0100, Albert Astals Cid
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
Hi, Thank you for you contribution towards improving the KDE software
suite.
Bug reports from active users, merit the highest level of software testing
because
your use cases are real world, and not prescriptive.
The lifecycle of individual applications varies as projects develop and
stabilise, are superceeded or
simply become unmaintained. Active bug reporting, checking and triaging is
vital to an application project
In the case of your bug report { insert bug number, perhaps with link }
this project is no longer maintained
and there for we can not progress this bug further. We have now closed
this bug with status unmaintained.
Thanks again for your contribution and support
Best Wishes
The KDE Bug Tracking team
Just an initial idea, I hope it's helpful
Cheers
Rick
>
> Anyway before someone does some mass closing of bugs I think we need to
> take
> sysadmins adivce on how to do it, not sure we want to create a huge
e.mail
> storm.
>
> Cheers,
> Albert
>
>>
>> boudewijn
>> ___
>> kde-community mailing list
>> kde-community@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-community
>
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
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. Anyway before someone does some mass closing of bugs I think we need to take sysadmins adivce on how to do it, not sure we want to create a huge e.mail storm. Cheers, Albert > > boudewijn > ___ > kde-community mailing list > kde-community@kde.org > https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
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. 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 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. boudewijn ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
El Dissabte, 10 de gener de 2015, a les 15:44:20, Boudewijn Rempt va escriure: > On Sat, 10 Jan 2015, Lydia Pintscher wrote: > > On Tue, Jan 6, 2015 at 11:31 PM, Albert Astals Cid wrote: > >> It also says > >> > >> "Whenever an application has not received a commit for one complete year, > >> you will be contacted via email to discuss if you want to continue the > >> application or if it has died. In the latter case or when the email > >> bounces, it will be moved to /tag/unmaintained/N/. " > >> > >> On the other hand this is in the "The start" section so it can be argued > >> if it applies to only playground/ or to everything. > >> > >> It's a similar-ish condition to the one you suggested. > > > > Anyone up for making a list of projects that fit the criteria so we > > can see which projects we're talking about? > > I checked quickgit, and judging by commits, and disregarding scripty > commits, there are 191 candidates. See attached file. Of course, some of > these projects aren't really dead, they are just finished, I didn't go > through them to check that out. > > Judging by bugs is a bit harder, it needs a query on bugzilla, but from > the top-100, these are all pretty dead, it seems. > > kword 124 0 0 0 > kftpgrabber 80 0 0 0 > KMail Mobile 77 0 0 0 > koffice 66 0 0 0 > kuickshow 62 0 0 0 > quanta123 0 -1 -1 > kmail 880 0 -7 -7 > kcontrol 164 0 -38 -38 What do you suggest doing with those? 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. Others like kftpgrabber may be either suggested for new people to adopt them and if not moved to unmaintained. 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. Cheers, Albert > > Boudewijn ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
On Sat, 10 Jan 2015, Lydia Pintscher wrote: On Tue, Jan 6, 2015 at 11:31 PM, Albert Astals Cid wrote: It also says "Whenever an application has not received a commit for one complete year, you will be contacted via email to discuss if you want to continue the application or if it has died. In the latter case or when the email bounces, it will be moved to /tag/unmaintained/N/. " On the other hand this is in the "The start" section so it can be argued if it applies to only playground/ or to everything. It's a similar-ish condition to the one you suggested. Anyone up for making a list of projects that fit the criteria so we can see which projects we're talking about? I checked quickgit, and judging by commits, and disregarding scripty commits, there are 191 candidates. See attached file. Of course, some of these projects aren't really dead, they are just finished, I didn't go through them to check that out. Judging by bugs is a bit harder, it needs a query on bugzilla, but from the top-100, these are all pretty dead, it seems. kword 124 0 0 0 kftpgrabber 80 0 0 0 KMail Mobile77 0 0 0 koffice 66 0 0 0 kuickshow 62 0 0 0 quanta 123 0 -1 -1 kmail 880 0 -7 -7 kcontrol164 0 -38 -38 Boudewijn cutepaste.git Client application for paste.kde.org written in Qt 5 months ago kdev-java.git Java language support for KDevelop4 5 months ago kdev-valgrind.git kdev-valgrind is a plugin offering a full integration of the valgrind suite to KDevelop.5 months ago kdev-xml.gitKDevelop Plugin for XML and HTML Language Support 5 months ago kvkbd.git A virtual keyboard for KDE 5 months ago polkit-qt-1.git Qt wrapper around polkit-1 client libraries, used by kdelibs to provide the polkit-1 kauth backend and by KDE's polkit client. 5 months ago appmenu-runner.git AppMenu runner that allows to quickly find any action exported in AppMenu 5 months ago artikulate-data.git This repository holds the Artikulate course data files. 5 months ago notificationsurvey.git For more information, see http://community.kde.org/Elegance/Notification_Study 5 months ago ksaolaji.gitKSaoLaJi cleans all sorts of waste things in your system. 5 months ago kontaminuti.git Kontaminuti is a simple helper utility to time your activities according to the Pomodoro Technique. 5 months ago abakus.git Abakus is a simple, keyboard-driven calculator. 5 months ago kdisksutilities.git Disks management utilities. 5 months ago cocoon.git A GUI for Git. 5 months ago rekollect.git A rich note-taking application. 5 months ago akonadi-vkontakte.git Makes contacts, notes and messages from VKontakte.ru social network available in KDE. 5 months ago akonadi-google-applets.git Plasma applets for Akonadi google resources 5 months ago akonadi-git-resource.gitAkonadi Git Resource allows you to see your commits in kmail. 5 months ago kwhiteboard.git KWhiteboard is a shared whiteboard application built with Telepathy. It allows you to run a shared whiteboard session with Instant Messaging contacts. 5 months ago ktp-ssh-contact.git Connect to your contacts using ssh 5 months ago ktp-kipi-plugin.git A Kipi Plugin to send images through telepathy 5 months ago kopete-scripting.gitScripting Plugin for Kopete 5 months ago aki.git Extensive IRC client for KDE4. 5 months ago nepomuktvnamer.git A command line tool, service, and desktop action to fetch information about TV Shows from thetvdb.com and store it into Nepomuk. 5 months ago kubeplayer.git A multimedia player for different online platforms. 5 months ago ktutorial.git A library and an editor for interactive tutorials in KDE applications 5 months ago cirkuit.git KDE interface for LaTeX graphic tools (such as TikZ, Gnuplot, Circuit Macros) to produce publication-ready pictures.5 months ago bookmanager.git A simple E-book manager and viewer. 5 months ago ksokoban.gitKSokoban is the Japanese warehouse keeper sokoban game 5 months ago mula.gitMulti Language Dictionary with online, offline dictionary, translation and text-to-speech support. 5 months ago khipu.git *Advanced Mathematical Function Plotter*5 months ago kartesio.gitKartesio is a program for calculating best fit curves with experimental points using regression algorithms or neural networks. 5 months ago kard.gitKard, a Memory-like game for kids 5 months ago conquirere.git h1. Conquirere is
Re: [kde-community] GCompris is now released on Android
On Tue, Jan 6, 2015 at 8:28 PM, Bruno Coudoin wrote: > Hi all, > > I am happy to announce that we published on Google play store the first > public version of GCompris [0]. > > One year ago I took the hard decision to fully rewrite GCompris in QtQuick > in order to address tablet users while keeping PC compatibility. As you > imagine it's a daunting task and something for sure I could not do alone. > Thanks to the help of the many contributors who joined the project we have > been able to port 86 activities of the 140 of the legacy version in a year. > You can look at this page [1] to see the status of the port. We can hope to > complete the port in one more year. The new version is far from perfect and > we continue to polish it everyday but we already provide a better user > experience than the legacy version. > > I would like to take this opportunity to thanks the KDE community at large > who took us under its cute umbrella and allowed us to attract numerous > contributors, developers, translators and provided us development support. > > Some numbers, within a year GCompris had 1211 commits made by 19 > contributors representing 34000 lines of code plus the 8 KDE translation > teams who reached 100% (Ukrainian, Swedish, Portuguese, Polish, French, > Dutch, Chinese Traditional and Brazilian Portuguese). > > As you will see, thefullAndroid version is sold for 6€ now but the price > will have to be adjusted to find the optimal one. Software development is a > lot of work, paying for GCompris is a good way to reward us and give us the > opportunity to sustain the development on our beloved project. Another very > easy way to help us is to share the news and rate us on Google play. > > I don't like the idea of selling GCompris to free software contributors and > thus you can download an unlocked version from [2]. You will only miss the > automatic update feature. By the way if someone wantsto help us distribute > GCompris through f-droid.org you'rewelcome. Congratulations on this milestone, Bruno and team! It's great to see this. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher KDE e.V. Board of Directors / KDE Community Working Group http://kde.org - http://open-advice.org ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] retiring unmaintained modules?
On Tue, Jan 6, 2015 at 11:31 PM, Albert Astals Cid wrote: > It also says > > "Whenever an application has not received a commit for one complete year, you > will be contacted via email to discuss if you want to continue the application > or if it has died. In the latter case or when the email bounces, it will be > moved to /tag/unmaintained/N/. " > > On the other hand this is in the "The start" section so it can be argued if it > applies to only playground/ or to everything. > > It's a similar-ish condition to the one you suggested. Anyone up for making a list of projects that fit the criteria so we can see which projects we're talking about? Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher KDE e.V. Board of Directors / KDE Community Working Group http://kde.org - http://open-advice.org ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
