Re: When should be advocate external projects? - Mailing list pgsql-advocacy

From Joshua D. Drake
Subject Re: When should be advocate external projects?
Date
Msg-id 5734C8ED.3030703@commandprompt.com
Whole thread Raw
In response to Re: When should be advocate external projects?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: When should be advocate external projects?
List pgsql-advocacy
On 05/12/2016 08:54 AM, Adrian Klaver wrote:
> On 05/12/2016 08:44 AM, Robert Haas wrote:
>> On Thu, May 12, 2016 at 11:30 AM, Magnus Hagander

>> Sure, that kind of idea.  I'd forgotten we had that.  I think that we
>> should go to a format with just one line for each piece of software,
>> though, instead of a big box.  And try to get it all one one page.
>> And remove all of the proprietary products or put them in a separate
>> section.  And include only stuff that's actually reasonably widely
>> used.
>
> This is the part I see is going to be the biggest problem, who is going
> to curate this stuff? As you mention below the information is of dubious
> value as it stands now. While the idea of including third party stuff on
> the site is noble, I have yet to see an actual plan to ensure that it is
> handled in a timely manner and with accuracy.

There are several different ways to make sure this stuff is curated
correctly but that isn't the problem. At least not the immediate one.
The problem is a lack of leadership driving the content.

Any project whether documentation, code, web, social etc... without
leadership is destined to fall by the wayside due to people focusing on
other things.

Sincerely,

JD



--
Command Prompt, Inc.                  http://the.postgres.company/
                         +1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.


pgsql-advocacy by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: New versioning scheme
Next
From: Alvaro Herrera
Date:
Subject: Re: New versioning scheme