This is an interesting idea but would be tricky to manage.
People who will give their time for free but are in other full time paid work will generally need to work out of hours and remotely. I think these are the type of people you are thinking about - the likes of the typical contractor on this board.
To work in this way you would need to break down the project into manageable packages (what size/skills?) that individuals could take on.
To prevent the silly requests you could allocate a notional budget based upon the amount of hours volunteers would commit (in advance) over the project timeline. Each work package could be estimated and there would be a finite limit to what could be fitted in and so this would give a mechanism to prioritise requirements.
Since you would be reliant on people's good nature to keep contributing you would not be able to forecast delivery dates with good accuracy - but then that is true on most projects anyway!
You would need to have some "trusted" staff to review and test the systems to ensure no "nasties" were slipped in e.g. Trojans, unlicensed stuff, etc.
The ad-hoc and remote working nature of such a project would lend itself to way the Open Source community works so maybe it would be useful to look at the way they operate.
This could be an excellent way to fill time between contracts whilst learning new skills and keeping your CV full and fresh.
It will be interesting to see how (if) this develops.
Good luck.
People who will give their time for free but are in other full time paid work will generally need to work out of hours and remotely. I think these are the type of people you are thinking about - the likes of the typical contractor on this board.
To work in this way you would need to break down the project into manageable packages (what size/skills?) that individuals could take on.
To prevent the silly requests you could allocate a notional budget based upon the amount of hours volunteers would commit (in advance) over the project timeline. Each work package could be estimated and there would be a finite limit to what could be fitted in and so this would give a mechanism to prioritise requirements.
Since you would be reliant on people's good nature to keep contributing you would not be able to forecast delivery dates with good accuracy - but then that is true on most projects anyway!
You would need to have some "trusted" staff to review and test the systems to ensure no "nasties" were slipped in e.g. Trojans, unlicensed stuff, etc.
The ad-hoc and remote working nature of such a project would lend itself to way the Open Source community works so maybe it would be useful to look at the way they operate.
This could be an excellent way to fill time between contracts whilst learning new skills and keeping your CV full and fresh.
It will be interesting to see how (if) this develops.
Good luck.
Comment