Re: When should be advocate external projects?

On 05/12/2016 02:16 PM, Bruce Momjian wrote:
> On Thu, May 12, 2016 at 02:15:15PM -0700, Joshua Drake wrote:
>> On 05/12/2016 02:02 PM, Justin Clift wrote:
>>> On 12 May 2016, at 21:58, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>>> On Thu, May 12, 2016 at 09:46:25PM +0100, Justin Clift wrote:
>>>>> On 12 May 2016, at 21:24, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>
>>>>>> I think our wiki page that lists all the FDWs is great, so why can't we
>>>>>> do this for other external software?
>>>>>>
>>>>>> https://wiki.postgresql.org/wiki/Foreign_data_wrappers
>>>>>
>>>>> That page does seem well put together. Guess the main question now is
>>>>> "who will drive this initiative?"
>>
>> IMO:
>>
>> A much better solution is to rework the software catalogue to properly
>> highly open source "projects" versus "products" and allow people to manage
>> via a moderated interface their own listings. It will be consistent, provide
>> a central place within the primary domain and be lower overhead than a wiki.
>
> The nice thing about a wiki is anyone can go in and improve it.

Agreed but I think that is a downside here. Keep in mind we have a
locked down wiki that we only allow update if you ask edit permission.

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.