Re: [Firebird-docs] Where to place FlameRobin documentation

[Nando D. <na...@de...>]

Paul,

P> That said, if you like our doc build system, why not copy it to the FR
P> project (that's what it's Open Source for) and use it for your docs
P> (the DocBook sources of which would be committed to FR's CVS tree) ?

that's a lot of stuff; I'm a bit concerned about duplicating
everything (and keeping it in sync). OTOH if someone else needs to
contribute documentation to FR (unlikely, for now) (s)he should be
able to checkout everything needed from the FlameRobin CVS tree...

P> Your top level node should IMO be a <book>: FR documentation covers
P> "only" one tool, so no need for a <set> like with the Firebird docs.

I wanted to keep developer docs and user docs separated. As it looks
like we won't be using DocBook but wiki for developer docs, I agree
that a <book> is better suited.

P> By the way, if you alert us as soon as you guys feel that FR is mature
P> and robust enough for the average Firebird user, we can at least
P> include a link in the Quick Start Guide (along with links to other
P> usable frontends).

Don't worry - when FR is production ready you'll know it. ;-)

Ciao
-- 
Nando Dessena
mailto:na...@de...