Thomas Ferris Nicolaisen's blog

A bit over a year ago, me and my colleague Felix started working on a little experimental project during our 20% time. As far as I can remember, we wanted to do some Clojure, and we wanted to make something that looked like a company-internal Twitter. We called it Flurfunk , which is the German word for "office talk" or something along those lines. After a few days of development, we set it up on an internal server, and it was already quite useful, as it was a nice way to group-chat with the whole team. We are co-located, so we don't really IM so much, but it's still nice for pasting URLs and unix one-liners, etc. We then proceeded to integrate it with our Jenkins build notification mails, and commit mails, so there's a nice timeline of what's going on. A bit like our team's heartbeat . A nice bonus is that if either of us are doing home-office, it's a nice way to interact with what the rest of the team is doing. We actually open-sourced

Continuing my little tribute to the Gitblit 1.0 release , I asked some old colleagues of mine, Leif and Trygve , about their experiences with using Gitblit in practice. Q: How do you use Gitblit?   Leif: Webstep is a consultancy company, and we needed a Git repository for a specific client project that is being run in-house. At the moment the Gitblit server hosts three different projects, but only one is in active development. Trygve: I was working as a consultant in a team that was currently using Subversion, but wanted to switch to Git. IT were working on an installation of Gitorious, but the project didn't have a very high priority. As an intermediate solution I looked around for small, simple solutions for hosting a low number of repositories (around 10). As it was only our team that was going to use it, we didn't have any need for complicated security setups, just plain hosting. Having a web interface was a big plus as I wanted to show it was easy to create lots o