Template:L10nProjectRequestForm: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Undo revision 403876 by Eolonir (talk))
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<p>__NOTOC__
__NOTOC__
</p>
<noinclude>
<h1>What we need from you</h1>
<pre>
<h2>Project owners</h2>
{{l10n-priority=
<p>Who we will be collaborating with on your team?
|l10n-owner=
</p>
|l10n-length=
<h2>Project scope outline</h2>
|l10n-targetaudience=
<p>Identify the following as part of your project's scope:
|l10n-projecthome=
</p>
|l10n-locales=
<ul><li>  What is the estimated length of localizable content (in number of strings and words)?
|l10n-expansion=
</li></ul>
|l10n-resources=
<p>The whole interface of Mozille Firefox 10 into Kyrgyz language ( I understand so that we should receive this file form you?)
|l10n-life-cycle=
</p>
|l10n-schedule=
<ul><li>  What is your project's key functionality?
|l10n-target-date=
</li></ul>
}}
<p>Localize the FFF to Kyrgyz
</pre>
</p>
Edit page to see entire form.
<ul><li>  Where will your project live?
[[category:NewL10nProjects]]
</li></ul>
</noinclude>
<ul><li>  What are your target locales?
 
</li></ul>
<includeonly>
<p>Kyrgyz
 
</p>
<div style="width: 300px; background-color:#CFCFCF; padding: 5px; font-size: .8em">Please use the "Edit with Form" link above to edit</div>
<ul><li>  What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
 
</li></ul>
{| class="wikitable"
<ul><li>  What are your available resources?
! Priority
</li></ul>
| [[l10n-priority::{{{l10n-priority|}}}]]
<p>25-strong localization team
|-
</p>
! Owner
<ul><li>  What is your project's expected life-cycle (i.e., short-term/long-term)?
| [[l10n-owner::{{{l10n-owner|}}}]]
</li></ul>
|-
<p>Long term: the project will be supported by the Kyrgyz community of localizers in Bishkek and Osh.
! Project length (in # of strings and words)
We will be ongoingly supporting the project in terms of adding new strings localizations.
| [[l10n-length::{{{l10n-length|}}}]]
</p>
|-
<ul><li>  What L10n requirements have you already defined?
! Description of target audience
</li></ul>
| [[l10n-targetaudience::{{{l10n-targetaudience|}}}]]
<table border="1">
|-
<caption><b>Considerations to make when identifying L10n requirements</b>
! Project home (Where will your project live?)
</caption>
| [[l10n-projecthome::{{{l10n-projecthome|}}}]]
<tr>
|-
<th scope="col"> Short-term
! Target locales
</th>
| [[l10n-locales::{{{l10n-locales|}}}]]
<th scope="col"> Examples
|-
</th>
! Locale expansion rate (What is your estimated rate of locale expansion per quarter?)
<th scope="col"> Long-term
| [[l10n-expansion::{{{l10n-expansion|}}}]]
</th>
|-
<th scope="col"> Examples
! Available L10n resources
</th></tr>
| [[l10n-resources::{{{l10n-resources|}}}]]
<tr>
|-
<td>L10n requirements must be simple </td>
! Project life-cycle
<td> </td>
| [[l10n-life-cycle::{{{l10n-life-cycle|}}}]]
<td> Use techniques to make updating the site much easier. </td>
|-
<td>
! Release schedule
</td></tr>
| [[l10n-schedule::{{{l10n-schedule|}}}]]
<tr>
|-
<td>Words </td>
! Target date
<td> </td>
| [[l10n-target-date::{{{l10n-target-date|}}}]]
<td> Updating content is laborious. Beware of L10n burnout. </td>
|}
<td>
 
</td></tr>
[[category:NewL10nProjects]]
<tr>
</includeonly>
<td>Palabras </td>
<td> </td>
<td> How "evergreen" is the content on your site? </td>
<td>
</td></tr>
<tr>
<td>Palavras </td>
<td> </td>
<td> How often do you plan to change your project? </td>
<td>
</td></tr></table>
<h2>Release schedule</h2>
<p>Identify the following as part of development phases:  
</p>
<ul><li>  Dates outlining development phases for the first localized releases.
</li></ul>
<p>2 months for the localized front end to go live
2 more months for bugs fixing and adding back end localizations
</p>
<ul><li>  Cost in days for each development phase.
</li></ul>
<p>two stages, each 60 days
</p>
<h2>Timeline to implementation</h2>
<p>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 <a href="https://docs.google.com/spreadsheet/ccc?key=0Al5H7QuXOsNZdGh0LXRQWlB6OTZGa2kzV2loRXpFT3c&amp;hl=en_US%7CLive#gid=0">Firefox Live timeline</a>.
Briefing the localization team about the localization procedures - by March 15
Distributing the tasks - by March 16
Feedback and Q&amp;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
</p>
<h1>Our response</h1>

Latest revision as of 15:04, 22 April 2013


{{l10n-priority=
|l10n-owner=
|l10n-length=
|l10n-targetaudience=
|l10n-projecthome=
|l10n-locales=
|l10n-expansion=
|l10n-resources=
|l10n-life-cycle=
|l10n-schedule=
|l10n-target-date=
}}

Edit page to see entire form.