Things have been a little quiet around here since 0.4.1 flew the coop, but don’t let that fool you. Despite the holiday interruptions the Dojo community has been in the midst of several important discussions on the future of the Toolkit and the future of the Foundation. The time is coming to make the hard cuts and decisions about one-point-oh that can only really happen over beer, so I’m happy to announce the second Dojo Developer Day (aka: 3D2), Jan 12-13th in Mt. View CA. AOL is once again generously donating use of their facility and has promised to keep us from starving.
Unlike the previous Developer Day, this one is not aligned with a conference and isn’t really an event for users. Instead, project contributors and participants are going to pow-wow for two full days to hash out the future of Dojo and start on the work that’s going to make it happen.
Event details are in the wiki, and an RSVP to <rsvp at dojotoolkit.org> is greatly appreciated. If you need a place to stay, a ride to the event, or some other sort of help getting to 3D2, let us know when you RSVP.
Update: I almost forgot! The day before 3D2 (Jan 11th), the Cometd project is going to be having a similar developer gathering at the 6Apart offices in San Francisco. Send word to the Cometd lists if you’re going to be attending that one.
I am pleased to announce that Cometd has been accepted as a Dojo Foundation project!
“Cometd is a scalable HTTP-based event routing bus that uses a push technology pattern known as Comet.” Cometd support is already found in the Dojo Toolkit in the dojo.io.cometd package, found in current nightly builds and in Subversion.
The Dojo Foundation now has 3 projects: Cometd, the Dojo Toolkit, and Open Record.