[gentoo-dev] Sunrise trusted committers with bugzilla access

[gentoo-dev] Sunrise trusted committers with bugzilla access

[Stefan Schweizer]

To my fellow Gentoo developers,

in the Sunrise project we have some users who are ambitious and cotribute
more than a few ebuilds. Those regulars have the possibility to take the
ebuild quiz and acquire the title "Sunrise trusted committer". Those
sunrise committers can use extended bugzilla permissions to edit keywords
EBUILD and REQUEST for example in the maintainer-wanted@ and
maintainer-needed@ bugzilla region where usually developers clean up litle
or have no interest in spending time on.

Now I tried to get this done with the "[GLEP] Bugzilla access for
contributors" and I was told it is to undefined and misses out the point of
removing access levels again. Also I was told that a GLEP for this is
overkill.

All this is addressed and working with the current arch testers procedure.
The plan is to just treat Sunrise trusted committers the same as arch or
herd testers. The difference is that they operate on ebuilds of all
flavours that interest themself in the sunrise overlay and not on a certain
herd of packages. Neither do they focus on testing for a specific
architecture. Just coding is their work, not testing - which explains the
difference in the name.

Now how do people feel about this approach?


-Stefan

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Sunrise trusted committers with bugzilla access

[Simon Stelling]

Stefan Schweizer wrote:
> To my fellow Gentoo developers,
> 
> in the Sunrise project we have some users who are ambitious and cotribute
> more than a few ebuilds. Those regulars have the possibility to take the
> ebuild quiz and acquire the title "Sunrise trusted committer". Those
> sunrise committers can use extended bugzilla permissions to edit keywords
> EBUILD and REQUEST for example in the maintainer-wanted@ and
> maintainer-needed@ bugzilla region where usually developers clean up litle
> or have no interest in spending time on.

I am not up to date, but I know that when the AT project was started, it
wasn't possible to give out access on specific keywords but just the
KEYWORD field as a whole. Not that it would make a difference, just
mentioning it here...

> All this is addressed and working with the current arch testers procedure.
> The plan is to just treat Sunrise trusted committers the same as arch or
> herd testers. The difference is that they operate on ebuilds of all
> flavours that interest themself in the sunrise overlay and not on a certain
> herd of packages. Neither do they focus on testing for a specific
> architecture. Just coding is their work, not testing - which explains the
> difference in the name.

Huh, I hope they will do testing :P

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 developer
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Sunrise trusted committers with bugzilla access

[Bryan Østergaard]

On Wed, Sep 13, 2006 at 11:39:16PM +0200, Stefan Schweizer wrote:
> To my fellow Gentoo developers,
> 
> in the Sunrise project we have some users who are ambitious and cotribute
> more than a few ebuilds. Those regulars have the possibility to take the
> ebuild quiz and acquire the title "Sunrise trusted committer". Those
> sunrise committers can use extended bugzilla permissions to edit keywords
> EBUILD and REQUEST for example in the maintainer-wanted@ and
> maintainer-needed@ bugzilla region where usually developers clean up litle
> or have no interest in spending time on.
> 
> Now I tried to get this done with the "[GLEP] Bugzilla access for
> contributors" and I was told it is to undefined and misses out the point of
> removing access levels again. Also I was told that a GLEP for this is
> overkill.
> 
> All this is addressed and working with the current arch testers procedure.
> The plan is to just treat Sunrise trusted committers the same as arch or
> herd testers. The difference is that they operate on ebuilds of all
> flavours that interest themself in the sunrise overlay and not on a certain
> herd of packages. Neither do they focus on testing for a specific
> architecture. Just coding is their work, not testing - which explains the
> difference in the name.
> 
> Now how do people feel about this approach?
> 
As there's been very little, if any, interest from anybody besides
Stefan and Recruiters / Developer Relations I'm going to deny the
contributor access idea. Recruiters and Developer Relations feels that
this is a bad idea, especially seeing how hard it has been to reach any
kind of resolution regarding who should get access and how we should
solve the problems that I've outlined earlier.

Regards,
Bryan Østergaard
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Sunrise trusted committers with bugzilla access

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

On Thursday 14 September 2006 17:04, Bryan Østergaard wrote:
> As there's been very little, if any, interest from anybody besides
> Stefan and Recruiters / Developer Relations I'm going to deny the
> contributor access idea. Recruiters and Developer Relations feels that
> this is a bad idea, especially seeing how hard it has been to reach any
> kind of resolution regarding who should get access and how we should
> solve the problems that I've outlined earlier.

agreed
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

[gentoo-dev] Re: Sunrise trusted committers with bugzilla access

[Stefan Schweizer]

Bryan Østergaard wrote:
> As there's been very little, if any, interest from anybody besides
> Stefan and Recruiters / Developer Relations I'm going to deny the
> contributor access idea. Recruiters and Developer Relations feels that
> this is a bad idea, especially seeing how hard it has been to reach any
> kind of resolution regarding who should get access and how we should
> solve the problems that I've outlined earlier.

thanks for the clear no. I should have realized that before writing the GLEP
and everything. Sorry :(

-- 
gentoo-dev@gentoo.org mailing list