I'm no longer happy with my personal wiki; since upgrading to a version of zwiki that supports dated comments, I find that I'm more comfortable doing "episodic publishing" (i.e. blogging) than collaborating on collected wisdom. A personal wiki is an oxymoron; the wiki genre is all about collaboration.
So I started thinking about how to migrate my content to a blogging system. The first step was to somehow grok all the data I've got in there. I asked in the #zope channel about .zexp format and was discouraged from peeking inside. I was advised to write an
external method that runs inside Zope to export my data,
but by the time I saw that advice, I already had dumpwiki.xsl converting the zope XML export format to XHTML. The actual contents of the wiki pages was quoted, so I'm undoing that with python and xmltramp. I think I hit a bug in the xmltramp serializer. Gotta look into that.
Anyway... the #zope guys were surprised that I had never done any Zope methods. I explained that I use Zope because it's the only server you can apt-get and write to (with iPhoto or emacs eldav mode) out of the box, with elephant-never-forgets versioning.
That got me thinking... with the "cvs is good enough" orthodoxy eroding, and all the work on subversion and arch and darcs, maybe it's time to take another look at the versioning part of WebDAV. Especially git, with its cryptographically secure history... because the problem with the writeable web is more social than technical. People use sftp rather than HTTP because the social protocol is well known, not because FTP is a better protocol than HTTP for writing.
Hmm... if I had a PAW blog or a DIG blog, this might belong there. Maybe reltag will work...
I sure wish python had more penetration in the blogging world. PHP is clearly the server-side deployment vehicle these days, and javascript is the way to juice up clients, but neither PHP nor javascript meets the unambiguity requirement that I think is critical for software engineering in the large.
