Re: Wiki madness

Simply because there are bigger fish to fry.  The Wiki is a tool that looks 
like it'll be 'good enough' for OSAF's needs.  OSAF shouldn't get bogged 
down in creating the perfect collaboration tool at the sacrifice of moving 
the product development/architecture forward.

I understand the issues about the current OSAF Wiki, but the system seems to 
provide a good enough platform to get collaboration going, despite it's 
limitations.

My thoughts are that we need to keep our eyes on the goal --> Chandler 
Design/Development.  The Wiki is just a tool.

Lastly, if this is such a major issue I suspect that someone in the OSAF 
community to create their own Wiki (Wikipedia, etc) and get OSAF to provide 
a link to it.

  --Jim


>On Mit, 2003-01-15 at 18:38, Jim McCusker wrote:
> > Agreed.  Sometimes you have to bite the bullet, make a decision and go 
>with
> > it.
>
>Why?
>
>Regards,
>
>Erik
>--
>FOKUS - Fraunhofer Insitute for Open Communication Systems
>Project BerliOS - http://www.berlios.de
>
>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
>Open Source Applications Foundation "Process" mailing list
>http://lists.osafoundation.org/mailman/listinfo/process


_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Process" mailing list
http://lists.osafoundation.org/mailman/listinfo/process