| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>, pgsql-www <pgsql-www(at)postgreSQL(dot)org> |
| Subject: | Re: What do we need for new PUGs? |
| Date: | 2015-03-04 18:38:49 |
| Message-ID: | 20150304183849.GN3291@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-www |
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.]
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.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-03-04 19:20:41 | Re: [pgsql-advocacy] What do we need for new PUGs? |
| Previous Message | Jonathan S. Katz | 2015-03-04 16:24:18 | Re: What do we need for new PUGs? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-03-04 19:20:41 | Re: [pgsql-advocacy] What do we need for new PUGs? |
| Previous Message | Jonathan S. Katz | 2015-03-04 16:24:18 | Re: What do we need for new PUGs? |