Project Onboarding: Difference between revisions

From Localization Lab Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 18: Line 18:
:*Do you have regular beta releases that you can include partial and unreviewed translations in?
:*Do you have regular beta releases that you can include partial and unreviewed translations in?
:*Do you have a demo that regularly updates translations?
:*Do you have a demo that regularly updates translations?
*Can you bundle string updates so that there is not a continual flow of new strings?


'''Usability'''<br>
'''Usability'''<br>
Line 28: Line 29:
*Do you have a project style guide?
*Do you have a project style guide?
*Should your project name be transcribed or translated?
*Should your project name be transcribed or translated?
*


'''Communication'''<br>
'''Communication'''<br>
Line 36: Line 36:
*Where do you communicate project updates and news?
*Where do you communicate project updates and news?
*Can you announce when new translations and localization updates are released for your project?
*Can you announce when new translations and localization updates are released for your project?
*Can you provide recognition for localizers who have worked on your project?
*Is there dedicated staff to review open issues in the project on a weekly basis?
*Are you willing to engage with contributors in a project demo, Q&A or AMA?


'''Users & Languages'''<br>
'''Users & Languages'''<br>
Line 56: Line 57:
*Can you link to your project in the translation platform on your website?
*Can you link to your project in the translation platform on your website?
*Can you recognize collaboration with Localization Lab on your website?
*Can you recognize collaboration with Localization Lab on your website?
*Can you recognize localizers in release notes, in app, on social media or on your website?

Latest revision as of 08:47, 10 September 2018

Project Onboarding and Follow-Up Questionnaire:

Localization Workflow

  • Do you have an existing localization workflow?
  • Please detail your release cycle as much as possible.
  • How often are you able to integrate translations into your project?
  • How many languages are you able to integrate into your project? Do you have any limitations on adding new locales?
  • If there are limitations, which languages are you able to include in your project?
  • Do you have dedicated staff to respond to localization-related questions?
  • Can you provide a string freeze of at least one week prior to release for localization?
  • How easily can you update source text?
  • Which of your project resources are highest priority?
  • Can you incorporate partial translations?
  • Should you use partial translations?
  • Do you agree to only include reviewed translations in builds?
  • Can you provide screenshots for strings?
  • How can volunteers demo and test translations in context?
  • Do you have regular beta releases that you can include partial and unreviewed translations in?
  • Do you have a demo that regularly updates translations?
  • Can you bundle string updates so that there is not a continual flow of new strings?

Usability

  • What is your process for receiving, prioritizing and implementing user feedback?
  • Do you have a user feedback framework?

Linguistic

  • Do you have an existing glossary of terms used in your project?
  • Are there any neologisms specific to your project?
  • Do you have a project style guide?
  • Should your project name be transcribed or translated?

Communication

  • Which platforms do you use to communicate with your team and project contributors?
  • Do you have any existing localization communication platforms?
  • Which platforms do you use to manage bug and feature requests?
  • Where do you communicate project updates and news?
  • Can you announce when new translations and localization updates are released for your project?
  • Is there dedicated staff to review open issues in the project on a weekly basis?
  • Are you willing to engage with contributors in a project demo, Q&A or AMA?

Users & Languages

  • Who is your target user?
  • What are your language priorities and why?
  • Please provide a use case for each of your language priorities.
  • Which audience(s) are you trying to reach short term?
  • Which audience(s) are you trying to reach long term?
  • Do you have any organizational partners who are requesting your project in a specific language?

Marketing & Outreach

  • Do you have an outreach strategy to market your tool post-localization?

Funding

  • Do you have any funding to support localization work?
  • Can you write localization funding into future proposals?

Misc.

  • Can you link to your project in the translation platform on your website?
  • Can you recognize collaboration with Localization Lab on your website?
  • Can you recognize localizers in release notes, in app, on social media or on your website?