Date: Thu, 12 Jun 2008 14:50:53 -0400
From: Robert Treat <xzilla@users.sourceforge.net>
Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
In-reply-to: <200806121022.18339.josh@agliodbs.com>
To: pgsql-www@postgresql.org
Cc: Josh Berkus <josh@agliodbs.com>, "Joshua D. Drake" <jd@commandprompt.com>,
	Dave Page <dpage@pgadmin.org>,
	Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>,
	Magnus Hagander <magnus@hagander.net>
Message-id: <200806121450.54231.xzilla@users.sourceforge.net>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <200806091539.00540.josh@agliodbs.com>
	<1213290175.11470.94.camel@jd-laptop>
	<200806121022.18339.josh@agliodbs.com>
User-Agent: KMail/1.9.9

On Thursday 12 June 2008 13:22:17 Josh Berkus wrote:
> First, I wasn't proposing merging pgfoundry news with *events* (which only
> has 3 slots) but with *news* (which has 6).  Right now, 3 of those slots
> are taken up by commercial products; don't you think it's fair that
> pgFoundry projects should bump them? If we have a problem with core 
> release announcements scrolling off too fast, isn't that a *code* problem
> for the WWW team to solve?
>

I think it is only a code problem once we decide on a policy we want to use. 
Right now we have a few different types of content we promote on the main 
page:

core release announcements 
other core specific news
project announcements
product announcements
training information
large event information
pug information
blogs

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. 

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. 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL