From: Daniel Gryniewicz <dang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 41: Making Arch Testers official Gentoo Staff
Date: Mon, 12 Sep 2005 20:15:14 -0400 [thread overview]
Message-ID: <1126570514.3416.8.camel@localhost> (raw)
In-Reply-To: <432609D3.7070909@gentoo.org>
On Tue, 2005-09-13 at 00:05 +0100, Daniel Drake wrote:
> Simon Stelling wrote:
> > This has been in the todo-list for quite a while, but finally it's done.
> > I'm curious what you think of it.
>
> I'm curious how much change this would involve for the people involved.
>
> Perhaps you could explain how the current system works (I presume from reading
> the GLEP that they _don't_ currently have commit access and havent taken any
> quizzes)? How do they get their keywording work into the tree?
>
> Thanks,
> Daniel
They don't have commit access (or any CVS access at all) but have taken
the ebuild quiz, the first dev quiz. They have the ability to KEYWORD
bugs in bugzilla, that the only special ability they get (other than
voice in #-amd64-dev) currently.
Daniel
(former AT)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-13 0:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 19:39 [gentoo-dev] GLEP 41: Making Arch Testers official Gentoo Staff Simon Stelling
2005-09-12 19:50 ` Ciaran McCreesh
2005-09-12 21:10 ` Martin Schlemmer
2005-09-12 21:13 ` Olivier Crete
2005-09-12 21:17 ` Homer Parker
2005-09-12 19:56 ` Stephen P. Becker
2005-09-12 20:18 ` Simon Stelling
2005-09-12 20:08 ` Martin Schlemmer
2005-09-12 20:13 ` Donnie Berkholz
2005-09-12 20:30 ` Stephen P. Becker
2005-09-12 20:47 ` Homer Parker
2005-09-12 20:57 ` Stephen P. Becker
2005-09-12 21:20 ` Homer Parker
2005-09-12 21:02 ` Simon Stelling
2005-09-12 21:21 ` Homer Parker
2005-09-12 21:46 ` Joseph Jezak
2005-09-12 22:12 ` Homer Parker
2005-09-12 20:36 ` Simon Stelling
2005-09-12 20:45 ` Homer Parker
2005-09-12 21:08 ` Diego 'Flameeyes' Pettenò
2005-09-12 20:59 ` Wernfried Haas
2005-09-12 23:05 ` Daniel Drake
2005-09-13 0:14 ` Homer Parker
2005-09-13 0:15 ` Daniel Gryniewicz [this message]
2005-09-13 7:04 ` Chris White
2005-09-12 22:47 ` Stephen P. Becker
2005-09-12 23:16 ` Martin Schlemmer
2005-09-12 23:34 ` Alec Warner
2005-09-12 23:53 ` Stephen P. Becker
2005-09-13 0:13 ` Daniel Gryniewicz
2005-09-13 0:26 ` Stephen P. Becker
2005-09-13 0:47 ` Nathan L. Adams
2005-09-13 1:41 ` Alec Warner
2005-09-13 1:50 ` Ciaran McCreesh
2005-09-13 3:01 ` Alec Warner
2005-09-13 3:14 ` Ciaran McCreesh
2005-09-13 3:51 ` Brian Harring
2005-09-13 4:04 ` Ciaran McCreesh
2005-09-13 11:26 ` Simon Stelling
2005-09-13 12:00 ` Luca Barbato
2005-09-13 13:08 ` Mike Doty
2005-09-13 13:49 ` Wernfried Haas
2005-09-13 4:27 ` Homer Parker
2005-09-13 11:22 ` Simon Stelling
2005-09-16 15:38 ` Lares Moreau
2005-09-13 5:39 ` Brian Harring
2005-09-13 16:14 ` Ciaran McCreesh
2005-09-13 11:21 ` Simon Stelling
2005-09-13 16:13 ` Ciaran McCreesh
2005-09-13 0:11 ` Homer Parker
2005-09-13 0:10 ` Homer Parker
2005-09-18 6:26 ` [gentoo-dev] " R Hill
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=1126570514.3416.8.camel@localhost \
--to=dang@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