From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-www@postgresql.org
Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
Date: Thu, 12 Jun 2008 14:46:38 -0700
User-Agent: KMail/1.8
Cc: Robert Treat <xzilla@users.sourceforge.net>,
	"Joshua D. Drake" <jd@commandprompt.com>, Dave Page <dpage@pgadmin.org>,
	Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>,
	Magnus Hagander <magnus@hagander.net>
References: <200806091539.00540.josh@agliodbs.com>
	<200806121022.18339.josh@agliodbs.com>
	<200806121450.54231.xzilla@users.sourceforge.net>
In-Reply-To: <200806121450.54231.xzilla@users.sourceforge.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200806121446.40725.josh@agliodbs.com>

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