public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Rafael Martinez <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Documentation and explanatory diagrams
Date: Fri, 9 Jul 2010 20:01:55 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Rafael Martinez wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/03/2010 01:02 AM, Robert Haas wrote:
>
> >
> > Also, I think we need to review these images carefully before adding
> > any of them into our docs.
>
> I agree with this. I didn't want to use a lot time with the diagrams
> until everything is decided and we agree to have diagrams in the
> documentation.
>
> They are a proof of concept, different diagram types for different parts
> of the documentation. They all need to be reviewed if they are going to
> be used.
>
> If we go for having diagrams, we should:
>
> - - Create a TODO list with the diagrams we would like to have and where.
> - - Define a procedure and rules to send diagrams patches: how to send,
> review, give feedback, back to send and final commit.
> - - Define some guidelines about how to create a diagram, colors to use,
> key information, etc.
Where are we on this? Application? dia? xfig? Number of colors? Once
we decide these items, we can start adding diagrams.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
view thread (114+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Documentation and explanatory diagrams
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox