public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Sunrise trusted committers with bugzilla access
Date: Wed, 13 Sep 2006 23:39:16 +0200	[thread overview]
Message-ID: <ee9ts7$lhj$1@sea.gmane.org> (raw)

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



             reply	other threads:[~2006-09-13 21:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 21:39 Stefan Schweizer [this message]
2006-09-14 16:53 ` [gentoo-dev] Sunrise trusted committers with bugzilla access Simon Stelling
2006-09-14 21:04 ` Bryan Østergaard
2006-09-15  3:03   ` Mike Frysinger
2006-09-15 11:50   ` [gentoo-dev] " Stefan Schweizer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ee9ts7$lhj$1@sea.gmane.org' \
    --to=genstef@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox