From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201007100001.o6A01to03428@momjian.us>
Subject: Re: Documentation and explanatory diagrams
In-Reply-To: <4C31966E.1020007@usit.uio.no>
To: Rafael Martinez <r.m.guerrero@usit.uio.no>
Date: Fri, 9 Jul 2010 20:01:55 -0400 (EDT)
CC: Robert Haas <robertmhaas@gmail.com>,
 pgsql-docs <pgsql-docs@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

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  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + None of us is going to be here forever. +