Websites/Mozilla.org/Archive/Planning

From MozillaWiki
Jump to navigation Jump to search

This page is being used as a planning document for updating the www.mozilla.org site. A high-level big picture document is also available that gives information about the goals and vision for the site.

Planning Meetings

Meetings are held on the first Thursday of each month to coordinate ongoing work related to the site.

  • Next regular meeting: Thursday, March 4 at 9:30 pacific
  • Dial-in information: 1-800-707-2533, pin: 369, conf: 7600
  • Back channel: irc.mozilla.org#siteplanning
  • Notes from previous meetings

Open Issues

These issues are the agenda for the next planning meeting.

P1 Bugs

Ownership

Content

Current Project

Future Content Updates

See more:

Design

Localization

Now that the site is on Subversion we can start to work with the existing web localization community.

Current blockers:

  • Having a genuine staging site for localizers (and others) to stage content without it automatically go live
  • Web l10n community booked until January

Planning:

  • Determine objectives for localizing content (eg, increase traffic on Manifesto page)
  • Determine what we want to localize and what's ready to be localized
  • Look into alternatives for dynamic content (either find language-specific replacements or degrade pages gracefully)
  • Finalize and implement our l10n system

Other

  • bug 479085 – Turn off language negotiation for Mozilla Manifesto translations

Back-end

Archiving/Migrating

Note: For migrating docs, 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.

Testing

How can we improve the ongoing testing we're doing for the site? Some ideas to discuss:

  • Announce call for testers and owner for www.mozilla.org QA
  • Triage open site bugs
  • Hook in to existing Web QA team and processes
  • Set up automated tests for site (See MDC unit testing and Selenium)
  • Other things we should be doing?

Stats

Open Issues:

Relevant Links:

Getting New People Involved

Open Issues:

Relevant Links:

Resolved/Inactive Issues

Previous items on this page have been moved to the Archive page.