From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for June
Date: Mon, 02 Jun 2008 16:43:51 +0200 [thread overview]
Message-ID: <48440727.9050403@gentoo.org> (raw)
In-Reply-To: <3c32af40806020405j62502e1ag1f8aa5e21b72b919@mail.gmail.com>
Santiago M. Mola wrote:
> I think we have not enough feedback from users about this. Either
> Bugzilla is not the right tool, or we don't encourage users enough to
> ask for keywords when they need them. Currently, some people assume
> that "if a user from $arch needed this package, he'd have requested
> keywords", but that's wrong.
Good point and probably a good start to find a decent solution about
getting the stuff needed by user keyworded but not overwork arch teams.
Probably having 2-4 lines about this in the next newsletter could foster
awareness.
Having a smarter repoman and bugzilla integration to handle
stabilization and keyword bugs automagically would be great but I think
would require time (since such bugs could spare the dev some trips
around bugzie)
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-02 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 5:30 [gentoo-dev] Monthly Gentoo Council Reminder for June Mike Frysinger
2008-06-01 9:36 ` Alec Warner
2008-06-01 12:25 ` Mart Raudsepp
2008-06-01 17:41 ` Raúl Porcel
2008-06-01 21:54 ` [gentoo-dev] " Ryan Hill
2008-06-02 3:30 ` Richard Freeman
2008-06-02 12:21 ` Alec Warner
2008-06-02 9:18 ` Raúl Porcel
2008-06-02 11:05 ` Santiago M. Mola
2008-06-02 14:43 ` Luca Barbato [this message]
2008-06-03 15:54 ` Christian Faulhammer
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=48440727.9050403@gentoo.org \
--to=lu_zero@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