Updated: Never — Philip's Blog

Of course there will be a Friday Beer Event at FOSDEM this year. Only this year, it won't be me organizing it. I felt it was time to do something different and it looks like Jochen has a very firm grip on things. I'm looking forward to attending the beer event as a participant.

What to do with the so-called free time now though?

It seems I've inherited the keysigning bits.

Setting up a very basic key submission server required a mere couple of hours of remembering why Perl is a write-only language. The results of that exercise can be admired at http://ksp.fosdem.org/kspd.pl.txt. Announcing the existence of this service to the world was rather more involved.

The ordeal reminded me -- again -- of primitive cavemen.

Every time someone wanted to paint a woolly mammoth on a cave wall, they'd have to draw it from scratch, either with reference to a previous drawing, or from memory. It was impossible to reuse previous mammoths.

One glorious day, a bright caveman discovered that certain rocks can be rubbed against thin sheets of skin to leave an impression, and the impression can then be used to draw new woolly mammoths. Even more (haha) impressive was that the impression could be used to make a new, slightly modified (longer tusks, who knows?) mammoth-template. Previous impressions could be saved for future generations, to teach them what woolly mammoth looked like in grandpa Thag's youth.

And thus version control was born.

Fast-forward many centuries. People no longer live in caves. Mammoths are now stored in "the cloud". Someone comes up with the wonderful idea of "content management".

One day, someone creates a mammoth and pastes it on the proverbial cave wall. A couple of days later, the mammoth needs changing a bit. In these modern days of the cloud, where mammoths fit in 140 characters or less, this can now be accomplished without going through the pesky process of archiving previous mammoths. Of course, the cave wall could be "configured" to keep old mammoths around, but why bother? In ten minutes time, there will be a new mammoth, and no one could possibly care about the previous one.

And thus version control died.

And mammoths are drawn from scratch again.

As technology advances, humans regress to compensate.

The keysigning announcement is now online. Being the caveman I am, I've also put it in a version control system, far away from any clouds. Just on the off chance that it may come in handy. You know, in a year or so?