Fair point.

The TWiki CoreTeam’s fruitless obsession about rolling their own code rather than using known good http://www.twiki.org/cgi-bin/view/Codev/CpanPerlModulesRequirement is still one of my most fundamental disagreements about that project. (Not least because every time they add a feature they then need to maintain that feature – ceteris paribus this slows growth).

Re: Template Toolkit, I was under the impression that Kwiki now used this. http://www.kwiki.org/index.cgi?KwikiTemplateToolkit

WRT: Being easy to install: this is one of the most contentious issues about TWIki  - upgrades (when they happen, the last one took 15 months to be released) are entirely manual and incredibly painful, to the extent that many complain and even some of the CoreTeam have admitted they personally run versions of code that are two releases (i.e. 2.5 years) old in production. Ease of install is critical, mind: if people can’t install it they can’t use it and this ripples down to the development process. Witness http://template-toolkit.org/pipermail/templates/2003-May/004648.html. Also: http://www.twiki.org/cgi-bin/view/Codev/KwikiWiki  

One (now-ex) TWikiContributor, Michael Sparks, wrote an installer that promised to simplified issues but TWiki’s “leadership” (I use that term cautiously) proved through to both him and I through their sequence of inaction (bottleneck at the top) that any illusions of autonomy were precisely that – an illusion.

I’ve now pretty much given up on TWiki – see http://www.twiki.org/cgi-bin/view/Main/MartinCleaver for my future intentions. I’ve always felt that TWiki has not kept up with the times (for example, an embeddable model could make use of a http://www.twiki.org/cgi-bin/view/Codev/ApplicationServer or provide service through P*Nuke). I am seeking a new right “home” and believe that CGI::Wiki is the most promising prospect.

Peter Masiar may be able to add something about his observations in the increase of pace of Kwiki.

Regards,
    Martin