Re: [Firebird-docs] Where to start?

[Paul V. <pa...@vi...>]

Hi Armando,

> I don't know how you have felt when you joined this list, but I feel
> a little confused about where should I start, maybe because I
> usually prefer to organise and plan things before starting do do
> them.
>
> It occurs to me a possibility which I'm no sure if you agree with
> it: maybe I could start with a TOC for the basic documentation so
> that we could discuss and refine it. From my point of view, when you
> have a TOC signaling what's to be done it's easier to choose what
> piece of documentation I would like to write next...

We made a rather informal to-do list last summer. If you point your
newsreader to news.atkin.com you may still find it. If it's expired I
can repost it.

We could make an updated version of this list. When it comes to
picking tasks, let's not forget:

- The Quickstart Guide will be coming our way soon (if Helen survives
  the conversion but I guess she will ;-)), so we don't have to write
  a beginners's guide - we only have to update it.

- After that, we'll also inherit Using Firebird, This is a big one, my
  initial thought is that we should split it up in several docs.
  Anyway, this too is a lot of material we don't have to write anymore.

- IBPhoenix will produce an API Guide/Reference and an SQL Reference.
  That doesn't mean that we can't do the same, but it seems more
  logical to concentrate on other tasks. After all, both require a lot
  of work and the IBPhoenix docs may not be free, but at least they will
  be there.

- One existing project that could use input is the Glossary.


Greetings,
Paul Vinkenoog