Jim Carroll <[email protected]> writes: > What if we used the Vague wiki to track promising open source > projects, and how they might be implemented in Vermont... and also > keep some to-do lists on the wiki that would be broken down to the > point that any of us could do a step with a free hour or two.
I'm not sure that a lot of creative work can be broken down in this way. There's a class of data-processing stuff (see the types of things in the Mechanical Turk HIT queue¹; translation work comes to mind, too², and monkey-testing effort³). But it quickly gets down to a point where the context needed to make the task a 1-2 hour job takes 1-2 hours to convey, and as much time to create as a consumable in the first place. But that's not to say that VAGUE couldn't be the forum for collaboration on the creation of some project (or improvement of an existing project). As always, it's identifying the project and getting people to commit to its execution that are hard. And using the VAGUE wiki to track the VT impact or footprint of existing projects is a great idea. I've noticed Aaron has been wiki-gnoming the <http://www.uvm.org/vague/wiki/index.php/Related_links> page to great effect, recently. ¹: https://www.mturk.com/mturk/findhits?match=false&state=WmxMc2JQWkgyNUtYNHpha0loMkxkL3pSUWRrPTIwMDkwMTIxMTkwNVVzZXIudHVya1NlY3VyZX50cnVlJQ-- ²: https://translations.launchpad.net/ubuntu/+translations ³: http://feedbackarmy.com/ -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo $...@${b}
pgplsrniSuvKw.pgp
Description: PGP signature
