discuss: August summary
Subject:
Re: [discuss] August summary
From:
jdd ####@####.####
Date:
13 Oct 2005 15:18:38 -0000
Message-Id: <434E7ACC.6040502@dodin.org>
Randy Kramer wrote:
> I'd be hesitant about prodding the host (ibiblio(sp?)) to install a wiki
> until:
> * there is some agreement on which wiki
> * there is somebody willing to put the document on the wiki
> * there is a document chosen for the purpose
>
> There is no sense "prodding" anyone if there is not some certitude about
> subsequent followup.
+1
>
> Also, I'm not sure, would ibiblio actually install the wiki or simply give us
> (someone) the necessary permissions and so forth to install it ourselves.
probably give permissions
>
> Although I don't know when I'd have the knowledge or time to do it, my
> preference would be TWiki.
it's up to you. I can use tkwiki, but don't want to manage
it, I don't want to learn too many wikis.
I know that:
> * a new release of TWiki is imminent (sp?)
> * TWiki has a fair number of dependencies
???
meiawiki installs in nearly any config - i I could do on my
own server it can be done anywhere :-)
no root account needed, only mysql access
mediawiki is on 1.5 stable now since some days
> If jdd wants to install his preferred wiki (is that MediaWiki?), I can live
> with that, but may not be as active in adding the original content (as I am
> not proficient in MediaWiki).
to be clear, I won't be active to add any content out of my
own HOWTO (except basis, that is to say home page, basic
management).
to be of any interest, a wiki must be a self running app .
it only needs a dayly survey of the "recent changes" page.
If active, any user will warn in case of vandalism.
a dayly backup is also usefull.
jdd
--
pour m'écrire, aller sur:
http://www.dodin.net
http://valerie.dodin.net
http://arvamip.free.fr
