1.1

Stefan Schweizer wrote:
> Hi,
> 
> As requested by multiple devs in my last mail thread about this I have
> written a GLEP. I send this here before sending to gentoo-dev@ so that
> I can gather what devrel thinks about it. Please have a look.

I don't really see how this is GLEP worthy..... Ok so all of Gentoo
should know about it...but it isn't a "far reaching change."

> 
> Best regards,
> - Stefan
> 
> 
> ------------------------------------------------------------------------
> 
> GLEP: 52
> Title: Bugzilla access for contributors
> Version: $Revision: 1.1 $
> Last-Modified: $Date: 2006/08/16 19:25:14 $
> Author: Stefen Schweizer <genstef@g.o>,
> Status: Draft
> Type: Standards Track
> Content-Type: text/x-rst
> Created: 01-Sep-2006
> Post-History: 01-Sep-2006
> 
> 
> Abstract
> ========
> 
> To improve the development flux in Gentoo, we should allow more people to
> manage bugs in our large bugzilla database.

This already happens, I had perms to modify portage bugs like 10 months
before I became a developer

> 
> 
> Current situation
> ================
> 
> Currently there are specific deals with arch testers and devrel/infra to allow
> arch testers to edit bugs. This GLEP is written to standardize the process and
> make it available for all aspects of Gentoo where work is being done by people
> who are no full developers.

So....talk to Jforman/Kingtaco?  All you really need is a group made in
bugzilla; along with a specific subset of bugs you want them to edit.

> 
> Management
> ---------------
> 
> This cannot be managed by devrel, because they lack the resources to do it.
> Instead a developer who mentors more people gets access to edit bugzilla
> permissions and can add people there where he has checked the ebuild quiz. The
> developer will also take care of removing them again if needed. This reflects
> current arch tester practice.

so hparker has bugs editing perms, or recruiters does it? (/me doesn't
know).
-- 
gentoo-devrel@g.o mailing list