On Wed, 05 Mar 2008 22:07:37 +0100 [EMAIL PROTECTED] (Diego 'Flameeyes' Pettenò) wrote:
> The tasks are minor tasks that don't require a lot of time at hand, > but gives a good way to judge if the person is in for the experience > or the money, and might be able to cut the deal even for Gentoo devs > if that is really wanted. > > How to implement it for Gentoo? Well I think we have the tool already: > Bugzilla. We just need to add a keyword SOC_QUALIFICATION_TASK; when a > developer think of a working qualification task, he can add the > keyword and CC the soc team or something like that. While the concept itself is a good one, I think that such qualification tasks have to be related to the proposed project to be of real use. With a single codebase and a single implementation language like ffmpeg a single list of tests can work, but Gentoo has many aspects that require completely different skills. For us a generic list of tasks you may help in testing the motivation, but it hardly helps to assess the technical skills of a student to complete e.g. a webapp project if he fixes some ebuilds or writes a patch for a random package. I think we should just require students to list some references related to their project in their application and have the relevant mentors check those. If a student can't find some references on his own he can the soc team/mentors/devs for something. In fact I think what is needed most is improved communications instead of random tests. Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.
signature.asc
Description: PGP signature
