Re: [gentoo-dev] proxy-maintaner improvement (was: Monthly Gentoo Council Reminder for March)

[Peter Volkov]

В Чтв, 06/03/2008 в 09:08 +0530, Anant Narayanan пишет:
> The idea is to make the recruitment process as easy and quick as
> possible, while ensuring that the person involved has the requisite
> skills.

Could you explain, how our recruitment process is long and hard? Also
how could you ensure that the person involved has the requisite skills
without asking him some questions (read quizes)? If potential developer
does not have either time or knowledge to answer our quizes he/she'll be
unable to maintain packages on a daily/weekly basis:
 * if candidate knows nothing about ebuilds he/she have to spend some
time and learn what they are, or how do you suppose it's possible to
maintain packages without such knowledge? We ~40 questions in both
quizes. Doing about 1 question a day (no so hard I suppose) it's
possible to finish quizes less then in 2 months.
 * if you know how to write ebuilds, it's possible to finish both quizes
in one day, not to hard/long I suppose too.

We already have alternatives: proxy-maintainer and sunrise overlay.


That said, I agree that proxy-maintainers should be improved. I'll try
to gather ideas from this thread and may be add some new. So:

* proxy-maintainers work with developers through bugzilla (as we have
them now), but after they finish ebuild quiz and recruiters approve it
they could:

 - get access in cvs to maintained packages. In this case:

1. they should have mentors which are subscribed to all proxy-maintainer
commits, and the mentor is responsible for all the things
proxy-maintainer commits
2. proxy-maintainer couldn't request initial package stabilization, only
mentor/dev from herd/team is allowed to do that
3. they should have IRC cloak, forums mark, voice in @gentoo-dev,
subscription to -core & -dev-announce.
4. they should be announced in -dev as ordinary

Also proxy-maintainers should be mentioned somewhere in the /doc/ area
of our web-site.

-- 
Peter.