I’m updating my copy of the Smallest Federated Wiki, and the plugin format has evolved again. (Not surprising, the SFW is still in its experimental stage.)

So, I’ve broken out my plugin for ThoughtStorms / SdiDesk format (wikish) from the original Project ThoughtStorms and made a dedicated git repository in the recommended format, naming convention etc.

The plugin is also now available as a node npm package on npmjs for easy installation.

Last year I wrote about how impressed I was by Clojars, the Clojure package repository. Seems like this might actually be the standard way things are done these days. Because npm seems equally straightforward.

The latest instructions for installing extra plugins to your copy of the SFW seem to be here.

Posted in Uncategorised.

Note to self :

sudo apt-get remove python2.7

Has a pretty dramatic effect on a Ubuntu box. There are a LOT of packages these days that are dependent on Python somewhere inside them (including a lot of Unity) 🙂

Posted in Uncategorised.

So Google are shutting down Google Code.

To be honest, I don’t think it will be much missed. It’s a tacit acknowledgement that the state-of-the-art for code-hosting sites, and even how to run code-hosting sites, has moved far beyond it with GitHub.

Google have obviously worked with GitHub and BitBucket to support migration. And, ironically, even support migration back to SourceForge, a site which predates Google Code and which was probably going before the GitHub guys were even born.

I have some nostalgia for the old days of Slashdot and SourceForge. It would be nice if this was a boost to the older site. I wonder when they’ll acknowledge it on their blog.

Posted in Uncategorised.

Further to this story.

I tried to deploy another small Clojure library to Clojars today. And found myself being asked for the passphrase to sign my update.

You need a passphrase to unlock the secret key for
user: “phil jones
2048-bit RSA key, ID XXXXXX, created 2012-03-05

I got into a terrible confusion. Because, for the life of me, I couldn’t remember what passphrase I’d chosen to sign my Clojar last time. Had I just locked myself out of my Clojars account and the existing group and Patterning project?

A couple of hours faffing and I figured it out :

– my previous library WASN’T signed. It’s just in “Clojars Classic” and isn’t “promoted” so doesn’t require signing. That’s why I don’t remember signing it or inventing a pass-phrase.

– the reason that lein deploy was demanding a pass-phrase THIS TIME, was that in this library I’d decided to remove the word SNAPSHOT from the id in defproject.

lein deploy assumes that SNAPSHOTs default to being deployed in classic (the “free-for-all” part of Clojars) whereas non-SNAPSHOTS are intended to be deployed in the new “releases” repository, which is slightly more formalized arrangement, requiring author signing.

– I have gpg on my machine, and I did set up signing for my email address a couple of years ago. This was nothing to do with the previous library I put on Clojars. It was when I was experimenting with encrypted email. (A practice that I’ve embarrassingly let slip since then, but should really go back to.) So that’s the pass-phrase that was being demanded, and that I’ve managed to forget (from 2012, not end of 2014). Not impressive, but not quite as bad as creating one four months ago and then totally forgetting about it.

That still leaves me with some problems when I eventually will want to put my libraries into “releases”) but at least I can still use Clojars. The library will have to continue as a SNAPSHOT though.

Posted in Uncategorised.