public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron Mavrinac" <mavrinac@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keyword request interface (SoC candidate?)
Date: Fri, 29 Feb 2008 14:27:13 -0500	[thread overview]
Message-ID: <97a7f0880802291127w283962f3jb4c497f36fcf9649@mail.gmail.com> (raw)
In-Reply-To: <47C84B3C.3080505@gentoo.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1627 bytes --]

On Fri, Feb 29, 2008 at 1:13 PM, Richard Freeman <rich0@gentoo.org> wrote:
> Rémi Cardona wrote:
> >
> > +1 on that idea, using bugzilla with an external tool for keyword
> > requests is a good idea.
> >
> > The tool could do bugzilla research to see if the keyword has already
> > been requested and point the user to the corresponding bug report,
> > hopefully limiting the number of dupes.

Definite ++ here..

> It would still be nice to have better status tracking in bugzilla - some
> way for ATs to officially mark that stuff is tested in a way that can be
> easily queried (so that ATs can find stuff that isn't tested, and devs
> can find stuff that has been).  The issue about hard-to-test packages is
> really a separate one, but one that could use a solution...

This would certainly help coordinate AT efforts. Couldn't this also be
done by searching through bugzilla? Maybe with an "official" keyword,
or some sort of flag we don't otherwise use? (I'm not intensely
familiar with bugzilla internals.) Keeping it all in bugzilla seems
best, if possible.

An additional suggestion: what about some way for ATs to indicate that
they are currently testing a package? Testing can take a while, and
occasionally I've tested packages only to find that someone else had
already taken care of it. Coordinating that on bugzilla or the mailing
list as is would be cumbersome, and IRC is hit or miss. Not sure how
this could be implemented, but that's what a SoCer is for (hey, maybe
me, I'm planning to apply!).

-- 
Aaron Mavrinac
www.mavrinac.com

PGP Public Key: http://www.mavrinac.com/pgp.asc
éí¢‡^¾X¬¶È\x1ežÚ(¢¸&j)bž	b²

  parent reply	other threads:[~2008-02-29 19:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 17:33 [gentoo-dev] Keyword request interface (SoC candidate?) Santiago M. Mola
2008-02-28 17:50 ` Torsten Rehn
2008-02-28 21:43 ` Alec Warner
2008-02-28 21:47   ` Santiago M. Mola
2008-02-29  2:49 ` Richard Freeman
2008-02-29  9:44   ` Peter Volkov
2008-02-29 11:11     ` Rémi Cardona
2008-02-29 18:13       ` Richard Freeman
2008-02-29 18:29         ` Thomas Anderson
2008-02-29 19:27         ` Aaron Mavrinac [this message]
2008-02-29 23:26           ` Richard Freeman
2008-02-29 23:48             ` Aaron Mavrinac
2008-02-29 23:20   ` [OT] " Andrej Kacian
2008-02-29 20:37 ` Bernd Steinhauser
2008-03-01 15:24 ` [gentoo-dev] " Ryan Hill

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=97a7f0880802291127w283962f3jb4c497f36fcf9649@mail.gmail.com \
    --to=mavrinac@gmail.com \
    --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