From: Miguel A. B. L. <mig...@ho...> - 2004-05-22 01:14:51
|
Hi all, Lately I have been thinking about the way of recruiting new people ( before kse case :-) ) and I have found not motivating at all the way of looking for developers and what they found when they join. I think kse's email hit several important mistakes at the recruit process. Mainly he says he don't want to do the ugly work: read docs, read code, fix docs, fix code. That's fine. I do agree with him. Unfortunately that process is the only way of learning an application. So to avoid this terrible gap between desire and reality and after reading a few bits of Cathedral and the baazar model I think that it would be nice that instead of recruiting developers we simply request tasks to be done, that is less cathedral and more baazar model. For example instead of a Java developer for server that needs to be instructed about what server is, how it works and that have to either frustrate himself/herself searching tasks or getting annoyed because he/she is assigned them, we could just send a request for tasks that need to be done. Developer will apply for the task and commit a patch, no more relation to with arianne at all. Usual contributors could/should be granted CVS access. What do you think? Agree? Disagree? Silence? _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail |