I need to get to bed, so this is going to be a bit short... (cue applause)
On 6/20/07, Ted Roche <[EMAIL PROTECTED]> wrote: > What projects has GNHLUG undertaken? http://wiki.gnhlug.org/twiki2/bin/view/Organizational/OurProjects > What distinguishes a successful project from a > not-so-successful one? Whether the project ever did anything more then generate a web page and some mailing list traffic. One thing I've noticed in our subculture is an (unsurprising) tendency to throw technology at problems. Starting a project or group? Okay, create some mailing lists, a wiki, a news site, a CMS, etc., etc. And that's all they ever do. Look at the brazilians of empty projects on SourceForge. "There are seldom good technological solutions to behavioral problems." What a successful project needs most is (1) a clear set of goals, and (2) volunteer time. Projects eat time like fire eats oxygen. If you don't feed it enough time, the fire goes out. > There was no need for a "Hosstraders committee," task force ... Sure there was. Me and maddog. Just because we didn't call meetings or keep minutes doesn't mean we weren't a group of people working towards a common goal, which is what a task force is supposed to be. The goal was "evangelize and demo Linux at Hosstraders". -- Ben _______________________________________________ gnhlug-org mailing list gnhlug-org@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-org/
