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

From Vik Fearing
Subject Re: When should be advocate external projects?
Date
Msg-id 5733CE6E.6000900@2ndquadrant.fr
Whole thread Raw
In response to When should be advocate external projects?  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: When should be advocate external projects?  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-advocacy
On 05/12/2016 02:18 AM, Joshua D. Drake wrote:
> Hello,
>
> There has been a lot of back and forth about when we (as a community)
> should advocate external projects as well as where we should advocate
> external projects. It seems the more advocacy minded individuals would
> like to be more inclusive whilst the -hackers and old school folks don't
> want to bother with it at all (this is not exclusive, I know there are
> exceptions).
>
> I think we need to come up with some guidelines. I have my own ideas of
> what those should be:
>
>     * Must be released under an OSI approved license
>     * Must have source downloadable without barrier (no registration for
> example)
>     * Must have a way to file bug reports
>
> There are others but they may be controversial so I will leave them for
> now.

To avoid proliferation, I think we should also limit them by
exclusivity.  There are no other real contenders for the belts that
pgBadger, check_postgres, and pgAdmin hold, so all of those should be
promoted.

That could perhaps be extended from one to two, which would allow us to
promote both PgBackRest and Barman.
--
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-advocacy by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: When should be advocate external projects?
Next
From: "Joshua D. Drake"
Date:
Subject: Re: When should be advocate external projects?