public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Treat <[email protected]>
To: [email protected]
Cc: Josh Berkus <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Cc: Magnus Hagander <[email protected]>
Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
Date: Thu, 12 Jun 2008 14:50:53 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<1213290175.11470.94.camel@jd-laptop>
	<[email protected]>

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

view thread (19+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox