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

[Hermanni Hyytiälä]

On Tue, 2003-07-29 at 17:04, Tuomas Lukka wrote:
> > > 
> > > Why would wiki make a good starting point?
> > 
> > 1) Information categorization
> > We could categorize things under different categories with links (e.g.,
> > "Tutorials", "Terms", "Best practices", "Documentation",
> > "Tutorials/Fenfire project", "Tutorials/Subprojects", "Best
> > Practices/LibVob", "Best Practices/Design Patterns" "Best
> > Practices/Avoid these things", "Terms/Xanalogical model", "Terms/3D
> > programming" &c).
> > 
> > 2) Familiar interface
> > People are able to use familiar interface for viewing information, i.e.,
> > their favourite web browser.
> 
> What advantages does wiki have w.r.t. rst for either of those?
> 
> 1) This is about structuring information, not about wiki vs rst.
> 
> 2) .rst goes into html


Using different programs (i.e. interfaces) for structuring information
(editor <-> rst) and for viewing information (browser <-> html); with
wiki there's only one program for these tasks.


> 
> > > I'd think we should use .rst for those things.
> > 
> > If .rst files can do categorization then it should be fine ;).
> > 
> > > 
> > > For Wiki, the main use I see is "running commentary", i.e.
> > > "X is broken, you need to do Y right now to accomplish it" &c
> > > Anything permanent should probably be on the rst side.
> > 
> > Indeed. Wiki should *not* store anything permanent (i.e. official)
> > documents. As said, wiki would only act a starting point/quick ref place
> > where information is categorized with links to official documents for
> > more detailed (official information) information.
> 
> Why?

Starting point:
For people who join to our research group, or our own people how move
from one subproject to an another: people get started with their tasks
more quicly since there is more "mandatory" information what they should
know before doing anything.


-Hermanni