--- xml/htdocs/proj/en/glep/glep-0041.html 2005/10/13 14:53:37 1.2 +++ xml/htdocs/proj/en/glep/glep-0041.html 2005/11/11 18:42:27 1.3 @@ -35,7 +35,7 @@ Version:1.2 -Last-Modified:2005/09/15 21:01:51 +Last-Modified:2005/10/13 14:53:37 Author:Simon Stelling <blubb at gentoo.org>, @@ -80,13 +80,21 @@

ATs should basically be treated as staff. This includes the following changes to the current situation:

-

Additionally, the mentoring period should be shortened to two weeks if an AT -wants to take the end quiz to become a developer, assuming he has been AT for -at least two weeks. The amd64 porting team has handled situations -like this for a while and only made positive experiences.

+

There will be a 30 day probationary/mentoring period for new ATs.The lead AT/HT +for arch/herd will be responsible for the mentoring period. If arch/herd +doesn't have a Lead AT/HT, then either the arch/herd lead or the Strategic AT +Lead will be responsible. The Lead AT is a seasoned developer that watches for talent, +recruits and mentors ATs. Additionally, the mentoring period should be shortened +to a minimum of two weeks if an AT wants to take the end quiz to become a developer, +assuming he has been AT for at least two weeks. The amd64 porting team has handled +situations like this for a while and only made positive experiences.

Also, the idea of an arch tester as a trustworthy user who is able to test critical changes (such as hard masked software branches), could be expanded to other herds. These 'ATs' wouldn't be called arch testers as the 'arch' is @@ -110,7 +118,7 @@