On Tue, Apr 11, 2006 at 06:40:34PM +0200, Marc 'HE' Brockschmidt wrote: > 1.2 Already proposed solutions > ------------------------------
1.2.7 Knowledge-area assessment ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Determine a set of "required knowledge" modules, and ensure that the applicant has been assessed satisfactorily on all of them. This assists in assessing different sorts of applicants -- you can customise the "required modules" for a documentation person as opposed to a package maintainer, without needing to totally gut the whole system. With this, we'd essentially get rid of the arbitrary and pointless distinction of P&P vs T&S (a number of the questions in both templates cross over into the other's territory anyway), and allow us to better assess what an applicant knows and doesn't know. It's also easier for an AM to "spice up" their life a bit by replacing particular modules with different types of assessment, while retaining some base level of comparability between applicants (the question for each module effectively comes down to "do I think, from this work, that the applicant has a suitable knowledge of <foo>", where <foo> could be the BTS, Debian philosophy, linker flags, Docbook, or whatever). - Matt
signature.asc
Description: Digital signature
