Access to Mozilla Bugzilla Bug Data

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Administration
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: g-leijo, Assigned: mhoye)

Tracking

Production

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; InfoPath.3; .NET4.0C; .NET4.0E)

Steps to reproduce:

It would be beneficial to the computing research community in general to be able to do research on Mozilla bug data without having to scrape the bugzilla website. 



Expected results:

The Mozilla project could make a sanitized database dump of the Bugzilla bug data available for research.

Updated

5 years ago
Assignee: administration → nobody
Component: Administration → Administration
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
(Assignee)

Comment 1

5 years ago
Thanks for your interest. Once a permanent home for the Bugzilla data is found, I'll let you know.
Assignee: nobody → mhoye

Comment 2

5 years ago
As a volunteer Bugzilla developer, one issue I have is not having a decent sized database to play with. Even if it wasn't a copy of the actual Mozilla database, even a sanitised version of the landfill database would be very useful.

Regards,
Hugo
(In reply to Hugo Seabrook from comment #2)
> As a volunteer Bugzilla developer, one issue I have is not having a decent
> sized database to play with. Even if it wasn't a copy of the actual Mozilla
> database, even a sanitised version of the landfill database would be very
> useful.

i have an old copy of a sanitized landfill database. i'll contact hugo directly with the details.
(Assignee)

Comment 4

4 years ago
No permanent hosting found yet, but I'll redirect the people URL rather than updating lots of individual bugs. Closing resolved.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.