Hi,

as requested by multiple devrel members I have written a GLEP to standardize
bugzilla access for contributors. It has already been discussed on the
devrel mailing list before but I am looking for a wider opinion now.

This is also a submission for the new council when it meets.

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 <[EMAIL PROTECTED]>,
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.


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.

Requirements
============

Bugzilla permissions
------------

It is needed that contributors who work on bugs can edit them on their own and
do not have to rely on their mentoring or supervising developers to reassign
or modify bugs.

An example for this has been obvious since the overlays project was established.
Bugs for overlays should be filed on bugs.gentoo.org and will most likely get
assigned to the developer/herd. This does allow a contributor to fix the bug
but only to mark it as fixed in bugzilla when he is also an arch tester.

Security
-----------------

To ensure that not everyone who asks for it can get access to edit bugs it is
required to complete the ebuild quiz prior to requesting access

Management
---------------

This cannot be managed by recruiters, 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.

Copyright
=========

This document has been placed in the public domain.

Reply via email to