L10n:Firefox web services process: Difference between revisions

no edit summary
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 7: Line 7:


==Triggers==
==Triggers==
What triggers the process?
What triggers the process?
* new locale added to the tree
* new locale added to the tree
Line 15: Line 14:
* technical changes in Firefox e.g., favicons
* technical changes in Firefox e.g., favicons


Here's a bit more specificity on what kind of releases are good for what kind of changes:
Here's a bit more specificity on what kind of releases are good for what kind of changes
    * major release, review web services for Tier 1/2 several months in advance (could even do that for all Tier's) starting with IRC chat and then moving to bugs for documentation and tracking and finally to wiki or google spreadsheet documentation, participate in the Fx product calls and listen for new features that can be localized and then if there are new ones, propose a process for localizing it and document that in the documentation (https://wiki.mozilla.org/Firefox3/L10n_Requirements)
* major release
    * minor release, update any changes that have been pending for any locale and take on new locales
**review web services for Tier 1/2 several months in advance (could even do that for all Tier's) starting with IRC chat and then moving to bugs for documentation and tracking and finally to wiki or google spreadsheet documentation,  
**participate in the Fx product calls and listen for new features that can be localized and then if there are new ones, propose a process for localizing it and document that in the documentation (https://wiki.mozilla.org/Firefox3/L10n_Requirements)
* minor release
**update any changes that have been pending for any locale and take on new locales


==Process==
==Process==
Line 24: Line 26:


===Filing bugs===
===Filing bugs===
See [[L10n:Bugogram]]
 
For major releases and new locales, 5 bugs regarding web services are filed:
 
* Search engine setup for Firefox X for ${locale}
** (blocker for new locales' beta releases)
* Firefox X protocol handler setup for ${locale}
* Firefox X RSS reader setup for ${locale}
* RSS Sample feed for ${locale}
* "Getting started" page for ${locale}
 
(See [[L10n:Bugogram]] for more details.)
 
For other triggering cases, separate bugs for affected locales are filed.


===Suggestions===
===Suggestions===
Line 43: Line 57:
#* what is the local way of using the web?
#* what is the local way of using the web?
#* what can we do to ensure best web experience for the local users?
#* what can we do to ensure best web experience for the local users?
In addition, we use a following set of tools to gather more information about the candidate services:
* [http://www.alexa.com/site/ds/top_500 Alexa'a top 500 by country]
* [http://toolbar.netcraft.com/stats/topsites Netcraft's top sites]
* [http://www.statsaholic.com/ Statsholic (Compete and Quantcast mash-up)]
* [http://validator.w3.org/ W3C Markup Validator]
* [http://validator.w3.org/feed/ W3C Feed Validator]


===Dialog with providers===
===Dialog with providers===
This step's purpose is to:
This step's purpose is to:
* obtain written permission from providers to include their services in the default installation of Firefox
* obtain written permission from providers to include their services in the default installation of Firefox (for search plugins, RSS readers, protocol handlers and the sample RSS feed).
* verify technical aspects of providers (search parameters, QA)
* verify technical aspects of providers (search parameters, QA).
* for the Getting Started page, we inform the websites that we link to about this fact.
 
===Implementation===
 
====Search plugins, RSS readers, protocal handlers====
All changes to web services need a patch and a review from one of the l10n-drivers. Depending on the current release schedule and tree rules, they may also require an approval before landing.
 
Once the patch has been reviewed and the code landed, the corresponding bug should be resolved as ''resolved fixed'' (by the localizer or a l10n driver).
 
====Sample RSS feed====
 
The Live Bookmark (sample RSS feed) is managed by a redirect under:
${locale}.fxfeeds.mozilla.com/${locale}/firefox/headlines.xml
 
After choosing and verifying the feed's URL, the page [[Firefox/L10n_Feed_Redirects]] should be updated, as well as the spreadsheet used by the l10n-drivers team (column ''Status'' should by cleared). An empty cell in this column indicates a redirect to be set up.
 
An IT bug is then filed by one of the l10n-drivers to create/change redirects ''en masse''.
 
====Getting started page====
 
===Verification===
 
The bug should be closed as ''verified'' (by the localizer or a l10n driver) in the following cases:
 
;Search plug-ins, RSS readers, protocol handlers
:After verifying that the change works as expected in a nightly build.
 
;Live Bookmark (sample RSS feed)
:This change is visible instantly after the IT bug has been closed. Alternatively, Pike's [http://hg.mozilla.org/users/axel_mozilla.com/tooling/log/tip/mozilla/testing/tests/l10n/scripts/verify-rss-redirects verify-rss-redirect script] can be used to verify if the redirects work as expected
 
;"Getting started" page
:This change is visible after the push of the mozilla.com website under:
http://${locale}.www.mozilla.com/${locale}/firefox/central/


==Lessons learned==
==Lessons learned==
Line 53: Line 107:
This is not meant to replace the Web Services Guidelines page but to enhance our own thinking and approach to evaluate these based on experience from many interesting situations that have come up in different locales.
This is not meant to replace the Web Services Guidelines page but to enhance our own thinking and approach to evaluate these based on experience from many interesting situations that have come up in different locales.


* kr - daum RSS reader (requiring the user to bundle reader with another service)
* ko - daum RSS reader (requiring the user to bundle reader with another service)
* Occitan sample RSS feed (culturally relevant, even though doesn't update often)
* Occitan sample RSS feed (culturally relevant, even though doesn't update often)
* ga-IE getting started page (Esperanto)
* ga-IE getting started page
* eo getting started page
* search plugins are always unique - we try to keep creative commons in most locales, often times locale have more unique specific local search or knowledge search that are dependent on what's culturally relevant. lots of interesting examples (zh-CN, et, lv)
* search plugins are always unique - we try to keep creative commons in most locales, often times locale have more unique specific local search or knowledge search that are dependent on what's culturally relevant. lots of interesting examples (zh-CN, et, lv)


Line 61: Line 116:
We track every change that is made for each release in bugs and in wiki or Google documents. The reason that we do this is to enable any one to be able to reveiw what has happened in any particular locale over time.  
We track every change that is made for each release in bugs and in wiki or Google documents. The reason that we do this is to enable any one to be able to reveiw what has happened in any particular locale over time.  


* Firefox 3 https://wiki.mozilla.org/Firefox_web_services_Review
* [https://wiki.mozilla.org/L10n:Firefox_web_services_status Firefox 3.0.x and later]
* Firefox 2 https://intranet.mozilla.org/Trademark_L10n_Review-Firefox2#Firefox_Search_Plug-In_Review_Document|
* [https://wiki.mozilla.org/Firefox_web_services_Review Firefox 3.0]
 
* [https://intranet.mozilla.org/Trademark_L10n_Review-Firefox2#Firefox_Search_Plug-In_Review_Document| Firefox 2]
==Stuff not to forget==
* feedback loop to ui/ue based on what you see in market, as well as marketing team
* email templates for outreach
** Protocol handlers
** Search parameters and permission
** RSS Feed
** RSS readers
** Getting started
* significant market research links for decisions (Alexa, Feed validator)
* outcomes of each step
canmove, Confirmed users
1,448

edits