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

Guys,

> Special attention should be limited specifically to community. That is
> how you are going to drive a larger community, by reinforcing the
> community itself. Not by becoming advertising space.

Can we *please* get back on topic here?  Absolutely none of this is relevant 
to a pgfoundry feed.

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?

The pgfoundry team can easily regulate the volume of pgfoundry traffic that 
gets passed on.

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco