Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 2E5F82E0083 for ; Thu, 12 Jun 2008 11:26:31 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 27981-02 for ; Thu, 12 Jun 2008 11:26:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from vms173001pub.verizon.net (vms173001pub.verizon.net [206.46.173.1]) by developer.postgresql.org (Postfix) with ESMTP id 0D3952E0082 for ; Thu, 12 Jun 2008 11:26:27 -0300 (ADT) Received: from ridley.home ([71.179.5.175]) by vms173001.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K2C00366TFZ9GU7@vms173001.mailsrvcs.net> for pgsql-www@postgresql.org; Thu, 12 Jun 2008 09:26:24 -0500 (CDT) Date: Thu, 12 Jun 2008 10:26:20 -0400 From: Robert Treat Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org In-reply-to: <1213240845.1068.111.camel@jd-laptop> To: "Joshua D. Drake" Cc: pgsql-www@postgresql.org, Dave Page , Stefan Kaltenbrunner , Magnus Hagander , josh@agliodbs.com Message-id: <200806121026.21074.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-15 Content-transfer-encoding: 7bit Content-disposition: inline References: <200806091539.00540.josh@agliodbs.com> <200806112258.12540.xzilla@users.sourceforge.net> <1213240845.1068.111.camel@jd-laptop> User-Agent: KMail/1.9.9 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/107 X-Sequence-Number: 15334 On Wednesday 11 June 2008 23:20:45 Joshua D. Drake wrote: > On Wed, 2008-06-11 at 22:58 -0400, Robert Treat wrote: > > On Tuesday 10 June 2008 03:58:40 Dave Page wrote: > > > I'm not convinced that merging them is such a hot idea anyway. It will > > > likely seriously reduce the amount of time any announcement gets front > > > page time which will in turn reduce the usefulness of the section. > > > Further, we then have a potential problem ensuring we don't get > > > duplicate items when one gets approved on www and subsequently on > > > pgFoundry. That of course, applies whether we merge the feed with the > > > existing news, or add it as a new section (ignoring the layout issues > > > that would involve!) > > > > The other concern that I have is that this gives even less face time to > > core project related news, which already has a hard time getting > > exposure. Things like minor releases, project events (beta/gsoc), and > > large community gatherings (oscon/pgcon) get at best limited exposure and > > that's if aren't just lumped in with everything else. > > OSCON and PGCON are responsible for their own promotion. As pgfoundry is > an official PostgreSQL supported project, it deserves more face time > than either of those two. One option would be to have: > Thats the kind of thinking that helps keep the postgresql community small. We should be promoting those events that rally our existing community and help raise exposure for Postgres outside of the community, no matter who runs them. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL