In article <[EMAIL PROTECTED]>, David A Golden wrote:
> At 6/29/2003 07:44 PM, Clint Moore wrote:
>>I dont mind either way. I've been working on Kwiki a lot lately and it's
>>what I use for just about everything.
>>
>>Anyway, I'll use whatever you guys decide.
>
> I kind of like Kwiki just because it is so simple, but the negatives are
> legitimate concerns. Who makes the call? Vote? Fiat? (Jesse! Help!)
LOL. Isn't this how it always happens? Nothing at all or all at once.
Without evaluating either project on it's code structure, I agree with
others that Kwiki is nice for it's simplicity.
However, I think Twiki has a more robust feature set and may serve us
better and scale for us better at the present. I'm personally inclined
towards putting my energy into the Twiki site.
It's great to see how much content has already appeared in the Kwiki
site just today. I can see that through collaboration, we can build
something significant and useful in a short term. With this quick pace
of progress, I think the email notification feature of Twiki will be
very nice.
I also like that it supports a syntax that allows your avoid CamelCase.
I'm not sure we need to make a decision as a group about choosing one or
the other. We can all try them both out, and eventually I think one will
become clearly the primary site.
Heck, we can even build on both sites as we choose and link between them
as appropriate.
Mark
--
http://mark.stosberg.com/
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
