Skip survey header

Mozilla l10n communication channels

L10n communication channels survey

Hello! The l10n-drivers are currently evaluating our communication channels. We'll be discussing making some changes to the way we communicate globally about l10n in the next month. We want your feedback about our current communication channels, where we can improve communication for the whole l10n program, and what communication channels we need to branch into in 2017.



Please take 5 minutes to give us your feedback. This survey will close on 24 May 2017.
2. Please rank the following Mozilla l10n global communication channels according to how frequently you pay attention to them (1 = most, 7 = least). *This question is required. Note: for the following table each column is restricted to a single answer across all rows.
1234567
3. How often do you check your top ranked communication channel? *This question is required.
4. Which of the following communication channels does your l10n community use to communicate with one another? Please choose all that apply. *This question is required.
  • * This question is required.
5. Do you feel we should branch out into new communication channels? *This question is required.
6. Please rank the following communication channels in order of priority for the l10n-drivers to incorporate into our global l10n communication channels (1 = highest priority, 8 = lowest priority).

We understand you may not be familiar with all of these. Please do your best to rank them according to those you know and feel should be prioritized. *This question is required. Note: for the following table each column is restricted to a single answer across all rows.
12345678
6. Do you feel there are too many or few details in emails the l10n-drivers (from Flod, Pike, Pascal, Jeff, Matjaz, Stas, Gandalf, Delphine, Peiying, or Arky) send to the mailing lists? *This question is required.
7. We send a Firefox l10n report at the beginning of each cycle to the dev-l10n mailing list and the l10n blog. In that report, we identify critical dates for Firefox & Firefox for Android, their volume of new strings & context, the percentage of localization coverage we acheived for a release cycle, and new locales that have shipped.

Is this report helpful for you to complete and sign-off on your localizations each cycle? *This question is required.
8. We regularly send out messages to the dev-l10n mailing list when there's a new product/project available to localize (e.g., Firefox for iOS, Firefox OS, etc.). Are these messages helpful for you to complete and sign-off on these localizations? *This question is required.
9. We regularly send out messages to the dev-l10n-web mailing list when there's been a relevant push of strings on mozilla.org. Are these messages helpful for you to remain up-to-date with your web l10n projects? *This question is required.
10. We regularly send out messages to the dev-l10n mailing list when gaia-l10n updates to point out useful changesets. Are these messages helpful for you to complete your Firefox OS localizations? *This question is required.
11. We regularly send out messages to the dev-l10n mailing list when we break string freeze on Aurora. Are these messages helpful for you to complete and sign-off on your product localizations each cycle? *This question is required.
0%