I. Have a system for matching volunteers to tasks

Background: in our current, design and early implementation stage, it is hard for those not immersed in chandler to take on many tasks without being closely tied to someone in OSAF staff. Here is some early thinking on figuring out when we should try to do this. The goals are to balance: (a) the desire to get others involved and the need for the OSAF staff to get the scaffolding in place so that development can proceed at full pace; and (b) the desire to keep people interested and the pssibility of wasting their time with tasks that become obsolete due to changes in plans.

In figuring out these balances, we should consider:

* Would progress on the task be useful in the relevant timeframe?

* Is the bug important enough in the relevant timeframe for OSAF staff to spend enough time on to get someone else going, provide direction, etc?

* Can the task be completed without significant information which isn't yet decided, available or written down?

* Is there someone "in the know" who is interested enough in seeing progress on this task to make sure the volunteer doesn't get lost or blind-sided by (especially undocumented) changes in plans?

* Is the task defined well enough that we would know progress if we saw it?

-- MitchellBaker - 17 Jun 2003