1,035
edits
L10n/HomePage/Status/2007-06-06: Difference between revisions
→Triaging Bug list
No edit summary |
|||
| Line 45: | Line 45: | ||
* We will be encouraging new Localizers to create a language pack which will be listed on AMO. This allows Localizers to start somewhere and doesn't require Mozilla Corporation to commit additional resources to support these language packs until later stages when Localizers move towards official builds (for more detail see the Localization Process overview). Existing or ongoing "Beta" builds will be hosted on the main Mozilla page. Language packs don't have a full installer or dedicated website or locale-chosen search engines, bookmarks, etc. They do provide the benefit of automated updates although a known bug prevents people from getting security updates | * We will be encouraging new Localizers to create a language pack which will be listed on AMO. This allows Localizers to start somewhere and doesn't require Mozilla Corporation to commit additional resources to support these language packs until later stages when Localizers move towards official builds (for more detail see the Localization Process overview). Existing or ongoing "Beta" builds will be hosted on the main Mozilla page. Language packs don't have a full installer or dedicated website or locale-chosen search engines, bookmarks, etc. They do provide the benefit of automated updates although a known bug prevents people from getting security updates | ||
* From our discussion we know that we need Engineering resources dedicated to fix the known bug; This is a significantly different user experience than the "regular" download; on AMO this will be seen as a regular XPI file; we can add a category for language packs on AMO; and given the AMO [https://addons.mozilla.org/en-US/firefox/pages/policy|testing guidelines] (scroll to "What are the criteria for public add-ons" to find out the requirements) we can rely on the community to assist in doing a review and then pushing it live based on their feedback/experience; no work has been done on the bugs as of yet there are known duplicates that need to be addressed by encouraging people to work together and create something users can test | * From our discussion we know that we need Engineering resources dedicated to fix the known bug; This is a significantly different user experience than the "regular" download; on AMO this will be seen as a regular XPI file; we can add a category for language packs on AMO; and given the AMO [https://addons.mozilla.org/en-US/firefox/pages/policy|testing guidelines] (scroll to "What are the criteria for public add-ons" to find out the requirements) we can rely on the community to assist in doing a review and then pushing it live based on their feedback/experience; no work has been done on the bugs as of yet there are known duplicates that need to be addressed by encouraging people to work together and create something users can test | ||
* There is another known [https://bugzilla.mozilla.org/show_bug.cgi?id=375359|bug] for allowing sandbox add-ons to get updates | * There is another known [https://bugzilla.mozilla.org/show_bug.cgi?id=375359| bug] for allowing sandbox add-ons to get updates | ||
* There was some discussion about whether it matters if this happens before or after cvs - which gives us different information; no conclusions were drawn | * There was some discussion about whether it matters if this happens before or after cvs - which gives us different information; no conclusions were drawn | ||
ACTION: Gerv (+ help offered from Mic, Pascal and Choffman) to start | ACTION: Gerv (+ help offered from Mic, Pascal and Choffman) to start | ||