Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30EB5B4F5 for ; Tue, 17 Jan 2012 01:51:25 +0000 (UTC) Received: (qmail 36217 invoked by uid 500); 17 Jan 2012 01:51:24 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 36006 invoked by uid 500); 17 Jan 2012 01:51:23 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 35998 invoked by uid 99); 17 Jan 2012 01:51:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2012 01:51:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wolf.halton@gmail.com designates 74.125.82.43 as permitted sender) Received: from [74.125.82.43] (HELO mail-ww0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2012 01:51:18 +0000 Received: by wgbdr11 with SMTP id dr11so6898991wgb.0 for ; Mon, 16 Jan 2012 17:50:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UL+LmTW8D9AaKwt9wjybdEj+2N07u5KgR6QtDCH1o4M=; b=ssuoaSW/JM4UkQ3k+qz3Mzi6L4xqh8OK6d1gZBc2yr0ps5QmU09xAq9Z1h+tNq4u2y r1DLeBvqVtP3+hKDCdFVTaVeTdpi+ObjFONUeSb6m09Md3UUIso2arcO36j67dc/DOyP rDWGp+lloDbq9sb5555BE7y3473NtoqgU9y0A= MIME-Version: 1.0 Received: by 10.180.83.104 with SMTP id p8mr19142106wiy.4.1326765057021; Mon, 16 Jan 2012 17:50:57 -0800 (PST) Received: by 10.223.1.200 with HTTP; Mon, 16 Jan 2012 17:50:56 -0800 (PST) Received: by 10.223.1.200 with HTTP; Mon, 16 Jan 2012 17:50:56 -0800 (PST) In-Reply-To: References: Date: Mon, 16 Jan 2012 20:50:56 -0500 Message-ID: Subject: Re: Seeking Bugzilla Admin Volunteers From: Wolf Halton To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d044289eeec967e04b6af8fc4 --f46d044289eeec967e04b6af8fc4 Content-Type: text/plain; charset=UTF-8 I volunteer. http://sourcefreedom.com On Jan 12, 2012 2:16 PM, "Rob Weir" wrote: > 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 > --f46d044289eeec967e04b6af8fc4--