Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44698 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58040 invoked from network); 4 Jul 2009 16:20:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jul 2009 16:20:19 -0000 Authentication-Results: pb1.pair.com header.from=sean@caedmon.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=sean@caedmon.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain caedmon.net from 64.15.79.181 cause and error) X-PHP-List-Original-Sender: sean@caedmon.net X-Host-Fingerprint: 64.15.79.181 iconoclast.caedmon.net Received: from [64.15.79.181] ([64.15.79.181:52881] helo=iconoclast.caedmon.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/58-06257-0418F4A4 for ; Sat, 04 Jul 2009 12:20:17 -0400 Received: from localhost (localhost [127.0.0.1]) by iconoclast.caedmon.net (Postfix) with ESMTP id 90156784277; Sat, 4 Jul 2009 12:19:53 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at iconoclast.caedmon.net Received: from iconoclast.caedmon.net ([127.0.0.1]) by localhost (iconoclast.caedmon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XSafYaii9Ui; Sat, 4 Jul 2009 12:19:47 -0400 (EDT) Received: from [192.168.145.200] (modemcable036.174-130-66.mc.videotron.ca [66.130.174.36]) by iconoclast.caedmon.net (Postfix) with ESMTPSA id AF04378424A; Sat, 4 Jul 2009 12:19:47 -0400 (EDT) Cc: PHP Internals , Sandro Tosi Message-ID: <134AAF02-5938-4F07-AF86-D9C6EC982ABD@caedmon.net> To: sean finney In-Reply-To: <20090704075309.GA29827@rangda.stickybit.se> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sat, 4 Jul 2009 12:20:02 -0400 References: <20090704075309.GA29827@rangda.stickybit.se> X-Mailer: Apple Mail (2.935.3) Subject: Re: [PHP-DEV] are there alternate interfaces to the bug tracking system? From: sean@caedmon.net (Sean Coates) > so what i'm wondering is: is there an easily parseable or structured > interface (xmlrpc, soap, read-only JSON export, whatever) to the > php.net bts > that could be used to get a bug's information? or would such a bts- > link > service need to resort to scraping the page for a particular bug's > status? Not sure if this really helps you (and I agree that the bug system really needs some sort of better programmatic interface), but you can translate most bugs.php.net pages into rss (which is easier to parse than HTML... usually (-: ) by prepending rss/ to the URL. This useful for reading. For example: http://bugs.php.net/bug.php?id=46944 becomes: http://bugs.php.net/rss/bug.php?id=46944 and: http://bugs.php.net/search.php?boolean=0&limit=All&order_by=status&direction=ASC&cmd=display&status=Open&bug_type []=Documentation+problem&bug_age=0 becomes: http://bugs.php.net/rss/search.php?boolean=0&limit=All&order_by=status&direction=ASC&cmd=display&status=Open&bug_type []=Documentation+problem&bug_age=0 S