From Fedora Project Wiki
m (rework structure and moved translation stories)
Line 14: Line 14:
= Current processes =
= Current processes =


= Requirements =
= User stories =
 
== Functional requirements ==


Visibility on actions:
Visibility on actions:
Line 38: Line 36:
|}
|}


Translation memory:
= System requirements =
{| class="wikitable"
|-
! Description !! Reasons, if required !! Priority
|-
| As a translator, I want to be able to query a translation memory containing a wide range of content so that knowledge beyond Fedora community is accessible.
 
This means: include in our translation memory translation from project out of the scope of the fedora translation community.|| . || .
|-
| As a localization coordinator, I can automatically complete existing translation using a translation memory using manual threshold so that useless operation for translators are limited. || . || .
|-
| As a localization coordinator, I have a tool to handle non-fedora translation content so that translation memory is continuously update.  || . || .
|-
| || . || .
|}
 
Automated translation:
{| class="wikitable"
|-
! Description !! Reasons, if required !! Priority
|-
| As a translator, I get suggestion from an automation translation engine based on a wide range of content to translate faster so that translation time is reduced.
 
This means we have a tool we fed with our translation memory and train it to have better result. || . || .
|-
| As a localization coordinator, I can automatically complete existing translation using an automation translation engine manual threshold so that useless operation for translators are limited.
|| . || .
|-
| As a translator, I can ask for an automated translation of a file and review suggestion so that starting a new translation is faster. || . || .
|}
 
== Technical requirements ==
=== Monitoring changes ===
=== Monitoring changes ===
=== Follow-up on updates pushed by projects ===
=== Follow-up on updates pushed by projects ===

Revision as of 17:02, 14 July 2019

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
  • 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 stories

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. . .

System requirements

Monitoring changes

Follow-up on updates pushed by projects

The display of the current translation progress

The ability to set specific translation process

Assistance in discussion between translators (from the same team and inter-languages)

Assistance with discussion with the project maintainer

The possibility to communicate globally on the platform (news, etc.)

Retrieved from "https://fedoraproject.org/w/index.php?title=L10N_Move_to_Weblate/Objective:_team_collaboration&oldid=547940"