Websites/Mozilla.org/Archive/Planning: Difference between revisions
| Line 23: | Line 23: | ||
'''Current Project''' | '''Current Project''' | ||
* | * [http://davidwboswell.wordpress.com/2010/08/04/refreshing-the-mozilla-org-home-page/|Home page redesign] | ||
* [ | * [http://www.mozilla.org/community/universe.html|Community Map] | ||
'''Future Content Updates''' | '''Future Content Updates''' | ||
Revision as of 17:00, 4 August 2010
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, August 5 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
Content
Current Project
Future Content Updates
- Revisit all top-level pages to sync with updated home page.
See more:
Coding
With Paul starting at Mozilla Foundation and with increased coding interest from community, we should discuss the review process for coding changes. David can handle content and design reviews, but has no business reviewing PHP or JS changes. For instance, there are three site code patches waiting for review now:
- Add last modified date to footer where the current 'Page History' link is
- Set up customizable auto-response for different project areas listed in Get Involved form
- Add a new tab on Contribute page on mozilla.org
- Add RSS feed for Mozilla Foundation Security Advisories
Localization
Current blockers:
- Having a genuine staging site for localizers to stage content without it automatically go live
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
- We've moved to WebTrends -- seems better but needs configuration.
Relevant Links:
Archiving/Migrating
- Documentation migration priorities
- Various archiving bugs
- Various documentation migration bugs
- Archived version of site
- Removing content from www.mozilla.org
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
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:
Relevant Links:
Resolved/Inactive Issues
Previous items on this page have been moved to the Archive page.