And so it begins.
I've got some ideas about how it might work. For example, I'd love for it to be hands-on and practical, and not only informative. But if it's to succeed, it's direction will need to come from the community.
There are now a few different communication channels for the event. Time will tell which ones prove to be most useful:
- The blog: asyncjs.com (subscribe to the feed, or subscribe by email)
- Twitter account for announcements: follow @asyncjs (and use the #asyncjs hashtag)
- Google group for discussion: groups.google.com/group/asyncjs/
- Individual events announced on Upcoming: upcoming.yahoo.com/tag/asyncjs/