Note: October 31 is the final day in which requests can be made. All requests made after October 31st will be marked as WONTFIX.

Since localization is a unique contribution area requiring the development of certain skills to be successful, regular community meetups help communities to establish best practices among themselves on how to translate content across their Mozilla localizations. These meetups increase localization consistency for users, build relevant skills in volunteers for their future success, and provide training for veteran and new localizers on changes to the localization process. This document outlines the process whereby trusted localizers (those with Translator or Manager roles in Pontoon) can work with Resource Reps to plan their own community meetups and request financial support from the l10n-drivers.

Criteria

Event requests are reviewed against the following criteria by the l10n-drivers:

Event organization

• Your event has a Mozilla Resource Rep involved and committed to seeing the event through.
  • Rep does not have to be in the same country as the event. Visit this page to find your closest Resource Rep.
• Your event should be easily classified as one of the following event types:
  • Training on l10n tools and process
    • Training sessions on best practices when translating, testing localizations, and using Pontoon, Transvision, and Fluent.
  • Quality Review
    • Activities that focus on improving the quality of the community's localizations. Could include reviewing pending suggestions, creating or editing style guides, testing localizations, or fixing Pontoon or Transvision reported errors, etc.
  • L10n development (Pontoon, MT, etc.)
    • Activities that focus on improving the l10n toolchain at Mozilla. Could include fixing Pontoon bugs, fixing Transvision bugs, developing unique tools that use the Pontoon API, etc.
  • L10n sprint for newly launched Mozilla products (version 1.0)
    • Activities that result in a locale being included in version 1.0 of a new Mozilla product. Could include string translation, translation review, testing, etc.
• Your event has a clear list of deliverables that are consistent with the event type you've selected and are measurable.

Expenses

• A Mozilla Resource Rep will work with the event leaders to manage the event's finances.
  • 'Manage' meaning that the Resource Rep and the trusted Localizer agree on a plan for performing all transactions for the event.
• The following expenses are approved for events (see “Community/Intercommunity meet-ups” row, with some exceptions)
  • Air/train travel for organizers and participants
  • Accommodation for organizers and participants
  • Most transport for organizers and participants (determined case-by-case)
  • Venue fees
  • Meals for organizers and participants
  • Gear (locally printed, t-shirts are ok)
• Event is cost-efficient and has a detailed budget for each expense.

Length

• If most people must travel for more than one hour to reach the event location (door-to-door), the event should be two days, with two extra days for travel (three nights total). Example: if the event is on the weekend, Friday and Monday are travel days.
• Events (excluding travel days) should be no longer than two days.

Size

• Multi-locale events must be restricted to three localizers per community.
• Single-locale events can have no more than 10 localizers.
• L10n-drivers may attend your event and play a minor role once there.

Locations and timing

• In-country requests must be approved by l10n-drivers a minimum of one month in before the event’s date. International requests must be approved a minimum of two months before the event’s date.

Travel and lodging requirements

• All travel must be visa-free, with few exceptions (i.e., localizers should not require a visa to attend).
• Location needs to be easily accessible and conveniently located for most attending localizers (i.e., if a single locale event, event should be located in the city with the most participants).
• Localizers qualify for lodging if they've traveled more than one hour to reach the event location from their home.

How to make your request

1. Trusted localizers and a Resources Rep plan the event proposal with all necessary information (see above).
2. The Resources Rep fills out the budget request form in bugzilla and will CC the trusted localizers. Communications and logistics between Mozilla staff and event organizers will take place in that issue.
3. The Mozilla Reps Budget Wrangler (Kiki) will assign the issue to the l10n-drivers for review.
4. On Tuesdays, the l10n-drivers evaluate event proposals against the above criteria for l10n community events.
5. L10n-drivers notify event organizers of their event's status and whether changes need to be made to their proposal in bugzilla.
6. If approved, the Mozilla Reps Budget Wrangler (Kiki) will process payment to the Resources Rep. Resources Rep makes sure that those funds are available for processing all payments for the event, according to the agreed upon plan between the Resources Rep and the trusted localizers.
7. If airplane travel is required, the l10n-drivers will work with the trusted localizers to gather necessary information for the travel agency to process travel bookings.
8. After the event, the Resources Rep collects all receipts and submits them to l10n-drivers in the event's bug.
9. Mozilla Rep and trusted localizers write and publish a blog post reporting on the event’s outcome and share it in the bug.