Re: User documentation vs Official Docs

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "Psql_General (E-mail)" <pgsql-general(at)postgresql(dot)org>
Subject: Re: User documentation vs Official Docs
Date: 2018-07-16 23:55:28
Message-ID: 912e7bc9-7c85-846e-17dc-e605a09f130d@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 07/16/2018 03:37 PM, David G. Johnston wrote:
> On Mon, Jul 16, 2018 at 3:19 PM, Joshua D. Drake <jd(at)commandprompt(dot)com
> <mailto:jd(at)commandprompt(dot)com>>wrote:
>
> On 07/16/2018 03:14 PM, David G. Johnston wrote:
>>
>> What does the community think about a community run,
>> community organized, sub project for USER documentation? This
>> type of documentation would be things like, "10 steps to
>> configure replication", "Dumb simple Postgres backups",  "5
>> things to NEVER do with Postgres". I imagine we would sort it
>> by version (9.6/10.0 etc...) as well as break it down via
>> type (Administration, Tuning, Gotchas) etc...
>>
>> What do we think?
>>
>>
>> ​Politely tell them to buy some of the many well written books
>> that are available on these very topics...
>
> Politely tell them to buy a license to MSSQl...
>
> Kind of misses the whole point doesn't it?
>
>
> ​I'm going for practicality over idealism here.  That some of the best
> written material for learning how to be an application developer or
> DBA is presently really only available in the forms of books is a fact
> of our existence.  I frankly don't have a problem that there isn't a
> "free beer" resource available to complete with it.

Fair enough but what about those that cant afford it? I think us in the
Western World tend to forget that by far the majority of users cant
afford a latte from Starbucks let alone a 60.00 USD dead tree.

>
> I'm all for continual improvement but color me doubtful that there is
> enough desire and discipline here to invent and then maintain a
> high-maintenance system.  So, yes, I am intentionally trying to avoid
> the trap that is problem that you want to solve by suggesting
> forgetting the revolution and instead coming at the problem from an
> entirely different angle and working to evolve the equilibrium that
> presently exists.

Hey, don't get me wrong. I get your point but I also know what I hear
and I hear from *lots* of users because of PostgresConf and all the
meetups. I am just trying to resolve a problem that exists for that
community. Think of this (if we can figure out how to pull this off):
User on StackOverflow says, "How do I do X", someone answers with a
direct link to a recipe on PostgreSQL.Org that tells them exactly how to
do X (with caveats of course). There isn't much more user friendly than
that.

I am also not suggesting this wouldn't be work but it is also work a lot
more people can do than people that can submit a patch to -hackers
(exponentially so).

IMO,

JD

--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
*** A fault and talent of mine is to tell it exactly how it is. ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2018-07-16 23:56:51 Re: User documentation vs Official Docs
Previous Message Adrian Klaver 2018-07-16 23:33:26 Re: User documentation vs Official Docs