Barcelona Goals and Agenda

[gueroJeff]

Core focus:

• Rebuilding communities
• Evangelizing localized products
• Quality
• Training on tooling changes

Outcomes:

• Localizers can recruit and train new localizers.
• Each community's language resources (style guides, term lists) are created & up-to-date.
• Marked improvement in localization quality for l10n projects.
• Localizers trained in translation process best practices.

Format:

Day 1:

Morning

• Spectograms
• Org updates

Afternoon

• Common goals breakouts
• Free time (goals work, 1:1 time with l10n-drivers, community visits with l10n-drivers)

  Day 2:

• Common goals breakouts
• Free time (goals work, 1:1 time with l10n-drivers, community visits with l10n-drivers)

Planning:

The l10n-drivers will coordinate among l10n communities to identify common goals and split up time into breakout sessions. Otherwise, we will only need a few hours in the first morning to accomplish our own goals (give Mozilla org updates, roadmap updates, l10n program updates, etc.).

The content and goals for the afternoons and the second morning are entirely open for the communities to fill with what they feel is most worthy of their time. Here are some questions that can help guide defining what this time could be filled with:

• What does the l10n community hope to accomplish during the hackathon?
• Are open, group discussions more valuable or are breakouts more valuable?
• Would there be value in holding an open public time during the hackathon?
• What does the l10n community hope to bring back to their larger community?

[gueroJeff]

Wiki event page created: https://wiki.mozilla.org/L10n:Meetings/2017_Barcelona_Workshop

Please begin planning goals and agenda.

[kberov]

Hello @gueroJeff , Are we expected to add to the wiki page what we think needs to be done on the workshop for the respective localization community? As this is my first participation in such event I am completely unsure what will be discussed (although written above). My plan is very simple.

1. Have finally the issue about adding BG language to the MDN page resolved.
2. Find out what needs to be done (although I have some specific vision, which can be wrong of course) to attract more translators in Bulgarian for MDN.
3. Come up with a list of article with highest priority to be translated in BG which will attract more Bulgarian visitors and some of them will contribute.
4. Find out how to manage the contributing process, both with help tot the translators - technical and editorial reviews.
5. Find out is it possible to get some sponsorship from Mozilla for all the translation, editorial and organizational work being done for a longer period of time - not just sporadic contributions.

[facyber]

Goals for my (Serbian) community are:

• New Style Guide (editing Wiki page and creating docx and pdf format of a guide)
• Finishing not translated projects on Pontoon (Mozilla.org > Firefox Accounts > Appstores, sorted by priorities)
• If we manage to finish all this before the end of event, we will continue with translation of Lightning Aurora. As there are a lot of untranslated strings, we will translate as many as we can.

[gueroJeff]

@kberov Commenting in this issue is enough. It makes an open discussion about these easy to manage.

[kberov]

@gueroJeff Thanks!

[gocemitevski]

Goals for the Macedonian community:

• Create a Style Guide
• Make substantial progress with the localization of Firefox Aurora -- try to reach at least 80% completeness
• Figure out how to rebuild our community

[gastaz]

Goals for the Ligurian (lij) community:

• Reach the 100% of completion of Firefox Aurora (now 96%)
• How to find new volunteers for ligurian localization
• Decide if add new projects for ligurian
• Create style guide

[gion-andri]

The goals for the Romansh (rm) community:

• Clean up our terminology list, make it more structured
• Make sure, all suggested translations are reviewed
• Complete translation of Firefox Aurora (currently at 95%)
• Discuss, how we could modify our team’s translation process to avoid suggestions not going into the product if nobody has time for the review

[HrantOhanyan]

Goals for the Armenian community:

• Update the Style Guide.
• Make a decision to add new projects for localization.
• Review existing suggestions in all platforms.
• Translate missing strings in Firefox, Firefox for Android and Thunderbird.

[sn-o-w]

Goals for the Romanian community:

• Update the style guide
• Complete Focus for iOS, Firefox for iOS, Firefox Accounts projects
• Translate and/or update top 10 articles from SUMO
• Discuss about the state of the community and how to find new localizers for Romanian locale

Off-topic: @gueroJeff little typo on wiki page: EUR is used in Barcelona, not INR :)

[julen]

As for Basque:

• Research on deploying a solution for gathering TM and terminology (not limited to Mozilla)

[meskobalazs]

Goals for the Hungarian team:

• Update our existing, but outdated style guide
• Discuss the revival of our glossary
• Make a strategy for MDN translation (decide what to translate, and what not; involvement of new translators)
• Compile the list of features needed in Pontoon, to allow the migration of all projects from Pootle
• Discuss the state of the local community

[AndreiTarkovski]

Goals for Slovenian team:

• Enhance glossary
• Define ways to expand localisation community
• Build 1-stop-point for all useful linguistic resources
• Reach 100 % progress

[jlgl10nes]

Goals for the Spanish team

• Discuss about the state of the community, find and support new contributors (es-ES and es)
• Documentation review and update (wiki, style guide, glossary)
• Tools and project request criteria

[ghost]

Goals for French team:

• Start a usable guide in French for newcomers on the new not-so-localizer-friendly SUMO platform :smile:
• Prepare material and docs in order to welcome high-level translators we invited for their first contribution on Mozilla on April 8-9th in Paris. It includes conf to introduce them to various l10n tasks, tools and process, and also find a range of activities to be proposed during the week-end (docs, pages, tech/non-tech articles)
• Review and validation of the pending suggestions on Pontoon.