Marketing:Thunderbird Website

Tracking document for Thunderbird 3 web site localization

Who

• lead: rebron
• l10n leads: sipaq, pascalc
• QA lead: _Tsk_

What

This is the planning document/site to manage the web site content in Thunderbird for our 51 lang/locales. The items to be localized include:

• 1) download "landing" page: all locales
• 2) download thank you page: all locales
• 3) start page: all
• 4) what's new page: all locales
• 5) product page: on a per locale basis depending on the amount of work they represent (localized graphics? amount of text, screen shots...)
• 6) release notes: on an opt-in basis. Interested locales can localize the page
• 7) press release: on an opt-in basis. Interested locales can localize the page

We also need to check for account setup -- which email providers are included during account setup.

The start page must live on *.mozillamessaging.com. The ideal is support page and product pages all live on *.mozillamessaging.com. However, Community sites may point to support and product pages with the Thunderbird web site look and feel.

Release notes may not be finalized until RC1 specifically the known issues section.

General Planning

step	start date	end date	status
planning meeting
Create Tracking Bugs - do we need this?
Announce plan to localizers	9/30/2009	9/30/2009

Website

step	start date	est. duration	end date	status
en-US content on staging	9/30/2009	-	10/2/2009
FR localization	10/5/2009	-	10/12/2009
Localization pages rest of countries	10/12/2009	-
QA tests website on staging (text, links etc)		-

Final Release Phase

step	start date	est. duration	end date	status
Build moves from trunk to staging		-
Build moves from staging to production		-
QA live site		-

Localization Checklist

Locale	Priority	Pages/URLs	Bug(s)	Completion
Afrikaans	P2
Albanian	P3
Arabic	P2
Basque	P3
Belarusian	P3
Bengali (Bangladesh)	P2
Bulgarian	P3
Catalan	P3
Chinese (Simplified)	P1
Chinese (Traditional)	P2
Czech	P2
Dutch	P1
English (British)	P2
English (US)	P1
Estonian	P3
Finnish	P3
French	P1
Frisian	P3
Galician	P3
Georgian	P3
German	P1
Greek	P3
Hebrew	P3
Hungarian	P2
Icelandic	P3
Indonesian	P2
Irish	P3
Italian	P2
Japanese	P1
Korean	P2
Lithuanian	P3
Norwegian (Bokmal)	P2
Norwegian (Nynorsk)	P3
Polish	P1
Portuguese (Brazil)	P1
Portuguese (Portugal)	P2
Punjabi	P2
Romanian	P2
Russian	P1
Serbian	P3
Sinhala	P3
Slovak	P3
Spanish (Argentina)	P2
Spanish (Spain)	P1
Swedish	P2
Tamil (Sri Lanka)	P2
Turkish	P2
Ukrainian	P2
Vietnamese	P2

Note: time estimates are calculated in uninterrupted hour/days... Better use them for comparing relative effort.

Other Notes

Localization of the site depends on several factors:

1/ possibility to communicate to localizers via the webdashboard, mozillamessaging is now a separate project there so no problem

2/ locale detection and general locale support on mozillamessaging, we have added the minimum requirements for that with the 2.0.0.21 release and the move of the localized start pages from mozilla.com to mozillamessaging, minor releases now happen on mozillamessaging for locales

3/ simplified templates (header/footer) for locales, to be done but shouldn't take me much time, a day to make and test them

4/ creation of TB3 content for localizers, this is highly dependent on the creation of en-US content that will be used as a basis for translation, essentially:

   - new start page
   - landing page for all locales that serves as a home page as we do on mozilla.com
   - minimum set of pages (essentially features pages) for top locales which will have a more complete set of pages

5/ creation of a simplified landing sub page on mozilla-europe to also propose downloads there

6/ some administrative work as I have to open bugs for all localizers to give them access to mozillamessaging repo

7/ QA