Recently active topics in Beanstalk tagged with integration

There is a high level of overlap in beanstalk (bs), basecamp (bc) and lighthouse (lh). Specifically projects (bs, bc, lh), users (bs, bc, lh), and milestones (bc, lh).

It would be fantastic to sync the projects from basecamp to beanstalk and to lighthouse, and do the same for milestones. This would also go for users. So, considering that basecamp would be the center of operations (used by project managers) we could do the following:
1) Create a new project in basecamp. Go to beanstalk and flag that project to be "synced". This would auto-create the repository and auto-create a lighthouse project. It would also auto-create all of the appropriate user accounts.

2) Sync users between Basecamp and beanstalk and lighthouse. If I manage users in lighthouse, it should manage users in beanstalk and lighthouse.

3) Sync Milestones between Basecamp and Lighthouse.

I realize that basecamp has a weaker API that does not allow for many things to be remotely created. However, it does allow most things to be exported. And lighthouse does a great job with their API allowing you to do nearly anything remotely.

The only draw-back is that there is no way to attach events to basecamp so that when a new milestone, project, user is created that beanstalk can know about it and act accordingly.

I was wondering if there was a plan to integrate the beanstalk app with a jabber bot or IRC bot. I don't use campfire with my developers, but do use IRC and we all have Jabber JIDs - so integrating with either IRC or jabber would be awesome.

I'd love to be able to search though commit history either based on keywords. I spend a good amount of time figuring out what other team members did, and being able to search for concepts throughout the history of commits would be killer for me.

I don't know if you would want to have search terms applied to commit mesages, code content, or usernames, but there is definitely a chance for some interesting features here. Perhaps, instead of search, take advantage of tagging...that would work quite well with the Lighthouse integration.

This is no small task, but you could probably add some of this functionality just by tossing acts_as_ferret onto changeset models. (BTW, I'm assuming this is built in Rails and not .Net...I know Wildbit does both) This could definitely grind your server pretty hard, though.