This past week, my company put me in charge of operations. The job includes responsibility for our tools and technologies: bug tracking, client request tracking, code repositories, internal knowledge sharing, and Agile process management. Right now we use a collection of tools that we've used for three years: Beanstalk, Sifter, Zendesk, Yammer, and a home-grown Agile tool called Storyboard.
Well, Storyboard runs on the Azure SDK 1.4, which Microsoft will stop supporting at the end of November. Beanstalk, which just turned on support for Mercurial a year ago, has decided to turn it off six weeks from now. Sifter and Zendesk are all right, except they don't really give us the integration we want with each other or with Beanstalk—which, anyway, is going away.
We haven't picked a new tool set yet. But the search has led me to think about changing my own development tools, starting with this blog.
I mentioned about three weeks ago that I'd started playing with Orchard, an open-source content management system that came out of a Microsoft demonstration project.
I want a blog/CMS that can handle the 3,800 entries I've created here. I also want to continue tagging each entry with its location and local time (like this, whose time stamp would look really bizarre without the local time zone), which means I need an extensible application.
Oh, and it either needs a kickass import engine or a way for me to write one.
I can't say for certain when I'll migrate, given how busy I am with everything else. I hope I'll get this done in the next few weeks.