Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45114
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.211.173 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:cc:content-type
         :content-transfer-encoding;
        b=lhNNycATkGR+0zEfJBE+0/aGt8T3LtUtTs7qz5ifmrX0UDvzfg0T5WsbGFRx7dAAUd
         SdlVg1qBJ9hguiCZZxjgukWPWjNx7L03KiYMl6segvfyyAWc/z+CBywsVLxrn8Ou+aTP
         3bcVg6/mszY9SiBousUbRDFoX2+/psf/2d57k=
MIME-Version: 1.0
Sender: matrixhasu@gmail.com
In-Reply-To: <8b2d7b4d0907040932k225da594u3ef8b4f2fd0a7a20@mail.gmail.com>
References: <20090704075309.GA29827@rangda.stickybit.se> <134AAF02-5938-4F07-AF86-D9C6EC982ABD@caedmon.net> 
	<8b2d7b4d0907040932k225da594u3ef8b4f2fd0a7a20@mail.gmail.com>
Date: Tue, 28 Jul 2009 10:38:38 +0200
Message-ID: <8b2d7b4d0907280138o173d9c8ck267b44d96aa45485@mail.gmail.com>
To: Sean Coates <sean@caedmon.net>
Cc: sean finney <seanius@debian.org>, PHP Internals <internals@lists.php.net>, 
	bts-link-devel@lists.alioth.debian.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] are there alternate interfaces to the bug tracking 
	system?
From: morph@debian.org (Sandro Tosi)

On Sat, Jul 4, 2009 at 18:32, Sandro Tosi<morph@debian.org> wrote:
> Hi all,
>
> On Sat, Jul 4, 2009 at 18:20, Sean Coates<sean@caedmon.net> 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.ne=
t
>>> bts
>>> that could be used to get a bug's information? =A0or would such a bts-l=
ink
>>> service need to resort to scraping the page for a particular bug's stat=
us?
>>
>> Not sure if this really helps you (and I agree that the bug system reall=
y
>> 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=3D46944
>> becomes:
>> http://bugs.php.net/rss/bug.php?id=3D46944
>
> yeah, I'll probably follow this way, but using the format=3Dxml parameter=
:
>
> http://bugs.php.net/rss/bug.php?format=3Dxml&id=3D46944
>
> that seems better for programmatical parsing.

FYI: I've implemented the parsing using the rss xml ouput. In case
some development is done on this side, please keep me in the loop :)

Cheers,
--=20
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi