Andreas Barth and the Debian team is looking for new release assistants.
the development cycle for etch just started off. We would like to bring new
people into the loop for etch now to better distribute the workload, and look
out for new release assistants.
Quoting from Anthony's mail from spring 2003, this are (still) the
requirements for assistants:
* You must be a Debian developer. Please include your name, and
Debian username on your application. The position will entail
work that requires login access to Debian machines which is
only available to developers.
* You must have time to kill. You'll need to be able to dedicate
a chunk of time each week to this task, and be able to keep
up with what's going on on close to a daily basis. Please include
on your application what times of the week you expect to be able
to spend on this activity, how much Debian stuff you already do,
and when you're usually available on IRC.
* You need to have done QA work before. Please include on your
application a list of sample bugs you've fixed or help fixed in
packages you don't maintain. If you haven't done this before,
feel free, nay, encouraged, to fix some bugs first, then submit
* You need to be able to understand C, /bin/sh scripting, Perl,
Python, Debian packaging, policy, the developers reference, and
similar things. If you don't, don't waste another second reading
this mail, go learn about them instead.
* You need to be aware that this is a gruntwork position. You
won't be deciding release policy, and this isn't an opportunity
to advance any existing opinions you may have about how we
should go about releasing or maintaining Debian. You'll be
given lots of chores, and no authority. The reward for a job
well done will generally just be another, probably harder,
job. If you don't think you can cope with this, don't apply.
Please contact the release team via email@example.com or me
directly if you are interessted. Applications should reach us till End of