From Fedora Project Wiki
(Created page with "= Zanata Removal = == Summary == While most Fedora project migrated to Weblate, the old translation platform still exists and needs to be removed (the community shouldn't ha...")
 
No edit summary
Line 48: Line 48:


Some project requiring Sign-off: https://docs.weblate.org/en/latest/admin/licensing.html#signed-off-by
Some project requiring Sign-off: https://docs.weblate.org/en/latest/admin/licensing.html#signed-off-by
Reducing translation impact in your repository:
* you can configure weblate's components to save po files without any line number, saving many useless commits if you do frequent pot updates
* you can configure weblate's components to squash commits per author to limit the number of commits


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 65: Line 70:
** if not, open a ticket to l10n team: https://pagure.io/fedora-l10n/tickets
** if not, open a ticket to l10n team: https://pagure.io/fedora-l10n/tickets


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/9537 #9537]
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->


* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: No
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


* Trademark approval: N/A (not needed for this Change)
* Trademark approval: No
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
Line 79: Line 80:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
This impact upstream projects, not the delivered operating system.
Worse case scenario: less translations reach upstream.


== How To Test ==
== How To Test ==
Line 97: Line 99:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
Project is in readonly in https://fedora.zanata.org
Project exists in Fedora Weblate: https://translate.fedoraproject.org
Modification done in Fedora Weblate can be seen in upstream repository.


== User Experience ==
== User Experience ==
Line 110: Line 114:
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->
-->
This improve the experience of users that don't speak English correctly (90% of the world, source CLDR + Wikipedia) or not at all (80% of the world, source CLDR + Wikipedia)


== Dependencies ==
== Dependencies ==
Line 115: Line 121:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)  
None (this doesn't impact packaging)


== Contingency Plan ==
== Contingency Plan ==


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: (What to do?  Who will do it?) No contingency, Zanata won't be kept any longer, we already gave 6 more month to let project migrate at their own pace to the new system <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: none <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
Line 131: Line 137:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
 
* [[L10N/Translate_on_Weblate|How to translate on Weblate?]]
* List of Weblate file formats support: https://docs.weblate.org/en/latest/formats.html
* Weblate's FAQ: https://docs.weblate.org/en/latest/faq.html
* Weblate evolves fast, reading changes is interesting: https://docs.weblate.org/en/latest/changes.html


== Release Notes ==
== Release Notes ==

Revision as of 12:10, 18 June 2020

Zanata Removal

Summary

While most Fedora project migrated to Weblate, the old translation platform still exists and needs to be removed (the community shouldn't have to go to multiple place to contribute, and nobody assume Zanata maintenance).

Owner

Current status

  • Targeted release: Fedora 33
  • Last updated: 2020-06-18
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

We created a migration page to follow projects migration from Zanata to Weblate: L10N Move to Weblate.

Remaining projects should either: migrate to Weblate or move to another translation platform.

Feedback

Weblate configuration: unless your team knows Weblate, Jibecfed will do first configuration and make you admin of your project so you can add more components.

Pull request support for Pagure: it is unlikely this features lands in Weblate before Zanata removal. Suggestion is to allow https://pagure.io/user/weblatebot for commits.

Some project requiring Sign-off: https://docs.weblate.org/en/latest/admin/licensing.html#signed-off-by

Reducing translation impact in your repository:

  • you can configure weblate's components to save po files without any line number, saving many useless commits if you do frequent pot updates
  • you can configure weblate's components to squash commits per author to limit the number of commits

Benefit to Fedora

This makes the distribution more efficient:

  • translators have one single place for translating, and get many interesting features (alerts, comments, etc.)
  • newcomers can directly translate without approval
  • maintainer have less automation to do (po updates, etc.)
  • reduce complexity (all in one place) & infrastructure costs

Scope

  • Proposal owners: continue to answer questions from upstream projects and translators
  • Other developers:
  • Release engineering: #9537
  • Policies and guidelines: No
  • Trademark approval: No

Upgrade/compatibility impact

This impact upstream projects, not the delivered operating system. Worse case scenario: less translations reach upstream.

How To Test

Project is in readonly in https://fedora.zanata.org Project exists in Fedora Weblate: https://translate.fedoraproject.org Modification done in Fedora Weblate can be seen in upstream repository.

User Experience

This improve the experience of users that don't speak English correctly (90% of the world, source CLDR + Wikipedia) or not at all (80% of the world, source CLDR + Wikipedia)

Dependencies

None (this doesn't impact packaging)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) No contingency, Zanata won't be kept any longer, we already gave 6 more month to let project migrate at their own pace to the new system
  • Contingency deadline: none
  • Blocks release? No
  • Blocks product? No

Documentation

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Zanata_removal&oldid=579596"