<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>[Satisfaction]: All topics tagged integration for Beanstalk - Unanswered</title>
    <link>http://getsatisfaction.com/beanstalk/tags/integration/unanswered</link>
    <description>All topics tagged integration for Beanstalk - Unanswered</description>
    <item>
      <title>Jabber/IRC Integration</title>
      <link>http://getsatisfaction.com/beanstalk/topics/jabber_irc_integration</link>
      <description>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.</description>
      <pubDate>Sun, 23 Mar 2008 23:19:56 -0000</pubDate>
    </item>
    <item>
      <title>Search through commit history instead of just browse.</title>
      <link>http://getsatisfaction.com/beanstalk/topics/search_through_commit_history_instead_of_just_browse</link>
      <description>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.&lt;br /&gt;&lt;br /&gt;
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.&lt;br /&gt;&lt;br /&gt;
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.</description>
      <pubDate>Sun, 23 Mar 2008 01:36:20 -0000</pubDate>
    </item>
  </channel>
</rss>