From Fedora Project Wiki
(added current processes)
Line 25: Line 25:


'''Strengths''':
'''Strengths''':
1. Upstream project are autonomous and don't require anyone from l10n team to create/push or pull translation


'''Issues''':
# Upstream project are autonomous and don't require anyone from l10n team to create/push or pull translation
1. nobody get noticed when a new ''project'', ''version'' or ''document'' is created
 
2.
'''Weaknesses''':
 
# nobody get noticed when a new ''project'', ''version'' or ''document'' is created


'''Risks''':
'''Risks''':
1. Zanata packages may not be available anymore for project to push/pull content https://apps.fedoraproject.org/packages/zanata-platform/builds/
 
# Zanata packages may not be available anymore for project to push/pull content https://apps.fedoraproject.org/packages/zanata-platform/builds/
 
'''Opportunities''':
 
# ...


= User stories=
= User stories=

Revision as of 06:33, 15 July 2019

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

Context

The Fedora Localization project has a few groups in https://fedora.zanata.org:

  • Upstream project, organized in two categories
    • main Following Fedora development cycle
    • upstream Not following Fedora development cycle
  • Fedora Project specific content:

In addition, we have two groups aiming to help prioritization:

  • Priority Packages List of priority packages, documentation and websites for the upcoming Fedora release
  • rhel Branches for Red Hat Enterprise Linux

Current processes

  • Any Fedora contributor can come an create a new translation project.
  • Inside Zanata, documents for a project are grouped into versions. For simple projects, it is typical to create a single version named 'master'. Other projects use workflows in which there is a version under active development, and one or more versions that are being maintained in a stable state with only some minor changes. Grouping these related versions under the same project allows for easier reuse of translations between versions. See doc for details.
  • Multiple files format are theoretically supported by Zanata, but only gettext format really matter.
    • SELECT contentType, count(id) FROM hdocument GROUP BY contentType, shows 12702 application/x-gettext and 137 text/plain.
    • Default file type by project: File 12, Gettext 80, NULL 23, Podir 5, Properties 2, Xliff 1, Xml 1

Strengths:

  1. Upstream project are autonomous and don't require anyone from l10n team to create/push or pull translation

Weaknesses:

  1. nobody get noticed when a new project, version or document is created

Risks:

  1. Zanata packages may not be available anymore for project to push/pull content https://apps.fedoraproject.org/packages/zanata-platform/builds/

Opportunities:

  1. ...

User stories

File formats:

Description Reasons, if required Priority
As a project maintainer, I want to be able to push/pull translation files with the following formats : po n/a MVP

Interaction:

Description Reasons, if required Priority
As a project maintainer, I want to have a direct connection between the translation platform and my project repository Make sure there is no delay. TBD
As a project maintainer, I want to have a manual connection between the translation platform and my project repository Pull/push mecanism as we currently have with Zanata. MVP
As a ‘’’???’’’, I want to be able to interact with the translation platform using an API. TBD

Quality checks:

Description Reasons, if required Priority
As a project maintainer, I can set/unset some technical checks. programming langage checks TBD

System requirements

supported file formats

synchronization with the source repository

automation support tools

translation quality checks

the interface possibilities