| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, "Nasby, Jim" <nasbyj(at)amazon(dot)com>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Maliing list request: pgsql-forks@ |
| Date: | 2019-08-07 10:08:16 |
| Message-ID: | 2907afd9-a577-1047-7e1d-48a2744f018c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 2019-07-30 15:41, Magnus Hagander wrote:
> On that note, I'd be a +1 for "pgsql-extensions" as it would
> certainly
> help facilitate above suggested communication. It would be all
> encompassing of extensions, forks, etc.
>
>
> Sounds like a better name and focus.
>
>
> +1.
>
> I think the other part is, what would be the "level" of focus. Is this
> for people building the extensions, or people using them? If it's for
> people working on them, perhaps it should be pgsql-extensions-hackers or
> similar, to make that clear?
My interpretation of those names involving "extension" would be that
that is a mailing list where the authors of plr, orafce, and ip4r hang
out and discuss battling the idiosyncrasies of pgxs. Which might be
useful (probably not), but it's totally not what this mailing list
proposal is meant for.
I'm personally not opposed to pgsql-forks, but I see that this name
could be contentious. How about something like pgsql-derived-hackers?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nasby, Jim | 2019-08-07 20:02:59 | Re: Maliing list request: pgsql-forks@ |
| Previous Message | Ian Barwick | 2019-08-07 01:50:01 | Re: Typo in the "unsupported version" notice |