[11:46pm] jacobkm: I just read your Django-Rails article, and it's very good; thanks.
[11:46pm] rtomayko: thanks.. i've had a chance to play a bit and i'm excited. so thank you
[11:47pm] jacobkm: I'm not sure we handled the release so well what with not really being ready and all, but spilled milk and all that...
[11:47pm] rtomayko: you were far enough along
[11:48pm] rtomayko: one thing I think is interesting--that I hadn't considered--is the effect watching you guys work is having on people
[11:48pm] jacobkm: What do you mean?
[11:48pm] rtomayko: for example, there's been a lot of svn activity, documentation updates, etc..
[11:48pm] rtomayko: that gives the project a sense of real movement
[11:48pm] rtomayko: and I think people get excited about that
[11:49pm] rtomayko: i wonder if your timing wasn't *perfect*
[11:49pm] rtomayko: absolutely
[11:49pm] jacobkm: You think it's good to keep people salivating a little bit?
[11:50pm] rtomayko: the app was their and the vision solid. there's finishing touches and new progress. i think that's healthy for growing a community
[11:50pm] jacobkm: Hm... good point.
[11:50pm] rtomayko: if you release to early, it doesn't meet people's expectations
[11:50pm] rtomayko: that's something I'm only recently starting to understand
[11:50pm] rtomayko: the commonly cited "release early" philosophy breaks down in some circumstances
[11:51pm] rtomayko: but release too late and you don't get the benefits of letting a community sprout up and feel like they're a part of the project
[11:51pm] rtomayko: so yea.. i'm pretty impressed observing the reaction to the way you guys launched
[11:52pm] rtomayko: i've been thinking about writing an article about how launching is really important