Do you have a proposed timeline to the publication of Kiwi code? What are stumbling blocks? [[http://wikihost.org/wikis]]
--
Fare', thanks for your interest. We don't have a definite timeline yet. We want to release it as soon as we can of course, but we don't want to release it until we can feel confident in its stability in a variety of conditions. tester
Right now it is still very much a beta system. It seems to be holding up reasonably well but there are numerous bugs we still have to fix. In addition, the installation procedure currently takes some knowledge of Kiwi internals to get the system up and running; by the time we release we want it to be a smooth procedure requiring no special knowledge.
We also need to write up some internal documentation to make it easy for other people to find their way around inside the code and extend the system to their liking and the code is still somewhat disorganized from our re-writing of original Cliki code. We need to clean it up so that other people can make some sense out of it.
There are also a few basic features (like a user system, and a complete wiki markup system so that pages don't have to be written with bare HTML) that we did not have time to write before setting up this site, but that we feel the system really needs before it will be viable in the outside world.
It is hard to say exactly how long this will take us. Probably several months when you take into account the fact that we can't work on this full-time -- we have to do it in our spare time so that it doesn't interfere with our 'real' (money-making) jobs. This is why I said on Kiwi that it would probably be early next year.
So, in summary -- just give us a little more time. Your patience will be rewarded with a stable system that is easy to install, maintain, and extend to your liking.
In the meantime, please report any bugs you discover on Kiwi Bugs. If you have any feature requests, feel free to list them in the features section on that page.
- Daniel Finster (Kiwi co-author), 02-Sep-05
--
fph wrote (in Kiwi Bugs): "A brief discussion of any upgrade path for existing Cliki websites."
--
Dear fph:
Thanks for your interest. We have a single function we've defined, REPLACE-CLIKI which you pass the pathname of a CLiki data directory. It imports all the data files, parses the recent-changes.dat, and indexes all the pages. Hopefully this will make it a drop-in upgrade to an existing CLiki installation, at least for stock CLiki systems.
Currently Kiwi only runs on Franz Allegro running AllegroServe. One of our projects before we can release this code publically is we want to port it so that it will run on Portable AllegroServe on other CL implementations. This will help smooth the upgrade for people without an Allegro license.
If you have any other comments, questions or suggestions please post them here.
-- Daniel Finster (Kiwi co-author), 12-Sep-05
--
Hey!
Is it just my imagination, or has someone updated the kiwi code running this site in the past few weeks? It seems that the old display bug in the Recent Changes page is gone.
-- John Wiseman, 2006-03-15
--Anyone there?
-- John Wiseman, 2006-06-09
--
Despite some unstability and installation issues you mentioned last year, I guess it'd be very beneficial to release the Kiwi code. Even if it still does run only on Franz. And even for Lisp newbies, like myself.-- Wojtek Kaczmarek, 2006-07-13
--
Any news yet on a possible release? It's been a while now, even if there are still some bugs, there's no such thing as bugless code. Releasing it will help you improve your code.-- Tom, 2006-12-27
--
Still no info about a date for releasing the code of this wiki?