Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44693 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12138 invoked from network); 4 Jul 2009 07:53:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jul 2009 07:53:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=sean@seanius.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=seanius@debian.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain seanius.net from 66.93.22.232 cause and error) X-PHP-List-Original-Sender: sean@seanius.net X-Host-Fingerprint: 66.93.22.232 cobija.connexer.com Received: from [66.93.22.232] ([66.93.22.232:58857] helo=cobija.connexer.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0F/D0-06257-A6A0F4A4 for ; Sat, 04 Jul 2009 03:53:15 -0400 Received: from rangda.stickybit.se (h-234-204.A189.priv.bahnhof.se [81.170.234.204]) by cobija.connexer.com (Postfix) with ESMTPA id 5D04B17C223; Sat, 4 Jul 2009 03:53:11 -0400 (EDT) Received: by rangda.stickybit.se (Postfix, from userid 1000) id B3DCF104CC; Sat, 4 Jul 2009 09:53:09 +0200 (CEST) Date: Sat, 4 Jul 2009 09:53:09 +0200 To: PHP Internals Cc: Sandro Tosi Message-ID: <20090704075309.GA29827@rangda.stickybit.se> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) Subject: are there alternate interfaces to the bug tracking system? From: seanius@debian.org (sean finney) --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hi everyone, (if there's a better place to ask this, my apologies and feel free to redirect me!) does anyone know here if there is any machine-friendly interface to the php bug tracking system? in debian we have a service called "bts-link"[1] which we can use to track "forwarded" bugs in remote systems's (i.e. a bug reported in debian which has been linked with another bug such as one on bugs.php.net). for debian package maintainers this is a major boon since we can keep better track of bugs that have been fixed or otherwise addressed "upstream". 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? thanks! sean [1] http://bts-link.alioth.debian.org/ ps - I'm cc'ing Sandro Tosi, who i believe could answer any questions you might have about the bts-link service in case you would only provide such access under certain conditions (he is not subscribed to this list). --=20 --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFKTwplynjLPm522B0RAhguAJ4tQrDPmBKYGoB3bUhP/qbb7QfaBQCdGT6E QrhCbMR9GQ7ygRA2X473fn4= =2EJT -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--