| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>, pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: [pgsql-www] What do we need for new PUGs? |
| Date: | 2015-03-06 08:56:42 |
| Message-ID: | CAKoxK+6yfLmD1dD9O0H431rOOjNnGQ8y+Mn7csVPEz_1qP_JyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-www |
On Wed, Mar 4, 2015 at 7:38 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Josh Berkus wrote:
>
>> So the question becomes: if what new PUGs need for infrastructure is not
>> new mailing lists, then what do they need?
>
> Have "PUG" be a new type of organization in the website database. Users
> (community accounts) can be marked admin of PUGs.
>
> Have "PUG events" be a new type of event in the website database.
> Admins of PUGs can post new PUG events [, without requiring moderation.]
>
Being new objects, could we define a little what we are expecting from a PUG?
> Show a box of the upcoming two or three PUG events somewhere in the front
> page of www.postgresql.org (maybe "Local events this week"); also have a
> link that opens a page listing all events in the next 30 days. Have a
> way to list all events of any individual PUG. Maybe steal space from
> "Latest News" for this.
I like this idea.
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikhil Sontakke | 2015-03-07 13:37:20 | Re: [pgsql-www] What do we need for new PUGs? |
| Previous Message | Joshua D. Drake | 2015-03-05 16:07:12 | Re: What do we need for new PUGs? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AWeber - Bob Lunney | 2015-03-06 18:38:00 | pgfoundry link for pgbouncer is dead |
| Previous Message | Craig Ringer | 2015-03-06 04:50:37 | git.postgresql.org commit hooks? |