RE: Re: [bigloo] bigloo wiki

Christian Jaeger wrote:
> I don't know the different wiki implementations well,
> and I've only ever set up an Axkit Wiki ever myself.

I should mention that for schemewiki.org, we didn't do a comprehensive
survey of wikis and CMS systems.  TWiki seemed to have a few key features we
wanted, and I was already familiar with it when the Schematics Cookbook
project needed a solution.  To some extent, it was chosen because we didn't
know of anything better-suited to the task.  I think that's still the case
now.

> These are the thoughts I have
> about the subject:
>
> - the wiki should offer ways to prevent from destructive
> edits / link spamming activities. Versioning is thus required,
> and it's offered by TWiki; additionally, either a notification
> email with easy undo capability should be sent to some wiki
> content maintainer (I would not recommend this, from what I've
> read the AxKit.org wiki maintenance did turn out to be too much
> work)

TWiki has a built-in feature for emailing a summary of changes to users who
sign up for such notifications.  Change emails are sent at specified times,
with all changes since the previous email batched in a single message.  No
email is sent if there are no changes.

I don't think this feature is configured on the schemewiki.org site right
now, but it's easy to set up.  I've used it on intranet sites.

There's also an RSS capability, so you can use any RSS reader or content
aggregator to monitor the most recent changes.  There's an RSS link on the
Schematics Cookbook home page.

> or there should be
> authentification of users (which is done in the schematics
> cookbook wiki, albeit without checking the validity of the
> given email address). Probably it's ok the way Anton did
> set it up.

I used the default TWiki authentication setup.  When a user registers, a
confirmation email is sent to the user, and a copy is sent to the site
administrator (me, for schemewiki.org).  If the user's confirmation email
bounces, the adminstrator should see that.

An advantage of requiring users to log in to make changes is that even if
they don't sign their changes, their username is recorded in the version
history for that page.  Each page has a "Diffs" link at the bottom which
displays the version history.  This makes it possible to figure out what's
happened and ask the author(s) about it when a change is made that doesn't
seem to make sense.  It reduces the potential for "wikifights" where someone
deletes something, the original author puts it back, and so on...

> - I think there should be the possibility to get at the wiki content
> sources (files/db dump/whatever), in case somebody ever wanted to
> move it to anoter wiki or host (be it for just trying out another
> wiki implementation). Someone (Anton?) assuring to send them on
> request should be enough.

No problem.  I can set up FTP access to the directories in question.

If it would be helpful, I'd be happy to set up a Bigloo area on
schemewiki.org for testing & experimentation.  Otherwise, if you want to
experiment with TWiki features, you can do it in the "sandbox" at:
http://schemewiki.org/bin/view/Sandbox/WebHome

Anton



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504