|
|
| (10 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| __NOTOC__ | | __NOTOC__ |
| =What we need from you= | | <noinclude> |
| | <pre> |
| | {{l10n-priority= |
| | |l10n-owner= |
| | |l10n-length= |
| | |l10n-targetaudience= |
| | |l10n-projecthome= |
| | |l10n-locales= |
| | |l10n-expansion= |
| | |l10n-resources= |
| | |l10n-life-cycle= |
| | |l10n-schedule= |
| | |l10n-target-date= |
| | }} |
| | </pre> |
| | Edit page to see entire form. |
| | [[category:NewL10nProjects]] |
| | </noinclude> |
|
| |
|
| ==Project owners==
| | <includeonly> |
| Who we will be collaborating with on your team?
| |
| Alaksiej Lavončyk, alaksiej.lavoncyk@tol.org, project coordinator
| |
| Jan Praŭdzin, inszyby@gmail.com, project coordinator
| |
|
| |
|
| ==Project scope outline== | | <div style="width: 300px; background-color:#CFCFCF; padding: 5px; font-size: .8em">Please use the "Edit with Form" link above to edit</div> |
| Identify the following as part of your project's scope:
| |
| * What is the estimated length of localizable content (in number of strings and words)?
| |
| The whole interface of Mozille Firefox 10 into Kyrgyz language ( I understand so that we should receive this file form you?)
| |
|
| |
|
| * What is your project's key functionality?
| | {| class="wikitable" |
| Localize the FFF to Kyrgyz
| | ! Priority |
| | | | [[l10n-priority::{{{l10n-priority|}}}]] |
| * Where will your project live?
| | |- |
| | | ! Owner |
| * What are your target locales?
| | | [[l10n-owner::{{{l10n-owner|}}}]] |
| Kyrgyz
| | |- |
| | | ! Project length (in # of strings and words) |
| * What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
| | | [[l10n-length::{{{l10n-length|}}}]] |
| | | |- |
| * What are your available resources?
| | ! Description of target audience |
| 25-strong localization team
| | | [[l10n-targetaudience::{{{l10n-targetaudience|}}}]] |
| | | |- |
| * What is your project's expected life-cycle (i.e., short-term/long-term)?
| | ! Project home (Where will your project live?) |
| Long term: the project will be supported by the Kyrgyz community of localizers in Bishkek and Osh.
| | | [[l10n-projecthome::{{{l10n-projecthome|}}}]] |
| We will be ongoingly supporting the project in terms of adding new strings localizations.
| | |- |
| | | ! Target locales |
| * What L10n requirements have you already defined?
| | | [[l10n-locales::{{{l10n-locales|}}}]] |
| | | |- |
| {| border="1" | | ! Locale expansion rate (What is your estimated rate of locale expansion per quarter?) |
| |+'''Considerations to make when identifying L10n requirements''' | | | [[l10n-expansion::{{{l10n-expansion|}}}]] |
| ! scope="col" | Short-term | |
| ! scope="col" | Examples
| |
| ! scope="col" | Long-term | |
| ! scope="col" | Examples
| |
| |- | | |- |
| |L10n requirements must be simple || || Use techniques to make updating the site much easier. ||
| | ! Available L10n resources |
| | | [[l10n-resources::{{{l10n-resources|}}}]] |
| |- | | |- |
| |Words || || Updating content is laborious. Beware of L10n burnout. || | | ! Project life-cycle |
| | | [[l10n-life-cycle::{{{l10n-life-cycle|}}}]] |
| |- | | |- |
| |Palabras || || How "evergreen" is the content on your site? || | | ! Release schedule |
| | | [[l10n-schedule::{{{l10n-schedule|}}}]] |
| |- | | |- |
| |Palavras || || How often do you plan to change your project? || | | ! Target date |
| | | [[l10n-target-date::{{{l10n-target-date|}}}]] |
| |} | | |} |
|
| |
|
| ==Release schedule==
| | [[category:NewL10nProjects]] |
| Identify the following as part of development phases:
| | </includeonly> |
| * Dates outlining development phases for the first localized releases.
| |
| 2 months for the localized front end to go live
| |
| 2 more months for bugs fixing and adding back end localizations
| |
| * Cost in days for each development phase.
| |
| two stages, each 60 days
| |
| | |
| ==Timeline to implementation==
| |
| Identify the length time we have to incorporate your project into the overall workflow, including noteworthy milestones. For an example of what we're looking for, see the [https://docs.google.com/spreadsheet/ccc?key=0Al5H7QuXOsNZdGh0LXRQWlB6OTZGa2kzV2loRXpFT3c&hl=en_US|Live#gid=0 Firefox Live timeline].
| |
| Briefing the localization team about the localization procedures - by March 15
| |
| Distributing the tasks - by March 16
| |
| Feedback and Q&As - by March 20
| |
| Front end localization - by May 1
| |
| Testing - by May 10
| |
| Back end localization - by June 1
| |
| Testing - by June 10
| |
| Going live - by June 15
| |
| | |
| =Our response=
| |