RE: Future of the cookbook

Noel Welsh wrote:
> Moshi doesn't currently run under Apache.  It could be
> modified to do so but that would be substantial work.
> I'll ask the PLT folk if they'll host it.  We
> discussed something similar in the past but never
> quite finalised everything.

I'm willing to host Moshi for this purpose on one of my servers.  Since it
already runs Apache, Moshi might have to use a port other than 80, although
I may be able to get around that using a DNS alias - I'll look into that.

I also already have the Twiki wiki set up on the server in question:
http://shizuku.appsolutions.com/twiki/bin/view/Main/WebHome

That's the default, uncustomized interface, don't let it put you off - it
can be customized to our heart's content, it's just HTML, stylesheets and/or
wiki content using wiki shorthand.

Twiki is a revision-controlled wiki, so changes can be monitored, rolled
back, etc.  There's user security so that only users with accounts can edit,
which also means that changes are associated with the person that made them.

Despite my desire to eat our own dog food and use Moshi, I think revision
control is pretty important for a shared project like this.  There's also a
lot of other functionality in Twiki.  For more, see:

http://shizuku.appsolutions.com/twiki/bin/view/TWiki/WelcomeGuest

...which has links to other intro and reference material.  I should warn
anyone of delicate constitution that the implementation language for Twiki
is Perl.  That shouldn't affect users, though.

I have no problem hosting Moshi as well, though.

I have no idea whether Twiki is appropriate for collective book authoring,
i.e. I'm not sure if other wikis have better features for this purpose, it's
not something I've ever looked at.

I don't want to jump the gun and create a Twiki area for Schematics unless
others like the idea: let me know if I should do that.  Twiki is organized
into named "webs", so we could name a web 'Cookbook', unless we want to go
for the more general 'Schematics', or both (with the latter being for
non-cookbook material).

BTW, longer term, perhaps a good idea would be for schematics to have its
own domain name.  If I host this, I can give it a name in one of my domains,
like schematics.appsolutions.com etc., but to support server portability in
future, having its own name might make sense.  Unfortunately I see that
schematics.org and .net is taken, not surprisingly.  I haven't searched for
any others.

Anton



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click