Re: [sfWiki-devel] prioritised to-do list

[Iain S. <iai...@ya...>]

At 06:18 PM 3/12/2001 -0500, Todd L. Miller wrote:
>I should stick in this the wiki so could update it there, but I'm probably
>going to be cleaning the database out as part of the deployment testing,
>so...

Excellent.  An option may be to try using their new tracker system and put 
this in as bugs/feature requests.  I'm of the opinion that the wiki may be 
better if the list remains minimal and the # of bugs is small.  With more 
though, it may be easier to manage in the sf tracker.

>do (fix) for this (#3) release
>
>* put help -- using the Wiki, the WikiFormatting, etc -- into the wiki;
>         distribute in tarballs and CVS as .txt files, and insert
>         instructions about using import.php3 to get them into the wiki.
>
>* establish a cron job/script for doing regular database backups.
>
>* implement defense against "spider bombs" editing pages

Seems reasonable.

>* list the last editor of the page on info.php3

Probably can be moved to v4 unless its easy to do.  I don't think its 
necessary for this version.

>do (fix) for the next (#4) release/
>
>* offsite backup script; an 'export.php3' script would be nice, but a
>         script doing MySQL database dumps would be OK also.
>
>* list of orphan pages page (orphans.php; integrate with web admin in
>         wishlist...)

Yes.  Sounds very good.

>wishlist/
>
>* diffs between revisions.  (Leverage SourceForge's cvsweb.cgi?)
>
>* delete wiki pages (part of web-based admin?)

Perhaps just delete pages that have no text in them?  That way users delete 
pages by simply clearing the text?  I believe the current behavior is just 
to store a completely blank page which seems weird/wrong anyhow.

>* web-based (user) admin
>
>* common (XML) format for wiki metadata; standard for wiki bookmarks?

Perhaps the above should be two separate issues.  I can imagine different 
usages for both.

I'll take this opportunity to add:

Export static "snapshot" of wiki.  This would be a zip or tar.gz of static 
html files representing the wiki (with working relative links and the 
"dynamic" aspects disabled/removed).  A static shot would allow people with 
expensive connections (europe) or mobile people (laptop) to download all 
the wiki content at once and have it available for browsing.

extensive wiki statistics.  Pages, edits per month, # of members, size 
(MB), total outgoing links, total interwiki links, etc etc etc.  Most of 
its probably just foo-foo statistics but should be relatively easy to 
gather when doing one of your backups/snapshots since you'll be touching 
all the pages anyhow.  I'd be interested to see if we could get some useful 
numbers that correlate to the liveliness, freshness, connectedness, value 
or "knowledge content" of a wiki.  Mostly just something I'm interested in 
and has no immediate practical application that I can see.  (that's why its 
on the wish list).

>investigate/
>
>* TWiki-style tree structure to the Wiki for autogenerated directory pages
>
>* url-rewriting implementation for less implementation-dependent
>         bookmarking of wiki pages

File uploads?  Image uploads at least?  It's a common request although I 
think fraught with peril.

Link maps/site maps/graphical representations of the wiki.  I think 
navigation and finding info in the wiki is its greatest weakness so 
providing as many alternative ways to get around in it will probably add 
significant value to the wiki.

-iain