Websites/Mozilla.org/Roadmap 2011

A Note On Naming

Right now it is easy to talk about the Mozilla, Firefox and Thunderbird sites since they are different sites. This will get more difficult when this content is consolidated together on www.mozilla.org. To avoid confusion, we can just refer to them as sections instead of sites.

• The Firefox section is mozilla.org/firefox
• The Thunderbird section is mozilla.org/thunderbird
• The Drumbeat section is mozilla.org/drumbeat
• The Mozilla section is mozilla.org/ (excluding Firefox, Thunderbird and Drumbeat sections)

Milestones

A list of high-level milestones for mozilla.org in 2011 in no particular order (timing will be discussed in the Roadmap section).

• Switch www.mozilla.com/firefox content to www.mozilla.org/firefox

• Launch membership, Firefox 4 and other pages as needed

• Resolve content overlap with mozilla-europe.org

• Sync/integrate mozilla.org and mozilla.org/firefox backends

• Move mozillamessaging.com content to mozilla.org/thunderbird

• Migrate legacy content out of Mozilla section

• Create mozilla.org/drumbeat pages

• Launch unified design across Mozilla, Firefox, Thunderbird, Drumbeat sections

• Add dynamic content areas on key pages

• Create processes and guides for mozilla.org that can be used by wider universe (common footer, mozilla web font, performance tips, etc)

Roadmap

Webdev has suggested we consider having rolling regular releases instead of adding things to the site in an ad hoc fashion to make scheduling resources easier. We'll follow SUMO's Kitsune roadmap as a template.

Proposal: Establish monthly releases with the details of each release determined at a site planning meeting held during the previous month.

1.0

• Tracking bug:
• Major tasks:
  • mozilla.com/firefox to mozilla.org/firefox domain switch
  • membership pages launched
  • Bug X
  • Bug Y
  • Bug Z
• Timeline:
  • Start: January 1, 2011
  • Freeze: January 24, 2011
  • Push: January 31, 2011

1.1

• Tracking bug:
• Major tasks:
  • Bug X
  • Bug Y
  • Bug Z
• Timeline:
  • Start:
  • Freeze:
  • Push:

Open Questions

• How should Engagement's projects that involve websites other than www.mozilla.org (such as a microsite) fit in with this scheduling?

• Are there projects that can happen outside of a release? For instance, I assume small updates don't need to go through this whole process, but where is that threshold?

• How could we handle rescheduling releases to adjust to changes in priorities?