>> What if we used the Vague wiki to track promising open source >> projects, and how they might be implemented in Vermont... > > I'm not sure that a lot of creative work can be broken down in this > way.
I agree... but I think there's plenty of mundane work that could be done after a few creative face-to-face sessions at the pub. > 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. I've been involved in some online communities that encourage five minute actions... such as call one key person and briefly tell them that you think XYZ is worth considering. The hard part is having that person be knowledgeable and 'warm' enough to represent the idea well... but we can all do that. There are plenty of other quick actions such as doing a little research online and updating the wiki. > 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). I'm really excited by this video on change.gov: http://change.gov/newsroom/entry/inside_the_transition_technology_innovation_and_government_reform/ and I'll keep looking for ways that we (or at least I) can join forces with these programs. > As always, it's identifying the project and getting people to commit to > its execution that are hard. What relatively mundane projects would be tractable? How about bringing more attention to libraries that are adopting open source software? Or approaching doctors in local family practices to see what systems they use, and seeing if there are any open source alternatives within striking distance... -Jim
