Websites/Taskforce/Proposals/Abandoned Sites: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 97: Line 97:
** Production code will go away when AMO switches off Remora codebase.
** Production code will go away when AMO switches off Remora codebase.
* '''[http://guides.mozilla.org/ guides.mozilla.org]'''
* '''[http://guides.mozilla.org/ guides.mozilla.org]'''
** Decision: Still active
** Decision: Still active, do not touch
** {{bug|617678}}
** {{bug|617678}}
* '''[http://hendrix.mozilla.org hendrix.mozilla.org]'''
* '''[http://hendrix.mozilla.org hendrix.mozilla.org]'''
** Status
** Decision; Retire and redirect to input.mozilla.com
** Decision; Retire and redirect to input.mozilla.com
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more
** {{bug|622621}}
* '''[http://www.mozilla24.com mozilla24.com]''' - Mozilla 24 - Worldwide Community Event
* '''[http://www.mozilla24.com mozilla24.com]''' - Mozilla 24 - Worldwide Community Event
** Decision: Hosted by Mozilla Japan.  Will revisit this 2011.
** Decision: Hosted by Mozilla Japan.  Will revisit this 2011.
Line 110: Line 112:
* '''[http://www.onebillionplusyou.com onebillionplusyou.com]''' - One Billion + You
* '''[http://www.onebillionplusyou.com onebillionplusyou.com]''' - One Billion + You
** Status: COMPLETED
** Status: COMPLETED
** Decision: Ryan will begin archive process
** Decision: Archive
** {{bug|607178}}
** {{bug|607178}}
* '''[http://www.opentochoice.org opentochoice.org]''' -- Open To Choice
* '''[http://www.opentochoice.org opentochoice.org]''' -- Open To Choice

Revision as of 18:46, 3 January 2011

Abandoned Sites

Working Group

Ryan Snyder, Frederic Wenzel, Mike Morgan, Chris Lyon, Steve Curbishley and David Boswell

Status

Draft

Problem

There are a number of Mozilla sites that are still online but are no longer active or up to date. These sites can make it hard to find more current information and can also create security or privacy concerns when there is functionality that is no longer being maintained or is no longer needed.

Note that this policy deals with abandoned sites and does not touch on abandoned content within otherwise active sites.

Solution

To be able to keep the content on our sites up to date and relevant we need a way to archive or turn off abandoned sites.

Archiving or Turning Off Sites

For sites that are no longer active, we propose either archiving them or turning them off. To define these terms more clearly:

Archiving a site involves scraping the content, moving it to a read-only archive site, adding a note about the content being out of date to the top of the pages and setting up redirects (for example, if http://mozillaservice.org was archived someone going to that URL would be taken to http://website-archive.mozilla.org/mozillaservice.org/).

Turning off a site simply involves taking it down from Mozilla's web servers. If there are relevant links, redirects could be set up (for instance, pointing traffic to a blog post about why the site was taken down).

We propose the following steps for determining how to identify abandoned sites and what the best course of action is in a given situation.

Identifying Abandoned Sites

Because of Mozilla's decentralized structure, there is no easy way to get a list of all sites and their current status. Unless someone comes up with a better way of finding sites and determining their level of activity, we'll just need to manually maintain a site list.

Currently the Community Directory is the most complete reference we know of. To add new sites to this list, to suggest a site be removed or to propose that a site be moved into the Archive section, please open a www.mozilla.org bug.

Processes

Once a site has been identified as a candidate for archiving or deletion, the following steps should be followed:

  • A bug should be filed in Bugzilla using the website-archive.mozilla.org component.
  • An attempt to identify the owner of the site should be made to confirm the site is no longer active. If no owner can be found, the websites task force will make a decision about the site's status.
  • A MXR search should be performed for the candidate site to ensure that it is not pointed to or used by any of our products. Searches should cover all supported branches of all relevant repositories (mozilla-central, comm-central, mozilla-* and comm-*, labs, chatzilla, etc).
  • The Abandoned Sites working group will then take the bug and take the appropriate next steps (closing as wontfix, archiving or turning off site).

Guidelines

It is important to preserve the community's history, but it is also unnecessary to save every site about Mozilla that's ever existed. To help with the decision making process about what to do with an abandoned site, we offer the following guidelines.

  • Is a reasonable alternative version of the content available anywhere else?
    • For instance, if all of the firefoxflicks.com videos are on our YouTube channel we could turn off the site and redirect traffic there.
  • Is the site a tool used to edit, view or interact with other content?
    • For instance, doctor.mozilla.org has no content but allows users to edit content used on CVS-hosted sites and could be turned off.
  • Is the site hosted on infrastructure run by the Mozilla Foundation or one of its subsidiaries?
    • For instance, a Firefox community site run by a contributor may be archived at our discretion depending on the specific circumstances of that site.
  • Are there web analytics for this site?
    • For instance, does this site receive a sizeable amount of traffic (e.g. greater than 250 unique visitors per day) that warrants being redirected to an archived copy of the website?

Implementation

An initial batch of sites to archive have been identified as part of this process. We are moving forward with archiving the Mozilla Service Week site first as a case study and we will then work through the remaining sites in the following list.

Sites to Discuss in 2011

  • firefoxclicks.com
  • guides.mozilla.org

Mozilla Japan

A member of the Website Taskforce needs to reach out to Mozilla Japan about retiring or archiving the following websites:

Sites Discussed in 2010

Ryan Snyder, David Boswell, John Slater, Fred Wenzel and William Reynolds met on Nov 23 2010 to come to the following resolutions:

Note: the items above related to removing a part of a site's functionality are being tracked as part of the archiving process for now, but this really deserves its own policy since these are separate issues.

Archiving Process

Follow these instructions to archive a Mozilla website.

Retrieved from "https://wiki.allizom.org/index.php?title=Websites/Taskforce/Proposals/Abandoned_Sites&oldid=275396"