Now that we'll have Firefox Input ( i.e. wiki.mozilla.org/Firefox/Input ) within our Beta Program, the reports that we'll be receiving from "Report a Broken Website" is now redundant. I'd like to archive it the site. So, let's set a timetable to archive this site once Firefox 4 Beta 1 goes live. The tentative date can be found here: https://wiki.mozilla.org/Firefox/4/Beta#Milestones
Then why does reporter still exist?
It's going to be removed from Firefox starting with Fx4 Beta 1.
If this means removal from mozilla-central, it means removal from both Firefox and SeaMonkey, FWIW.
Reporter has been identified as an abandoned site by the website taskforce. We are in the process of shutting down sites that are no longer used for security concerns. What are the remaining issues that need to be taken care of in order to retire reporter.mozilla.org?
Re comment #4, we need to contact the owner of the site. Based on the information on the site that is Robert Accetura, although that may be out of date. We should copy Robert on this bug -- does anyone here know his bugzilla account name? Re comment #3, if SeaMonkey still uses Reporter perhaps they want to update and maintain it and move this from an inactive site to an active site?
SeaMonkey has removed reporter as well on trunk.
I don't think anyone is currently using it.
I think we're free and clear here. The reporter for fennec add-on has been inactivated as well. So, all ties should be closed off to reporter.mozilla.org at this point.
Does it contain any data that needs to be safe, or can we remove both the code and the database backuplessly?
Let's go the safe route and backup the data. It is 7-9 years worth of broken website reports.
Re comment #10, this does seem like useful data to keep around so I think archiving instead of retiring is reasonable. We didn't talk about this site on the last abandoned sites call though, so it may be worth more discussion.
It's been discussed months back when input was getting incorporated into the betas. Everyone is on the same page that this site is abandoned, but has reasonable set of data to keep backedup somewhere. Git'r done!
I think there's no archiving this site in the same way others can be "webcrawled and saved", as it's essentially a big search form that ties into the database. This one needs to stay up with the search function active, or removed. This, of course, does not prohibit IT from keeping a long-term backup of the pure database SQL on a tape or something, but it won't be immediately accessible.
It sounds like we're talking about two different things -- there's the data and then the site. And as mentioned in comment #12, once you have the data backedup you need to keep it somewhere. We could archive the site as it is and let people access the data that way. In that case it would be moved to: http://website-archive.mozilla.org/reporter.mozilla.org Or you could put the data somewhere else and we can take down the reporter.mozilla.org site and have that URL redirect to wherever you put the data. Maybe you make a blog post with a link to the data on an FTP server or something?
Seems like setting reporter.mozilla.org -> input.mozilla.org and a blog post would suffice if input is its active (and better) replacement.
I'm with Fred and Morgamic. There's no way to scrape and archive this site to website-archive.mozilla.org because it's a form-based site. I think we need to: a) backup the database b) redirect the website visitors from reporter.mozilla.org to input.mozilla.org c) remove the existing database and website code Do we even need a blog post? It seems like input.mozilla.org has in essence replaced functionality in reporter.mozilla.org and redirecting those visitors to Input should be sufficient enough of an explanation.
I'll write one in the next product release of Input just to make sure.
Redirecting reporter.mozilla.org to input.mozilla.com sounds fine, but that doesn't address Aakash's point about backing up that old data -- where does that live then?
I'll file a bug to get a database dump from that site. I'll glance over it to see if there's any personally identifiable information in there (IPs, usernames, emails) and remove it (read: no backup). Then we can have IT drop that SQL file onto our FTP server, and Aakash can link to it in his blog post. Another question: What about making the root of website-archive.m.org a wordpress blog and just write a quick blog post about every site we remove? Seems like this should be a standard part of our site retirement process, now and in the future.
For the question in comment #19, we should probably find a better place to talk about the general archiving process instead of discussing it in a bug about a particular site. We could discuss over email with the group of people from the abandoned sites working group or we can have another meeting.
I'd suggest a DB dump as well. Backing up the pages is impractical and likely useless. The IP's and email addresses would need to be removed or sanitized to make them anonymous but still useful... Perhaps xxx.yyy.0.0 so that you can still perhaps tell what ISP (and country) the report came from. Could be interesting at some point down the road to analyze. Either a SQL dump or even CSV of the reports table.
Quick update, I have acquired a DB dump, I am anonymizing the IPs like Robert suggests and removed all emails. I will then export just the report tables for IT to upload to our FTP server. Finally, we can shut down the site.
A stub blog post for this site has been placed at: http://blog.mozilla.com/website-archive/2010/12/08/mozilla-reporter/
The anonymized SQL dump was uploaded to the FTP server, and I updated the blog post with it. I am going to file a bug to have the site taken offline.
Robert, will you give the green light to take down the site and database without a backup? The data is now anonymized in the way you suggest in comment 21. Only the two "reports" tables are included in the SQL dump.
I don't see why not. Thanks for driving this Fred.
The site is gone, and the blog post is available on the archive blog. Done!