public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: New Project: Bug Cleaners
Date: Sun, 17 Nov 2013 04:40:22 -0600	[thread overview]
Message-ID: <20131117044022.53efe9b4@caribou.gateway.pace.com> (raw)
In-Reply-To: 20131116121601.30f7f202@TOMWIJ-GENTOO

[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      parent reply	other threads:[~2013-11-17 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16 11:16 [gentoo-dev] RFC: New Project: Bug Cleaners Tom Wijsman
2013-11-16 17:05 ` Damien Levac
2013-11-17 10:40 ` Ryan Hill [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131117044022.53efe9b4@caribou.gateway.pace.com \
    --to=dirtyepic@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox