Template:L10nProjectRequestForm: Difference between revisions

Jump to navigation Jump to search

Template:L10nProjectRequestForm (view source)

Revision as of 14:49, 5 March 2012

423 bytes added ,  5 March 2012
Undo revision 403876 by Eolonir (talk)
(Undo revision 403876 by Eolonir (talk))
Line 1: Line 1:
__NOTOC__
<p>__NOTOC__
=What we need from you=
</p>
 
<h1>What we need from you</h1>
==Project owners==
<h2>Project owners</h2>
Who we will be collaborating with on your team?
<p>Who we will be collaborating with on your team?
Alaksiej Lavončyk, alaksiej.lavoncyk@tol.org, project coordinator
</p>
Jan Praŭdzin, inszyby@gmail.com, project coordinator
<h2>Project scope outline</h2>
 
<p>Identify the following as part of your project's scope:
==Project scope outline==
</p>
Identify the following as part of your project's scope:
<ul><li> What is the estimated length of localizable content (in number of strings and words)?
* What is the estimated length of localizable content (in number of strings and words)?
</li></ul>
The whole interface of Mozille Firefox 10 into Kyrgyz language ( I understand so that we should receive this file form you?)
<p>The whole interface of Mozille Firefox 10 into Kyrgyz language ( I understand so that we should receive this file form you?)
 
</p>
* What is your project's key functionality?
<ul><li> What is your project's key functionality?
Localize the FFF to Kyrgyz
</li></ul>
 
<p>Localize the FFF to Kyrgyz
* Where will your project live?
</p>
 
<ul><li> Where will your project live?
* What are your target locales?
</li></ul>
Kyrgyz
<ul><li> What are your target locales?
 
</li></ul>
* What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
<p>Kyrgyz
 
</p>
* What are your available resources?
<ul><li> What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
25-strong localization team
</li></ul>
 
<ul><li> What are your available resources?
* What is your project's expected life-cycle (i.e., short-term/long-term)?
</li></ul>
Long term: the project will be supported by the Kyrgyz community of localizers in Bishkek and Osh.
<p>25-strong localization team
</p>
<ul><li> What is your project's expected life-cycle (i.e., short-term/long-term)?
</li></ul>
<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.  
We will be ongoingly supporting the project in terms of adding new strings localizations.  
 
</p>
* What L10n requirements have you already defined?
<ul><li> What L10n requirements have you already defined?
 
</li></ul>
{| border="1"
<table border="1">
|+'''Considerations to make when identifying L10n requirements'''
<caption><b>Considerations to make when identifying L10n requirements</b>
! scope="col" | Short-term  
</caption>
! scope="col" | Examples
<tr>
! scope="col" | Long-term
<th scope="col"> Short-term
! scope="col" | Examples
</th>
|-
<th scope="col"> Examples
|L10n requirements must be simple || || Use techniques to make updating the site much easier. ||
</th>
|-
<th scope="col"> Long-term
|Words || || Updating content is laborious. Beware of L10n burnout. ||
</th>
|-
<th scope="col"> Examples
|Palabras || || How "evergreen" is the content on your site? ||
</th></tr>
|-
<tr>
|Palavras || || How often do you plan to change your project? ||
<td>L10n requirements must be simple </td>
|}
<td> </td>
 
<td> Use techniques to make updating the site much easier. </td>
==Release schedule==
<td>
Identify the following as part of development phases:  
</td></tr>
* Dates outlining development phases for the first localized releases.  
<tr>
2 months for the localized front end to go live
<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
2 more months for bugs fixing and adding back end localizations
* Cost in days for each development phase.
</p>
two stages, each 60 days
<ul><li> Cost in days for each development phase.
 
</li></ul>
==Timeline to implementation==
<p>two stages, each 60 days
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].
</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
Briefing the localization team about the localization procedures - by March 15
Distributing the tasks - by March 16
Distributing the tasks - by March 16
Feedback and Q&As - by March 20
Feedback and Q&amp;As - by March 20
Front end localization - by May 1
Front end localization - by May 1
Testing - by May 10
Testing - by May 10
Line 65: Line 93:
Testing - by June 10
Testing - by June 10
Going live - by June 15
Going live - by June 15
 
</p>
=Our response=
<h1>Our response</h1>
Eolonir
6

edits

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

Navigation menu