What Happened To The Freehackers Union?
zedshaw.com
zedshaw.com
There's focus (games! making games! a theme!), so participants just need to bring some skills (coding/art/music) and the willingness to awkwardly make impromptu teams with complete strangers. It's unlikely that the community will get swayed too far in one direction or another (all games need programming, and it's nice to have good art). "Idea men" have to find some sort of talent they can use for their team, otherwise they'll just be ignored or, at best, used as a playtester or level/content designer.
Negatives are that you have to clear out an entire weekend, and find a place with power and wifi that will let you stay (and potentially sleep) there.
When I was in Pittsburgh, I help start up the Pittsburgh Coding Dojo [1]. Each meeting was split into two parts. During the first part, we broke out into groups to solve a previously selected "code kata." The second half was a show-and-tell in which everyone got to explain their solution.
Sometimes we switched it up and instead of breaking out into groups, we used a single computer with a projector and coded the kata round-robin with everyone looking on.
It was a lot of fun. I really enjoyed that group.
Trust me I keep trying to find a way to do it, but when you can only code for either an hour or two or large chunks but only on the weekend, you just can't get into flow.
I keep hearing about people that can do it, and they allegedly also have friends, and fun away from the keyboard, and they supposedly are also not sleep deprived. Let's just call me an atheist about people like that.
In those 6 months, though, two ideas have been snowballing - (1) that (Greasemonkey) + (code repository with dependency resolution) + (some other stuff) would be a revolutionary piece of software, and (2) that the great thing about Lisp is vaguely similar to "Dependency Injection" and "Inversion of Control" - macros (reader and otherwise) are dependencies which are injected into the reader and compiler. If I was to figure out an elegant way of doing this in JS, I can piggyback on the buzz of DI and IoC to help people think deeper about programming.
Couple that with the frustration of "people don't get it unless you show them code", and I've been spending more and more nights coding away again. So my recommendation would be:
1) Get excited about something
2) Realize that you're very fortunate to have the resources to be excited about something 99% of the world does not
3) Socially commit by telling people about it (even if they don't get it)
Too bad this didn't work out.
otherwise you have all this meta-discussion about what the group's logo should be (why the hell does it need a logo?) and how meetings should run and what color the bikeshed should be, when all people want to do is get together, meet new people, and hack on stuff. why would anyone want to attend a meeting where you are forced to give a presentation in front of strangers? where's the fun in that?
in the openbsd group, when some people want to create something new or hack on something complex, we don't create a wiki and an irc channel and take minutes on the meetings. we organize a "hackathon", invite the relevant people there, and sit in a room together and hack. when we get tired, we go out for beers and talk, then go back to hacking.
Seriously, calm the hell down.
It would be so fucking awesome.
Get it right.