Re: [sfWiki-devel] release plan

[Todd L. M. <tm...@ha...>]

> I might suggest a more structured and thorough documentation set 
> (programmer, administrator/deployer and user) may be a good idea 
> at this point.  Since this release would make the sfwiki a fully 
> functional (but not 'safe') wiki system.

	Yup.  The documentation is in dire need of work.  Maybe you/we
should get root for Clark's box and record the administator/deployer side
of things.  (Once I've done something, it becomes very difficult to make
sure I record /everything/ I'm doing the second, especially if I forgot to
reset something.)  I'll write the programmer's guide, and we can leave the
user's guide up in the air for now.

> And now that we have a 'safe' wiki, another major documentation
> effort.

	Indeed.  Perhaps I should add to the file-release reorganization,
include documentation package(s).  (Add a 'documentation' task list?)

> I might add that at some point around release 5 (most major 
> important features implemented) the project should probably do a 
> code review and possibly a full rewrite/rearchitect.

	This is a very good idea.  I imagine a lot of this will be done
for the user auth / session management, because it will (probably) touch
most of the code, but a second look can never hurt.

> Snap shot (full html 'offline' site snapshot of a wiki's contents).  this 
> allows someone to put together a cd of a wiki that someone can 
> browse.

	This is good.  You've noted before that most wiki's eventually
become rather static.  (And I imagine for those with slow links, d/l'ing a
tarball over lunch break will be a more satisfying way of browsing
anyway.)

> auto archive (some facility of creating a data 'bundle' that can be 
> used to archive and restore a wiki.  this may be as simple as doing 
> a database table dump and targzipping the results).

	Should include the *.ihtml formatting stuff, as well, but this is
another good idea.

-_Quinn