About this project
Risks and challenges
The most obvious risk to any software project is going over initial time estimates. I've built an extra month into my funding goal to help me keep from running out of money before the project gets done, but since the project is open source, it will also be possible for backers to pick up the code base and finish if for some reason I am unable to finish. Since I'll be documenting my progress and releasing frequent blog posts/screencast walkthroughs of the code, it should be pretty thoroughly documented, making it easy for people to jump in and get started.
Learn about accountability on Kickstarter
Yes. Not having a good free solution for Hubot was the inspiration for this project. There will be a Hubot adapter.
For the last year and a half I've been lead developer/CTO at www.reachably.com, a startup in the social media space, leading development on both our API (which services both our frontend and our iOS app) and most of our Rails/Backbone frontend functionality.
While there probably won't be support for hyperchat servers talking to each other out of the gate, this is functionality I'd be interested in adding if I have additional time to work on it.
The backend will be written in Ruby. Business logic will be self contained and independent of web framework. This will give a chance to try both Rails API and Sinatra, perhaps also Reel+Webmachine. Persistence will be provided through generic adapters starting with a Mongo adapter, memory adapter, and perhaps an SQL adapter. Testing will be rspec and done first. The frontend will be Backbone.js, likely built with Brunch and Chaplin. There will be frontend tests with Mocha or Jasmine.