← Back to team overview

launchpad-dev team mailing list archive

Re: Releasing bug data for research


On Thu, Feb 14, 2013 at 12:00 PM, Jonathan Lange <jml@xxxxxxxxx> wrote:
> On Wed, Feb 13, 2013 at 4:43 PM, Gavin Panella <gavin.panella@xxxxxxxxxxxxx>
> wrote:
>> On 13 February 2013 16:32, Jonathan Lange <jml@xxxxxxxxx> wrote:
>> > On Thu, Jan 31, 2013 at 1:09 PM, Jonathan Lange <jml@xxxxxxxxx> wrote:
>> >>
>> >> Hello,
>> >>
>> >> I was wondering whether I could convince Launchpad to make its public
>> >> bug data available in some kind of downloadable blob.
>> >>
>> >> All of this information is available via the public API, but would
>> >> take a very long time to gather. Making the data available could allow
>> >> researchers & interested people with a copy of RStudio to come up with
>> >> insights into FOSS development.
>> >
>> >
>> > I should point out that I'm not asking for any data that isn't publicly
>> > available already. I'm just asking for someone to run a coouple of
>> > queries
>> > and stick a tarball on a webserver, to spare me writing a script that
>> > trawls
>> > the API for the same information.
>> So much of Launchpad's visibility and access policy is defined by
>> security adapters, in Python, that it would make writing a query to
>> grab public bug data a fairly hard thing to do correctly. Right now
>> the best solution is probably to go through the API :-/
> Thanks for replying!
> Why wouldn't this work?
>   SELECT * FROM Bug WHERE information_type = 1
> Plus some more queries with joins to get the full info.

Hi, jml. Sorry it took one of us awhile to reply. There's not many of
us on Launchpad anymore. :)

So just to jump in here, it's not actually that simple. There
shouldn't be any public bugs on proprietary projects, but we'd want to
do some other checks to be safe we don't leak something like a
proprietary project name somewhere else in the data. I'd be really
nervous about doing this without being very careful in crafting the


Deryck Hodge
Engineering Manager, Cloud Engineering
Canonical Ltd.

Follow ups