Template:L10nProjectRequestForm: Difference between revisions

Jump to navigation Jump to search

Template:L10nProjectRequestForm (view source)

Revision as of 00:21, 15 March 2012

1,352 bytes removed ,  15 March 2012
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
<p>__NOTOC__
__NOTOC__
</p>
=What we need from you=
<h1>What we need from you</h1>
 
<h2>Project owners</h2>
==Project owners==
<p>Who we will be collaborating with on your team?
Who we will be collaborating with on your team?
</p>
==Project scope outline==
<h2>Project scope outline</h2>
Identify the following as part of your project's scope:
<p>Identify the following as part of your project's scope:
* What is the estimated length of localizable content (in number of strings and words)?
</p>
 
<ul><li> What is the estimated length of localizable content (in number of strings and words)?
* What is your project's key functionality?
</li></ul>
 
<p>The whole interface of Mozille Firefox 10 into Kyrgyz language ( I understand so that we should receive this file form you?)
* Where will your project live?
</p>
 
<ul><li> What is your project's key functionality?
* What are your target locales?
</li></ul>
 
<p>Localize the FFF to Kyrgyz
* What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
</p>
 
<ul><li> Where will your project live?
* What are your available resources?
</li></ul>
 
<ul><li> What are your target locales?
* What is your project's expected life-cycle (i.e., short-term/long-term)?
</li></ul>
 
<p>Kyrgyz
* What L10n requirements have you already defined?
</p>
 
<ul><li> What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
{| border="1"
</li></ul>
|+'''Considerations to make when identifying L10n requirements'''
<ul><li> What are your available resources?
! scope="col" | Short-term  
</li></ul>
! scope="col" | Examples
<p>25-strong localization team
! scope="col" | Long-term
</p>
! scope="col" | Examples
<ul><li> What is your project's expected life-cycle (i.e., short-term/long-term)?
|-
</li></ul>
|L10n requirements must be simple || || Use techniques to make updating the site much easier. ||
<p>Long term: the project will be supported by the Kyrgyz community of localizers in Bishkek and Osh.
|-
We will be ongoingly supporting the project in terms of adding new strings localizations.
|Words || || Updating content is laborious. Beware of L10n burnout. ||
</p>
|-
<ul><li> What L10n requirements have you already defined?
|Palabras || || How "evergreen" is the content on your site? ||
</li></ul>
|-
<table border="1">
|Palavras || || How often do you plan to change your project? ||
<caption><b>Considerations to make when identifying L10n requirements</b>
|}
</caption>
 
<tr>
==Release schedule==
<th scope="col"> Short-term
Identify the following as part of development phases:  
</th>
* Dates outlining development phases for the first localized releases.  
<th scope="col"> Examples
* Cost in days for each development phase.
</th>
 
<th scope="col"> Long-term
==Timeline to implementation==
</th>
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].
<th scope="col"> Examples
 
</th></tr>
=Our response=
<tr>
<td>L10n requirements must be simple </td>
<td> </td>
<td> Use techniques to make updating the site much easier. </td>
<td>
</td></tr>
<tr>
<td>Words </td>
<td> </td>
<td> Updating content is laborious. Beware of L10n burnout. </td>
<td>
</td></tr>
<tr>
<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 &lt;a href="https://docs.google.com/spreadsheet/ccc?key=0Al5H7QuXOsNZdGh0LXRQWlB6OTZGa2kzV2loRXpFT3c&amp;hl=en_US%7CLive#gid=0"&gt;Firefox Live timeline&lt;/a&gt;.
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>
Jbeatty
Account confirmers, canmove, Confirmed users
2,357

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/407949"

Navigation menu