public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keyword request interface (SoC candidate?)
Date: Thu, 28 Feb 2008 21:49:25 -0500	[thread overview]
Message-ID: <47C772B5.9090905@gentoo.org> (raw)
In-Reply-To: <3c32af40802280933n1290c88bn35b2b989de29ce1b@mail.gmail.com>

Santiago M. Mola wrote:
> 
> I've been talking about it with some users and everyone agrees that
> they would like to have such an interface...
> 
> What do you think about? Would it be easy to integrate it with
> packages.g.o or should it belong somewhere else? Do you think this is
> a suitable project for SoC?

I like the idea, although it is a bit redundant with bugzilla.  One 
thing that would be nice is better workflow management.  Right now it 
would be nice as an arch dev to be able to get a list of all stable 
requests that have been checked by an arch tester on my arch - that 
isn't simple now.  We used to keyword bugs STABLE or TESTED but I don't 
think that anybody is doing that any more - and it breaks down when you 
have 7 archs CC'ed on a bug anyway (which one is tested?).

The fundamental issue, though, is that keywording obscure packages is 
not trivial.  I cringe when I see a stable request for some dialup 
networking package - I doubt many devs even own modems these days.

A tool like the one proposed could even raise questions about how more 
obscure packages should be maintained.  Maybe all interested users could 
subscribe to a package and then vote on when they will go stable.  If 
66% of users interested in a package vote that a package is stable then 
a dev would have discretion to just keyword it without any testing at 
all (obviously this would not be done with critical packages, but the 
world isn't going to end if autopano-sift breaks down on some edge 
case).  It also gets users more involved in the QA process and is a 
little less "cathedral" like...
-- 
gentoo-dev@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-02-29  2:49 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 [this message]
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
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=47C772B5.9090905@gentoo.org \
    --to=rich0@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