Gentoo Archives: gentoo-devrel

From: Wernfried Haas <amne@g.o>
To: gentoo-devrel@l.g.o
Subject: Re: [gentoo-devrel] [GLEP] Bugzilla access for contributor
Date: Sat, 02 Sep 2006 08:39:27
Message-Id: 20060902083611.GB13929@superlupo.rechner
In Reply to: [gentoo-devrel] [GLEP] Bugzilla access for contributor by Stefan Schweizer
On Sat, Sep 02, 2006 at 12:13:13AM +0200, Stefan Schweizer wrote:
> 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.
Perhaps not what devrel thinks but i'll rather drop my personal opinion. First off, imo there should have been a GLEP before, or this one should GLEP up stuff that is used as the starting point of this GLEP, more see below.
> 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.
This is very vague. What kind of contributors are you talking about? I assume you mean people contributing on sunrise, or does that also imply people who contribute to another project should get those privileges, too? What kind of people do you have in mind? Does that mean the contributors become official project members like devs/ATs?
> 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.
Stupid question, but why don't they do the quiz and become developer/staff/AT if they want to work on bugs? What's the reasoning to make another class of users who can edit bugs? Also is bugzi rights _all_ they are supposed to get or other stuff, too? Also, what kind of bugzi permissions are we talking about, just marking bugs as fixed?
> An example for this has been obvious since the overlays project was established. > Bugs for overlays should be filed on 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.
That's one of the reasons why sunrise should have been GLEPed from the beginning rather than finding out there are some substantial work flow and permission problems. ;-)
> 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
The ebuild quiz is also used in the AT project, so what exactly would be the difference between your contributor and and an AT/HT?
> Management > --------------- > > This cannot be managed by devrel, because they lack the resources to do it.
s/devrel/recruiters and have you talked it over with them or is this only an assumption? I'm not saying they do have the resources, but that statement sounds rather final for the first version of a GLEP. Executive summary (+ some more opinion): The whole glep is very vague, please be a bit more specific. Also, there really should be a good reason to introduce a new class of "official Gentoo people with extra permissions" as well as a difference to the ATs. Currently contributor and AT seem to have both the same requirements and permissions. cheers, Wernfried -- Wernfried Haas (amne) - amne at gentoo dot org Gentoo Forums: IRC: #gentoo-forums on freenode - email: forum-mods at gentoo dot org


Subject Author
Re: [gentoo-devrel] [GLEP] Bugzilla access for contributor Stefan Schweizer <genstef@g.o>