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 3 at 10 AM 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.

www.mozilla.com and www.mozilla.org merge

Mozilla.org/Roadmap 2011/Domain change

P1 Bugs

Create a more usable staging site
- What else needs to be done to fix this bug?

Content

Current Project

Future Content Updates

Move content as needed from mozilla.com

See more:

Content priorities list

Coding

Link to SVN history of page in mozilla.org footer is broken
- Fixed in staging; needs merge to trunk
Add last modified date to footer where the current 'Page History' link is
- Fixed in staging; needs merge to trunk
Set up customizable auto-response for different project areas listed in Get Involved form
- Needs patch; has been assigned to Paul Osman since 2010-07-15 with no progress
Install phpSyndication 1.0b1 site-wide
- Needs approval
Add RSS feed for Mozilla Foundation Security Advisories
- Easy to implement if phpSyndication is installed

Localization

Need staging server for testing integration with Verbatim

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

Stats

Note: Urchin script removed, no longer being used but available as archive.

We've moved to WebTrends -- seems better but needs configuration.

Relevant Links:

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.

Back-end

Look into replacing Doctor with ACE as editor for www.mozilla.org
- This has been sitting dormant since 2009; is it still desired?

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?

Getting New People Involved

Open Issues: