From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-www(at)postgresql(dot)org |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: Proposal: pulling newsbytes from www.pgfoundry.org |
Date: | 2008-06-12 21:46:38 |
Message-ID: | 200806121446.40725.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Robert,
> pug information
Where?
> As I see it, promoting core information should be our largest priority,
> which would include the top two items.
>
> our next priority should be promoting postgresql to the general
> populations, which would include large event and pug informations.
>
> after that we have service level information, which is projects,
> products, and training.
>
> now, I left out blogs because they are kind of across the map as far as
> content, but based on popularity of them, they should probably be held
> high on the list, I'd say somewhere below large event information but
> above pugs.
Hmmm. I'd put blogs lower on the list just because their content is less
vetted.
> looking that list over, istm just aggregating pgfoundry and our current
> news feed is the way to go, but there are still a number of areas that
> should be addressed, imho.
Which areas?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2008-06-13 01:28:19 | Re: Proposal: pulling newsbytes from www.pgfoundry.org |
Previous Message | Robert Treat | 2008-06-12 18:50:53 | Re: Proposal: pulling newsbytes from www.pgfoundry.org |