I had meant to post my reply to the list... I'm used to just hitting reply
and sending it directly to the list. I would've kept it at that, but since
Vince felt he had to share, I thought I'd just post this as well.
Greg
> > > Then it goes right back to what someone else eluded to... If you
don't
> > > like what you see in the documentation, contribute. Send in diffs, or
> > > even new items. If you don't know what's needed go to the DOCS list
and
> > > ask. Getting people to help with documentation for ANY project is
like
> > > pulling teeth. Finding people to criticize existing documentation is
> > > quite easy.
> >
> > What a horrible chicken and egg scenario... you can't help with
providing
> > documentation until you have some deal of experience with something, but
if
> > you ask for better documentation to get that experience, you are told to
> > write some. I understand the frustration, but at the same time, please
> > understand the frustration of those trying to learn. Personally I find
the
> > documentation is more than adequate, but could always be improved.
Hopefully
> > I will learn enough at some point to be able to say that I'm ready to
> > contribute... until then I'll be here feeding off the scraps of
knowledge
> > that are dribbled here and there...
>
> You need to read things again 'cuze you completely missed the point.
I'm sorry, what was the point then? I thought your point was that people
should put up or shut up, to which I was trying to point out that it's not
that easy. Particularly since those who know enough to 'put up' are not
those who are having trouble with the current documentation. I'm not trying
to turn this into a "PostgreSQL's documentation sucks" war... merely
pointing out that it could use some improvement and those that are asking
for improvement are not necessarily those who are best suited to improve it.
If this was not the point you'll have to explain it in simpler terms because
obviously I'm too obtuse to understand.
Greg
