Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 616202E0064 for ; Thu, 12 Jun 2008 22:28:37 -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 39925-09 for ; Thu, 12 Jun 2008 22:28:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by developer.postgresql.org (Postfix) with ESMTP id 87A262E005B for ; Thu, 12 Jun 2008 22:28:33 -0300 (ADT) Received: from ridley.home ([71.179.5.175]) by vms173005.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K2D00MR8NS4YI83@vms173005.mailsrvcs.net> for pgsql-www@postgresql.org; Thu, 12 Jun 2008 20:21:42 -0500 (CDT) Date: Thu, 12 Jun 2008 21:28:19 -0400 From: Robert Treat Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org In-reply-to: <200806121446.40725.josh@agliodbs.com> To: pgsql-www@postgresql.org, josh@agliodbs.com Cc: "Joshua D. Drake" , Dave Page , Stefan Kaltenbrunner , Magnus Hagander Message-id: <200806122128.19999.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> <200806121450.54231.xzilla@users.sourceforge.net> <200806121446.40725.josh@agliodbs.com> User-Agent: KMail/1.9.9 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/118 X-Sequence-Number: 15345 On Thursday 12 June 2008 17:46:38 Josh Berkus wrote: > > 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. > right, but based on the stats, it's one of the things that draws a lot of visitors, so I think that counts for something. > > 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? More focus on core announcements / events, regular pug promotion, highlighting large community events, and sorting out training (which most seem to agree is sub-optimal) -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL