| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL WWW Mailing List <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: whatcom-pgsql |
| Date: | 2014-08-05 02:57:46 |
| Message-ID: | 20140805025746.GO5475@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Josh Berkus wrote:
> On 08/04/2014 12:04 PM, Alvaro Herrera wrote:
> > If the Whatcom community takes form, we
> > can certainly create a list later.
>
> Catch-22:
>
> A: Can't get a PUG started because no mailing list.
> B: Can't get a mailing list because no PUG started.
>
> This seems like something it's critical for us to resolve. Again, it's
> sounding like we need some kind of additional resources for "peripheral"
> mailing lists.
Well, I am not averse to creating a list if it has value. However, I
don't know that having the list is a prerequisite for a PUG getting off
the ground. Is it? Why do we create lists for PUGs that never see any
activity? Is there any way to stop these lists from being born in the
first place?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2014-08-05 03:30:48 | Re: whatcom-pgsql |
| Previous Message | Jonathan S. Katz | 2014-08-05 00:19:41 | Re: whatcom-pgsql |