-
Strong words from a Democratic senator who’s starting to sound like a frontrunner.
-
Nice potential exploit of an as-yet-unreleased browser.
-
“Plenty of warmth and good definition, but a sense of the large acoustical space is also captured.”
-
Good rundown of the roadblocks that can occur in rolling out even a simple piece of software functionality.
-
Reminder to always trade off value for feature count.
-
One hates to provide help to censors, but guys–if you want to censor a PDF, you really have to make the text and the redaction bars all images rather than overlaying rectangles.
-
Quis custodiet ipsos custodes?
-
Oh crap.
Day: May 20, 2008
Integrating Rally with Trac
My company uses Trac as a ticketing engine and wiki and Rally for requirements management. We’ve been investigating ways to combine the two. (Of course, Rally has its own defect tracking system, but Trac is pretty well entrenched and integrates with our source repository.)
Rally provides a pretty well defined REST-based API, and much of their integrations are built using the RallyRESTAPI Ruby gem. So I went hunting for something comparable for the Trac side. It looks like Rtrac might be the way to go. One challenge is that the Rtrac documentation is scanty and it’s not clear how one might do an arbitrary ticket query (say, all tickets saved since a certain date). But we should be able to use some of the existing Rally integration examples to proceed.