Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id BBF4F2E0056 for ; Tue, 10 Jun 2008 03:53:56 -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 51145-07 for ; Tue, 10 Jun 2008 03:53:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by developer.postgresql.org (Postfix) with ESMTP id 325A82E004D for ; Tue, 10 Jun 2008 03:53:53 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 518F5DCC126; Tue, 10 Jun 2008 08:53:51 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mha-laptop.hagander.net (Postfix) with ESMTP id 8B146124230; Tue, 10 Jun 2008 08:53:50 +0200 (CEST) Message-ID: <484E24FE.1050807@hagander.net> Date: Tue, 10 Jun 2008 08:53:50 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: josh@agliodbs.com CC: pgsql-www@postgresql.org Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org References: <200806091539.00540.josh@agliodbs.com> In-Reply-To: <200806091539.00540.josh@agliodbs.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/57 X-Sequence-Number: 15284 Josh Berkus wrote: > WWW team, > > In an effort to make PostgreSQL accessory projects more visible, I'd like > to start including the newsbytes from the pgfoundry main page in the > www.PostgreSQL.org news ticker. Probably the best way to do this is > direct database pull. Anyone have time to hack something up? > > Also, any reason not to do this? Just so you know, I do edit the newsbytes > for relevance and brevity. I would not like to add a direct dependency on the pgfoundry database, given the track record that pgfoundry has for uptime. I'd like to see some kind of RSS feed, because we already deal with caching of them there. That way, the main website will survive the regular pgfoundry outages (at worst it'll cache an empty file, and leave the pgfoundry list empty). Oh, and you need to figure out a way to integrate it nicely: see thread of a couple of days ago about adding more stuff to the frontpage. (No, I don't think mergeing it it with the "main news" functionality is a good idea - at least not unless we moderate it...) //Magnus