Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44694 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15306 invoked from network); 4 Jul 2009 08:22:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jul 2009 08:22:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.94.239.7 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.94.239.7 mail.jdi.nl Received: from [82.94.239.7] ([82.94.239.7:33841] helo=mail.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 89/61-06257-7411F4A4 for ; Sat, 04 Jul 2009 04:22:32 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.jdi-ict.nl (8.13.7/8.12.11) with ESMTP id n648MPOJ025991; Sat, 4 Jul 2009 10:22:25 +0200 X-Virus-Scanned: by amavisd-new at jdi-ict.nl Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.7/8.12.11) with ESMTP id n648M2w0025902; Sat, 4 Jul 2009 10:22:24 +0200 Date: Sat, 4 Jul 2009 09:22:03 +0100 (BST) X-X-Sender: derick@kossu.ez.no To: sean finney cc: PHP Internals , Sandro Tosi In-Reply-To: <20090704075309.GA29827@rangda.stickybit.se> Message-ID: References: <20090704075309.GA29827@rangda.stickybit.se> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (jdi.jdi-ict.nl [127.0.0.1]); Sat, 04 Jul 2009 10:22:24 +0200 (CEST) Subject: Re: [PHP-DEV] are there alternate interfaces to the bug tracking system? From: derick@php.net (Derick Rethans) On Sat, 4 Jul 2009, sean finney wrote: > 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? There is no such thing at the moment, but I wouldn't mind seeing a patch for this. regards, Derick -- http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org twitter: @derickr