[Gzz] What is our Wiki for? (WAS: reST/Docutils Wiki and Navidoc)

[hemppah]

Ok, perhaps we should discuss more general about:

1) the content we want to store in our wiki
2) what is the function of wiki w.r.t our research group's communucation ways,
software development &c.

Once we have agreed a common "policy" (first discussing, then probably a PEG
document if needed) we can start creating content to wiki.

Currently, my personal opinion is that (as Tuomas cites below) wiki should be a
separate tool that should not be linked to every other tool we have (at least
not for now, maybe later if we found wiki useful).

Any suggestions?


-Hermanni

Quoting Tuomas Lukka <address@hidden>:

> On Mon, Jul 28, 2003 at 09:47:28PM +0300, Asko Soukka wrote:
> > Mon, 28 Jul 2003, Asko Soukka kirjoitti:
> > > ps. there will be problem with sync between ffdoc and wiki, without
> making 
> > >     changes to Navidoc, it could be solved by running doc-bot at  
> > >     himalia...
> > 
> > Hmm... this is necessary only, if we want to make references from ffdoc to
> 
> > Wiki. References only from Wiki to ffdoc won't need compiling 
> > documentations at Himalia.
> > 
> > Referring from ffdoc to Wiki brings also a yet another syncing problem.  
> > After modifying and compiling a single Wiki page, all implicit diagrams
> > added from ffdoc will disappear from that page. I see two solutions:
> > 
> >  - ffdoc is compiled at Himalia; implicit diagrams fron ffdoc to Wiki
> will
> >    reappear after next ffdoc run
> > 
> >  - after modifying a Wiki page, every diagram is checked for
> >    possible references to that particular Wiki-page
> 
> I see one more solution: *no* references from ffdoc to Wiki.
> Ffdoc is supposed to be standalone, right?
> 
>       Tuomas
> 
> 
> _______________________________________________
> Gzz-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/gzz-dev
> 




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/