Minnow WIKI Migration
bert at freudenbergs.de
Mon Oct 23 08:46:41 UTC 2006
Has Pier solved the persistency issue? Holding all data in image is
*not* acceptable for real deployment. That is why Michael pointed out
impara's Smallwiki version that puts everything into an external file
- Bert -
Am 23.10.2006 um 05:59 schrieb J J:
> I would say go to Pier. I think Kieth released some software that
> you can point at the swiki and it will slurp it all up. Am I right
>> From: Matthew Fulmer <tapplek at gmail.com>
>> Reply-To: The general-purpose Squeak developers list<squeak-
>> dev at lists.squeakfoundation.org>
>> To: squeak-dev at lists.squeakfoundation.org, guzdial at cc.gatech.edu
>> Subject: Re: Minnow WIKI Migration
>> Date: Sat, 21 Oct 2006 20:54:20 -0700
>> On Wed, Oct 18, 2006 at 01:04:12PM +0200, Bert Freudenberg wrote:
>> > >The wiki status is one of the agenda items of tonight's board
>> > >
>> > >http://lists.squeakfoundation.org/pipermail/squeak-dev/2006-
>> > >109791.html
>> > Right. But since the Board cannot order people to do something, it
>> > would need offers.
>> I'll offer. I will need the help of the web team.
>> How much interest is there in changing the Wiki engine? I have
>> encountered 3 obstacles in the Swiki setup (or at least, how it
>> works an the Minnow Swiki:
>> - no user-name based logging. It is very hard to translate the
>> computer names stored in the change log into who did the
>> - no easy rollback. It is possible, but not very convenient, to
>> roll-back a page to a previous state. One must copy and paste
>> the old text into the edit box.
>> - willy-nilly page locking. Many wiki engines only allow a
>> moderator to lock a page. In the Swiki, however, anyone can
>> lock a page and prevent rollback until an administrator comes
>> There are other, minor issues with the Swiki, but those are the
>> big ones.
>> A transition would most likely be a one or two phase process:
>> 1. Get the wiki off of the Minnow servers at Georgia tech.
>> (what about the other Swikis they host? Croquet?)
>> 2. If there is interest, translate the wiki database to another
>> format, most likely Magma + Pier.
>> I am not too familiar with Comanche or Seaside, but I am sure
>> they are easy enough to learn.
>> > TSTTCPW is to move the actual installation to our server. That
>> > take someone to work with the box admin team to do it.
>> Probably. Who are those people?
>> > Maybe we could even pursue the GA Tech folks to repoint their
>> > DNS entry to us - there's an awful lot of links on the web to
>> Mark: do you think this would be possible?
>> > I can see several other ways to continue, but none without severe
>> > drawbacks. All would require significantly more work, so there
>> > have to be volunteers to do it.
>> Well, I am volunteering. What are your other ideas?
>> Mark: please reply to squeak-dev at lists.squeakfoundation.org if
>> Matthew Fulmer
> Use your PC to make calls at very low rates https://
More information about the Squeak-dev