Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 1D7DC2E0091 for ; Tue, 10 Jun 2008 04:36:41 -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 89547-10 for ; Tue, 10 Jun 2008 04:36:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from cronos.madness.at (madness.at [217.196.146.217]) by developer.postgresql.org (Postfix) with ESMTP id A69CE2E0082 for ; Tue, 10 Jun 2008 04:36:31 -0300 (ADT) Received: from congw.dc1.conova.com ([217.196.145.250] helo=[192.168.1.61]) by cronos.madness.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1K5yOu-0008Td-UM; Tue, 10 Jun 2008 09:36:20 +0200 Message-ID: <484E2F6A.4060605@kaltenbrunner.cc> Date: Tue, 10 Jun 2008 09:38:18 +0200 From: Stefan Kaltenbrunner User-Agent: Icedove 1.5.0.14eol (X11/20080509) MIME-Version: 1.0 To: Magnus Hagander CC: josh@agliodbs.com, pgsql-www@postgresql.org Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org References: <200806091539.00540.josh@agliodbs.com> <484E24FE.1050807@hagander.net> In-Reply-To: <484E24FE.1050807@hagander.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/58 X-Sequence-Number: 15285 Magnus Hagander wrote: > 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). yeah - rss feed is the way to go if we want this > > 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...) iirc the pgfoundry main page news are already moderated - but we would still have to find a solution to the integration problem. Stefan