From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: bug-wrangling (was: [warning] the bug queue has 111 bugs)
Date: Fri, 17 Apr 2015 13:53:28 -0400 [thread overview]
Message-ID: <55314898.1050903@gentoo.org> (raw)
In-Reply-To: <5531312fdf90a_687012d52fc0@TP_L520.notmuch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 17/04/15 12:13 PM, Franz Fellner wrote:
> Alex Alexander wrote:
>> Our bug queue has 111 bugs!
>>
>> If you have some spare time, please help assign/sort a few bugs.
>>
>> To view the bug queue, click here: http://bit.ly/m8PQS5
>>
>> Thanks!
>>
>
> Is there something non-devs could do? Would it be OK to just CC
> HERD mail from epkginfo (as I am not allowed to reassign). Because
> I at least once a day browse the bug database and could at least CC
> some of the new bugs.
>
A few years before I became I dev, I did a short stint as a
bug-wrangler -- iirc all you need to do is train yourself via the
bug-wrangling guide and find someone to vouch for you in order to
obtain write-access to bugzilla. I don't know who you would talk to
about this right now (NP-Hardass maybe??) but I'm sure that we could
use the help, if you wanted to lend a hand.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlUxSJgACgkQ2ugaI38ACPCQJwD9HCxFXXsnUXR5WU3dHBsvO93Z
v7u2nzotdNAREAOBRekBAKRpu8xdSfxeE5GIBF0KOEGBqNMZ3Mtl2jjluN7EQZfs
=qR8R
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-04-17 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 21:00 [gentoo-dev] [warning] the bug queue has 111 bugs Alex Alexander
2015-04-17 16:13 ` Franz Fellner
2015-04-17 17:53 ` Ian Stakenvicius [this message]
2015-04-19 6:59 ` [gentoo-dev] Re: bug-wrangling (was: [warning] the bug queue has 111 bugs) Franz Fellner
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=55314898.1050903@gentoo.org \
--to=axs@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