Hi TJ,
My real-world job changed on the 1st December 2011 (I moved company),
and Bugzilla is no longer part of my day-to-day role, but I guess I
still remember most of what I knew! If I can be of assistance I'd be
pleased to help.
My bugzilla ID is thegur...@openoffice.org.
Regards, Dave.
On 13/01/12 10:19, tj wrote:
Hi, David,
Per below, Rob is going to push this. If you're still interested, it
would be *very* nice to have an admin like you, who knows what to do
and how to do it. --/tj/
-------- Original Message --------
Subject: Seeking Bugzilla Admin Volunteers
Date: Thu, 12 Jan 2012 14:16:31 -0500
From: Rob Weir <robw...@apache.org>
Reply-To: ooo-dev@incubator.apache.org
To: ooo-dev@incubator.apache.org
As far as I have been able to determine, no one in the project seems
to have the ability to do anything in our Bugzilla instance beyond the
basic operations that any member of the public is able to do. We
need to get a handful of people to have some elevated permissions to
edit bugs, edit components, etc., so we can manage the quality process
for the upcoming 3.4 release.
I'll enter a JIRA issue asking that myself, and whichever other
committers want to be included, be added to a group that will have the
following additional Bugzilla permissions:
- editbugs
- editcomponents
- canconfirm
- editkeywords
Having these additional permissions will especially be critical for
those engaging in QA, I think.
I'm not sure if Infra will do it (security concerns, etc.), but it
would also be good to have one or two admin-level committers, with the
editusers permission, so they can enable the above permissions for
other users without going through Infra.
So if you want to be on the initial batch, please respond to this note
and let me know what your Bugzilla ID is. This is not necessarily the
same as your Apache ID. And if you don't yet have a Bugzilla account
for the project, you can request one here:
https://issues.apache.org/ooo/
Thanks!
-Rob
