[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] Re: RFC: New Project: Bug Cleaners
From:       Ryan Hill <dirtyepic () gentoo ! org>
Date:       2013-11-17 10:40:22
Message-ID: 20131117044022.53efe9b4 () caribou ! gateway ! pace ! com
[Download RAW message or body]


On Sat, 16 Nov 2013 12:16:01 +0100
Tom Wijsman <TomWij@gentoo.org> wrote:

> Hello
> 
> This is a request for comments on a new project:
> 
> http://wiki.gentoo.org/wiki/Project:Bug_Cleaners

Sounds like a good idea to me.

>  * When is a bug considered still useful?
> 
>    There are clear cases like a bug that's no longer reproducable and
>    thus clearly doesn't apply; however, there are cases where one might
>    be in doubt (eg. Do people still want it resolved? Do we still want
>    to add a package that stopped its development X years ago?) that
>    might not be so clear cut. I'd like to get clearer borders defined.

I'd like it if maintainer-wanted bugs stayed open.  They often have useful
discussion, ebuilds, patches, etc.  I have one from 2006 that just got pinged
yesterday.  One thing you could do is CC teams that you think might be
interested in the package.

Of course if the project is dead and buried then the bug should just be closed.

>  * Do we need a mail alias so we can get assigned or CC-ed on bugs?
> 
>    This one gets me in doubt, the only case I can come up with is that
>    being able to CC bug-cleaners@gentoo.org allows users to effectively
>    help us out as well by marking bugs they consider old.
> 
>    Another reason might be that we can assign related trackers to it.

Well, once you touch an old bug it won't be old anymore, so you're going to
need some way of keeping track of them.  


-- 
Ryan Hill                        psn: dirtyepic_sk
   gcc-porting/toolchain/wxwidgets @ gentoo.org

47C3 6D62 4864 0E49 8E9E  7F92 ED38 BD49 957A 8463

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]