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 |
From: Stephen I. <Ste...@br...> - 2004-05-22 11:11:31
|
sounds like a good idea. mainly because as you said most people who want to contribute cannot or will not devote their full time. If tasks can be logically split into small seperate and realisable tasks it is more likely that someone will have a few spare hours, complete the task, submit the patch, and get on with their life. This is how I work and I believe that is probably how most people will work. As a final 'thanks' to that developer their name can be added to a 'Credits' list Any core long term developers will just have to bite the bullet and accept to read all the docs and code and stuck in so in conclusion, this sounds like an interesting model and at least a test run of it will see if the project attracts more people. regards steve i. ----- Original Message ----- From: "Miguel Angel Blanch Lardin" <mig...@ho...> To: <ari...@li...> Sent: Saturday, May 22, 2004 2:14 AM Subject: [Arianne-devel] Task politic proposal > 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 > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Arianne-devel mailing list > Ari...@li... > https://lists.sourceforge.net/lists/listinfo/arianne-devel > > |
From: Matthew D. <ma...@tr...> - 2004-05-24 02:15:28
Attachments:
signature.asc
|
Stephen Ierodiaconou wrote: > sounds like a good idea. mainly because as you said most people who want to > contribute cannot or will not devote their full time. > If tasks can be logically split into small seperate and realisable tasks it > is more likely that someone will have a few spare hours, > complete the task, submit the patch, and get on with their life. > This is how I work and I believe that is probably how most people will work. > As a final 'thanks' to that developer their name can be added to a 'Credits' > list I agree. Last time I tried to devote some time to Arianne, I got bogged down in reading the various docs, and assembling a mental model of how everything inter operated. If you could split out individual tasks, preferably with pointers to both pertinent code and documents, it would greatly simplify the initial "wind-up" for new contributors. If they continue to contribute for a while, they will probably start to understand the overall structure more clearly, but it generally isn't necessary to understand it all for each task. Just a couple of days ago, for the first time in a couple of months, I had a look through the trackers... it looks like you're already a fair way there. From what I saw, the most significant simplification you can make is to add "the following two documents are relevant to this task". The problem with this approach is that it creates a non-trivial amount of management overhead, and the job is not easily delegated... whoever is creating these tasks needs a fairly thorough understanding of how everything works. Matthew |