Re: [sfWiki-devel] release plan

[Iain S. C. M. <crr...@me...>]

On 28 May 00, at 16:26, Todd L. Miller wrote:

> Release 2: [provisionally, by June 11]
> * spend some time cleaning up (refactoring?) the code.
> * implement statistics as previously discussed
> * implement (the rest of) WikiFormatting
> - Change the file release scheme.
> 	one module for -full, with .tgz and .zip
> 	one module for -htdocs, -portal, -root, with .tgz and .zip

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.

> Release 3:
> * version tracking
> 
> Release 4:
> * user authentication and session management

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

> Release 5:
> * page watches
> * page deleting
> * CVS ACLs (, integration w/)
> 
> Comments?  (What do we do past Release 5?)

Looks good.  Seems like a good schedule to me.

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.  I find it always 
good to have a point where you say, 'ok, now lets look this thing 
over and from what we learned, let's rewrite it better/faster/etc' or 
you might look at it and say, 'hey, this thing doesn't need a rewrite'.

Other features not listed that I think would be really nice:

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.

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).

-iain