Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 97EE59FB783 for ; Fri, 13 Apr 2007 04:11:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 78983-02 for ; Fri, 13 Apr 2007 04:11:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id C5B179FA49B for ; Fri, 13 Apr 2007 04:11:15 -0300 (ADT) Received: by svr2.hagander.net (Postfix, from userid 1000) id DC7D8DCC800; Fri, 13 Apr 2007 09:11:14 +0200 (CEST) Date: Fri, 13 Apr 2007 09:11:14 +0200 From: Magnus Hagander To: Robert Treat Cc: pgsql-www@postgresql.org, josh@agliodbs.com Subject: Re: [pgsql-advocacy] Broken links in presskit Message-ID: <20070413071114.GC31884@svr2.hagander.net> References: <20070412135934.GE18546@svr2.hagander.net> <200704121336.32598.xzilla@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200704121336.32598.xzilla@users.sourceforge.net> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/71 X-Sequence-Number: 11821 On Thu, Apr 12, 2007 at 01:36:32PM -0400, Robert Treat wrote: > On Thursday 12 April 2007 09:59, Magnus Hagander wrote: > > Going through the logs on the new wwwmaster to find broken links, I noticed > > that almost every presskit for 8.2 contained broken links in them. Mainly > > to the sourceforge site (which missed sourceforge.net!) but also to > > regional sites, and to pages on our own site. > > > > Clearly, the verification of all the links in the presskits needs to be > > added to the presskit checklist (i assume there is one somewhere) for 8.3 > > and on. > > > > (I've fixed the links for now) > > Perhaps there should be some automated link checking for the postgresql > website? Taht's not a bad idea. I talked it over briefly with Dave yesterday, and we discussed doing it in the mirror script. This can probably be done, but it rquires some re-archtecturing of the mirror script (which may be needed anyway, as it's very inefficient somewhere - it represents about 98% of the CPU usage for a site build - compared to 2% for both the server-side PHP and the database server). That said, I *still* think we need better quality-control on the submitted press info, given that the mirror script can only tell that a link exists, not that it points to the correct place. //Magnus