Future migration plan
This page is a work-in-progress content about L10N Move to Weblate

Context

The Fedora Localization Project handle:

an informal global team, handling schedule, planning, projects communication and follow-up improvements regarding localization in the Fedora project itself and the Fedora products, administrating FAS' cvs_l10n group, administrating the translation platform, resolving conflicts
- this team only have one formal role: L10N Administrator
at least 86 formal translation teams, as described in L10N Teams
- theses teams have at least one L10N Coordinator (we suggest to have more than one),
- theses teams may use review process inside Zanata (teams with more than 10 000 words reviewed: pt-BR hu ru fr sq hr id)
- every translator follows an onboarding process: L10N/Guide#Becoming_a_Fedora_Translator

Current processes

User go on https://fedora.zanata.org they have a welcoming page with all the required information, information linked to three different pages (L10N/Translate on Zanata from fedora wiki, two on docs.zanata.org)
- A newcomer trying to login will:
  - be redirected to the Fedora Account System (FAS), have to fulfil multiple steps, accept FPCA, then to connect again to Zanata to create an account inside the application, validate the account creation.
  - ask to join a team. Someone will manually validate the join request. Sending an email to the mailing list is often mandatory (which often, aren't part of the fedora infrastructure... They have to find the L10N Teams page to get this information)
  - ask to joint the cvsl10n group to be a "CLA+1" and have the right to edit the wiki and vote
Once in a team, you can do whatever change you like, nobody will know

Strengths:

Weaknesses:

There is no communication between project managers and translators: we don't know when a new project/document/content is to translate
There is no team management feature: we don't know who is working and what was changed
There is no community management features: there is no activity information of the platform (new users, biggest contributors, best teams, etc.)

Risks:

Opportunities:

Visibility on actions:

Description	Reasons, if required	Priority
As a translator, I want to easily access the translation activity of my language team so that knowing active contributors is easy.	.	.
As a translator, I want to be know the translation activity of my language team on a document so that I can review changes.	.	.

Notification and alerts:

Description	Reasons, if required	Priority
As a translator, I'm able to get notification if someone does its first contribution to my language team so that I can easily welcome and review changes.	.	.
As a translator, I'm able to get notification for events on a document so that I can easily keep up the translation of a document that matters to me.	.	.

Priority Management:

Description	Reasons, if required	Priority
As global l10n coordinator, I'm able to edit the welcome screen with text and images so that newcomer have information to join the community.	.	.
As global l10n coordinator, I'm able to highlight specific projects or groups in the welcome page so that contributors know what are the priorities.	.	.
As global l10n coordinator, I'm able create list of components so that contributors can easily find a group of related components.	.	.
As global l10n coordinator, I'm able create list of projects so that projects with different communities can be easily identified.	.	.