[Bugsquad] Bugs for unmaintained projects
cgiboudeaux at gmx.com
Wed Apr 22 10:24:35 UTC 2015
On Tuesday 21 April 2015 17:24:35 Myriam Schweingruber wrote:
> Hi Marc,
> On Mon, Apr 20, 2015 at 11:20 PM, Marc Payne <marc321 at gmail.com> wrote:
> > Hey everyone!
> > I just joined the mailing list and am interested in doing some bug
> > triage work. I've read the Guide to Bug Triaging and I have a little
> > experience submitting new reports and commenting on existing ones.
> > Yesterday, I commented on bug 120979 while I was hunting for
> > webdav-related issues. The bug is related to quanta and is very old.
> > In fact, if I understand correctly, quanta is unmaintained now
> > (superseded by KDevelop). There are 239 quanta bugs currently. It
> > seems to me that these should be closed, and this is where I want to
> > start helping out.
> Quanta is closed for new bugs sinced quite some time, but indeed
> commenting on existing bugs is still possible.
> > Is there a standard practice for dealing with unmaintained projects? I
> > am happy to do whatever may be helpful. :)
> Somebody with enough karma would have to close those bugs. Not sure
> that KDevelop really is a replacement for it, as Quanta was very
> specific for web development, while KDevelop is much more generic for
> coding AFAICT. So I wouldn't call that a replacement, as the aims are
> quite different.
"Somebody" would have to ask first the last known maintainer(s) whether there
are reasons to keep these bugs opened.
The people from kdevelop-devel shall know (CC-ed)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: This is a digitally signed message part.
More information about the KDevelop-devel