Announcing GitMinutes - a Podcast for Git Users

I'm a bit late to my own party here, but I've launched a podcast called GitMinutes.

If you've been listening to my amateur/sandbox podcast tfnico's rants, you knew about this already, but now I finally got around to properly flaunt it on my own blog.

Why GitMinutes?

It's an obvious rip of Scott Hanselman's Hanselminutes, but hey, he nicked This Developer's Life from This American Life. I think GitMinutes has a great ring to it, it's easy to spell, and it had zero hits on Google before I started this.

But why a whole podcast about Git?

I'll admit it is a fairly narrow scope. But I was listening to a few technical podcast episodes lately that were about Git, and I wasn't really happy with the substance of it.

Also, I was recently approached about writing a Git book, but I figured that I could make something cooler than a book instead.

Also, there aren't enough technical podcasts for me to listen to, so I decided to add a little.

Also, there are a lot of Git users out there, and some don't really get to geek out about their Git usage enough. I hope this helps them.

What's in it for you?

I dunno, fame and fortune I guess. Actually, it's running at an estimated net minus of about 10$ monthly for all the traffic out of Amazon S3, so if you want to sponsor the show, I'm willing to negotiate something for you to cover that. I'd also love to buy a proper intro/outro song (although the free one from danosongs.com is great). I'd even love to be able to afford a 500$ audio mixer, but that's maybe a bit down the road.

If you want to know how I got rolling with podcasting, have a listen at tfnico's rants #002. If you want to learn more about how to listen to podcasts, listen to tfnico's rants #003.

How long will you keep it up?

I'll admit there might be a limit to interesting things we can discuss about Git, so after a bunch of episodes, I'll call it a day. Maybe start another podcast or something. Right now I've got 10 episodes lined up with some really interesting guests, so I'll see how it goes from there.

The first episode is out since Monday 25th, I've already recorded episode 2 & 3, and they will come out the following Mondays. Thanks for listening!

Comments

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password...

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git -> ~/.atom/* config-mr.git -> ~/.mrconfig -> ~/.config/mr/* config-tmuxinator.git -> ~/.tmuxinator/* config-vim.git -> ~/.vimrc -> ~/.vim/* config-bin.git -> ~/bin/* config-git.git -> ~/.gitconfig config-tmux.git -> ~/.tmux.conf config...