Websites/Mozilla.org/Archive/Planning
This page is being used to create a plan for www.mozilla.org to address comments raised in bug 345664.
Establish Identity
A discussion about the vision for www.mozilla.org is taking place on mozilla.dev.mozilla-org. See:
If a page on www.mozilla.org does not fit with the vision for the site, there are three options: archive it, migrate it or update it. Deleting a page is not one of the options because we feel that it is impossible to know what might be useful for someone in the community and we also want to preserve a record of past contributions to the Mozilla site.
Archive Obsolete Pages
Owner: David Boswell
Actions:
- First, we take a snapshot of the site (bug 395669) and make it available somewhere (archive.mozilla.org or wherever). At some point, we may put together a curated history page or section that makes the historically relevant information easier to find on the archive site.
- Second, we post a page on the wiki where we list all of the pages currently under consideration for archiving. To make things easy to manage, we should start by posting only a small batch of pages (5 or 10?). Once we have the process working more smoothly we can post larger batches of pages.
- Third, after a certain period of public discussion (2 weeks maybe?) these pages will be removed from www.mozilla.org's CVS and a redirect set up to the archive site. We may need to set up some sort of archive landing page or header so that people are aware that the content they are seeing is no longer considered current.
More detail is needed in this process, specifically: we need to have a page somewhere detailing the process (i.e. what newsgroup to post about the proposed-for-deletion pages, how do we identify and notify the interested parties about those documents, etc.) Right now there's no way to even start the removal/archival process (short of convincing someone with www access to kill the doc), and no estimates when this will change -- this discourages some contributors.
For background, a discussion about how to handle archiving or removing content from www.mozilla.org is available on mozilla.dev.mozilla-org. See:
Migrate Content
Owner: Sheppy
Action Items: Move developer content to developer.mozilla.org and identify other content that may belong on other community sites.
- Suggestion: Maybe we should set up a sandbox-like area on MDC to copy developer-related articles from Mozilla.org to; from there, they can make their way to the main MDC site as they're vetted and updated as appropriate, while remaining available with some sort of "This article may be obsolete" banner across the top of the page.
Having heard no objections to that plan, I think that's what we should do. I'll look at organization for this next week.
Update Content
Owner: Simon Paquet
Action Items:
- Reorganize the Projects page
- by removing projects, which are clearly inactive or outdated
- Determine the activity/validity status of other projects, whose project pages were not updated within the last 18 months
- Remove/archive all content of inactive/outdated projects
- create a valid definition of what constitutes a mozilla.org project and what does not. Remove all items, which do not fall under that category.
- Proposal posted to mozilla.dev.mozilla-org
- Tracking Bug - Bug 393447
Reorganize Structure
Owner: TBD
Action Items: Once content has been migrated, archived and updated it is likely that the remaining content will need to be reorganized.
Select Owners
Owner: TBD
Action Items: A module owner for the site needs to be identified that will make sure the site is following the identity established in this plan.
This is a pretty critical task. Until there's an owner, there's going to be a lot of indecision on the parts of people who are trying to work on this stuff about whether or not they're doing the right thing. --Sheppy 14:13, 13 September 2007 (PDT)