From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Keyword request interface (SoC candidate?)
Date: Sat, 01 Mar 2008 09:24:36 -0600 [thread overview]
Message-ID: <fqbsg9$t79$1@ger.gmane.org> (raw)
In-Reply-To: <3c32af40802280933n1290c88bn35b2b989de29ce1b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]
Santiago M. Mola wrote:
> A lot of users don't feel comfortable using Bugzilla and often are
> lost with our procedures for keyword (both ~ and stable) requests. I
> think we could use an easy web interface for requesting specific
> keywords for packages in a point-and-click fashion.
Speaking about Bugzilla in general, I think ours could really use a facelift.
When you look at what some other projects have done to make their bug reporting
and tracking interface more user-friendly, it's obvious we have a lot of room
for improvement. I remember back when I first started using Gentoo seeing a
mock-up some dev had done for a bugzilla redesign that was much simpler and
visually appealing, but I can't remember who and I suppose they've probably
retired since. I've always thought it was a shame it never saw implementation.
Anyways, I think this could make a good project for someone in our community
who would like to participate but perhaps is more artistic than technical.
Previous web design work and a good understanding of user interface design would
be required of course. I suppose we should probably ask infra if this is
possible first too. ;)
On keywording/stabilizing, Bugzilla has a flags feature that might be used to
track what has been tested where. For example:
https://bugzilla.mozilla.org/show_bug.cgi?id=12345
Flags have three states: +, -, and ?. + and - are obvious, and ? is a request.
So imagine having a "x86 tested" flag that the maintainer sets to "?" to
request stabilization of their package. An email is sent to the arch alias
notifying them of the request. The arch tester tests it out and sets the flag
to + or - depending on their results. The arch dev stabilizes the package as
normal.
If we added a "Keyword/Stable Request" component to the "Gentoo Linux" product
we could also have it dependent on that, so only bugs in that component would
display the flags. We can also make it so only people with editbugs privileges
and request or set flags.
http://www.bugzilla.org/docs/2.22/html/flags-overview.html
Again, this would require infra to be on board.
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwindows @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-03-01 15:25 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
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 ` 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='fqbsg9$t79$1@ger.gmane.org' \
--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