Notes from discussion about www.mozilla.org localization
davidwboswell
for the www.mozilla.org site and wanted to send around notes. We can
use these items as part of the agenda for the next planning meeting
this Thursday.
* We should determine specific objectives for localization. For
example, traffic targets for Manifesto. Our objectives will likely be
different from the product-related sites (for instance, we wouldn't be
measuring change in download rates).
* For pages with dynamic content (such as home page) we need to
identify language specific alternatives (such as Lizard Feeder-like
feed in other languages for Community Ticker) or have page degrade
gracefully by turning dynamic content off (create an alternate design
for home page without Community Ticker or Latest News section)
* We need to resolve what setup we're going to use for l10n on www.mozilla.org.
If Apache language negotiation, we need to make sure existing
localizers can work with this system. If not, what can we do to
follow the model of other localized Mozilla sites?
* Localizers will probably want a staging site where they can view
their work with others before the changes go live. How can we add
this to our existing workflow where commits automatically get sent to
the live site?
* Pascal suggested we start with just one locale to work through
issues and then go from there. He has someone in mind who might be
interested in doing a French localization.
* We can discuss more at the next planning meeting on Thursday or we
can set up another time to meet with the planning group (the upcoming
meeting in Prague might cause some scheduling conflicts with the
meeting on Thursday).