[Asterisk-Users] Wiki TOS - worrying for an open source project?

[James H. Thompson]

----- Original Message ----- 
From: "Steven Critchfield" <critch at basesys.com>
To: <asterisk-users at lists.digium.com>
Sent: Friday, May 28, 2004 5:11 AM
Subject: Re: [Asterisk-Users] Wiki TOS - worrying for an open source project?


> On Fri, 2004-05-28 at 08:37, Andrew Kohlsmith wrote:
>
> Please do not trim out attribution tags.
> The double quoted is from Julien Levi <jules at jlevi.co.uk>
>
> > > What worries me most is that the current terms seem crafted so as to
> > > ensure that should the people who run voip-info ever decide to remove
> > > content, or stop hosting the wiki, it couldn't be mirrored anywhere else.
> >
> > Untrue.  Their terms about relinking or republishing are for COMMERCIAL use,
> > unless I'm misreading something here.
>
> The other part is that a wiki is really unmirrorable using normal
> methods of mirroring a site. You need to just run the same software and
> have the database behind it mirrored. I'm sure if the wiki is running a
> new enough version of mysql, and the admin is willing, you could set up
> a mirror of the database and then set up a full on replication. Mysql
> supposedly supports replication, might want to put it to some use.

I've have no problem with mirrors of the wiki -- my only issue is the effort and time it will take
to set it up.

Mysql replication is usually setup as a one way process (i.e. updates to the replicated copy don't
automatically flow back to the master copy).  This would require that the wiki software be modified
to make the dynamically generated pages have URLs for reading that point at  the mirror, and URLs
for updating that point to the master site.  Another approach would be to modify the wiki software
to send Mysql read requests to the mirror Mysql server, and udpates to the master Mysql server.

Another issue for anyone wanting to setup a mirror is that the wiki software does a large number of
Mysql queries per page displayed.  The system is averaging over 100 queries a second and peaking
higher the last time I checked.

There is also a privacy issue, the DB currently has all of the registration infomation (passwords,
etc) for users, I think that part probably shouldn't be mirrored, but making the software work
without this may require modifications.

As an alternative,
I'd suggest the possibility of doing an HTML mirror using search engine like traversal of the site,
and manipulation of the embedded URLs to keep reads on the mirror, and sending updates to the
original site.  I believe there are existing tools to do this.

Jim
support at voip-info.org