Template:L10nProjectRequestForm: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 16: Line 16:
*  What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
*  What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?


*  What is your available budget and resources?
*  What are your available resources?


*  What is your project's expected life-cycle (i.e., short-term/long-term)?
*  What is your project's expected life-cycle (i.e., short-term/long-term)?

Revision as of 18:21, 20 January 2012

What we need from you

Project owners

Who we will be collaborating with on your team?

Project scope outline

Identify the following as part of your project's scope:

  • What is the estimated length of localizable content (in number of strings and words)?
  • What is your project's key functionality?
  • Where will your project live?
  • What are your target locales?
  • What is your estimated rate of L10n expansion (i.e., approx. number of L10ns you hope to add each quarter)?
  • What are your available resources?
  • What is your project's expected life-cycle (i.e., short-term/long-term)?
  • What L10n requirements have you already defined?
Considerations to make when identifying L10n requirements
Short-term Examples Long-term Examples
L10n requirements must be simple Use techniques to make updating the site much easier.
Words Updating content is laborious. Beware of L10n burnout.
Palabras How "evergreen" is the content on your site?
Palavras How often do you plan to change your project?

Release schedule

Identify the following as part of development phases:

  • Dates outlining development phases for the first localized releases.
  • Cost in days for each development phase.

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 Firefox Live timeline.

Our response