public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Rafael Martinez <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Documentation and explanatory diagrams
Date: Tue, 13 Apr 2010 21:02:09 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Rafael Martinez wrote:
> > Given that's how the work is being done by community members right now,
> > I think you'd make better progress asking how to index the material in
> > those slides better and provide a hotlist of good slides on the Wiki.  I
> > consider fighting the battle to get the diagrams directly into the docs
> > the way it would need to be done to be both impractical and a waste of
> > resources, given many of these diagrams do already exist (and new ones
> > are constantly generated) if you follow the presentation scene.
> > 
> 
> I still think that the right place to have explanatory diagrams is in
> the official documentation and not a wiki or external document with
> pointers to other documents/presentations.
> 
> They would make some important parts of the documentation much more
> easier to understand. This is especially important for new users of
> PostgreSQL and users who are trying to get an overview of PostgreSQL in
> a evaluation process.
> 
> I know that most contributors have more than enough to do with the new
> release, and I don't want to create more work at this time. So maybe it
> will be better to fight this battle after 9.0 is released. :-)

OK, DIA sounds like it meets the requirements, and it would be good to
get some images into our documentation.  I wonder if it could import
some of my xfig diagrams;  if so, I could probably keep the images you
took from me updated in CVS.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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], [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