public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Knight <tomk@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The Gentoo Developer Handbook - Quis custodiet ipsos custodes?
Date: Tue, 20 Jul 2004 00:03:58 +0100	[thread overview]
Message-ID: <20040719230358.GC22507@earwig.bogus> (raw)
In-Reply-To: <200407192144.38087.stuart@gentoo.org>

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

> 
> Btw, what was that about a probation period *before* cvs access was granted?  
> I was never quite clear how the would-be dev in question was supposed to 
> successfully complete a probation when he wasn't actually a dev yet, and 
> therefore couldn't do anything.
> 

Being a new dev, I've recently read all the relevant devrel docs. There's a
two week waiting period before you become a dev during which you should
complete the dev quiz. According to
http://www.gentoo.org/proj/en/devrel/recruiters/ there is an extra
probationary period after you become a dev:

"Additionally, for 30 days after joining, a new developer is considered to
be in a 'probationary period' in which their mentor is responsible for
actions taken by the new developer. This provides a certain level of
accountability."

Tom

-- 
Tom Knight
tomk@gentoo.org
GPG Public Key: http://dev.gentoo.org/~tomk/tomk.asc

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

  parent reply	other threads:[~2004-07-19 23:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19  9:20 [gentoo-dev] The Gentoo Developer Handbook - Now with FREE* extra mojo! Tim Yamin
2004-07-19 13:14 ` Daniel Armyr
2004-07-19 13:58 ` Spider
2004-07-19 15:27   ` Joshua Brindle
2004-07-19 18:20     ` [gentoo-dev] The Gentoo Developer Handbook - Quis custodiet ipsos custodes? Ciaran McCreesh
2004-07-19 20:22       ` Corey Shields
2004-07-19 20:35         ` Ciaran McCreesh
2004-07-19 20:55           ` Corey Shields
2004-07-19 21:03             ` Ciaran McCreesh
2004-07-19 20:47         ` fmouse-gentoo
2004-07-19 20:57         ` Jason Rhinelander
2004-07-19 21:02           ` Corey Shields
2004-07-19 21:14           ` Tim Yamin
2004-07-19 20:44       ` Stuart Herbert
2004-07-19 21:06         ` Ciaran McCreesh
2004-07-19 21:12           ` Stuart Herbert
2004-07-19 21:44             ` Spider
2004-07-19 22:03               ` Stuart Herbert
2004-07-20  0:31                 ` Dylan Carlson
2004-07-20  5:10               ` [gentoo-dev] " Duncan
2004-07-19 22:30         ` [gentoo-dev] " Grant Goodyear
2004-07-19 23:03         ` Tom Knight [this message]
2004-07-19 22:19       ` Grant Goodyear
2004-07-19 23:46         ` Deedra Waters
2004-07-20  0:23       ` Kurt Lieber
2004-07-20  1:38         ` Jon Portnoy
2004-07-20 10:15           ` Chris Bainbridge
2004-07-20 12:36             ` Dylan Carlson
2004-07-20 15:43               ` Stuart Herbert
2004-07-20 17:55                 ` Kurt Lieber
2004-07-20 21:13                 ` Deedra Waters
2004-07-20 21:43                   ` Stuart Herbert
2004-07-20 21:50           ` Donnie Berkholz
2004-07-20 18:07         ` Jason Rhinelander
2004-07-19 21:49 ` [gentoo-dev] The Gentoo Developer Handbook - Now with FREE* extra mojo! Stuart Herbert
2004-07-22  9:27 ` Stuart Herbert

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=20040719230358.GC22507@earwig.bogus \
    --to=tomk@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