From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...")
 
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
= Distribution Localization statistics
 
{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
= Change Proposal Name <!-- The name of your change proposal --> =


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.  
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.  
Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
Generate per language statistics about the current localization support for the whole Fedora Operating System.
Provide a static website with results and useful files for translators (as an example: translation memories).


== Owner ==
== Owner ==
<!--
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
This should link to your home wiki page so we know who you are.
-->
* Name: [[User:jibecfed|Jean-Baptiste Holcroft]]
* Name: [[User:jibecfed|Jean-Baptiste Holcroft]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
* Email: <jean-baptiste@holcroft.fr>
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 38: Line 30:
<!-- [[Category:SystemWideChange]] -->
<!-- [[Category:SystemWideChange]] -->


* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/34 | Fedora 34]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 53: Line 45:
== Detailed Description ==
== Detailed Description ==


<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Language support is a transversal activity, there is no way to know the actual language support provided by Fedora as an Operating System.
 
Because language support and translations are part of each upstream software, the Linux language community is as spread as the Free Libre and Open Source community is.
 
The ability to share efforts is limited (with data, tools, etc.):
 
* because translators often have a low level of technical knowledge,
* because development experts are more keen to use English by default, and don't know much about languages support requirements,
* because of the complexity to get an overview of the current localization status of the Linux community.
 
Debian did something similar (20 years ago) https://www.debian.org/international/l10n/ (code: https://salsa.debian.org/webmaster-team/webwml/-/commits/master/english/international/l10n/scripts/transmonitor-check)


== Feedback ==
== Feedback ==
* Why not reuse the code from Debian? This source code is deeply integrated with Debian infrastructure, and uses a language that doesn't allow to share easily with existing i18n/l10n tooling/libraries. We do use translation-finder used by Weblate, language data from Weblate, polib from David Jean Louis, Translate Toolkit from translatehouse.org.


<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
Line 61: Line 65:
== Benefit to Fedora ==
== Benefit to Fedora ==


<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved? -->
 
 
      Be sure to include the following areas if relevant:
Help the Linux community to face understand the language support challenges by providing measurement.
      If this is a major capability update, what has changed?
Increase the contributor effectiveness by providing translation memories and other tools.
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
Opens the possibility to change the translation file release process.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.  


    When a Change has multiple benefits, it's better to list them all.
== Scope ==


    Consider these Change pages from previous editions as inspiration:
All of the work is isolated, as long as dnf works, the automation works. The closer to mirror the cheaper it is for network cost (all Fedora is downloaded at each execution).
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


== Scope ==
* Proposal owners:
* Proposal owners:
* [[User:Darknao|Francois Andrieu]] integrate the existing scripts into containers to allow execution into openshift
* Infra team:
** provide some space for script execution (50 GB per release)
** provide a location for static website (about 2 GB per release, may increase over time)
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


Line 163: Line 153:
== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
A draft with simplistic template is there: https://jibecfed.fedorapeople.org/partage/fedora-localization-statistics/f32/language/fr/
Code and "documentation" are there: https://pagure.io/fedora-localization-statistics


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Revision as of 21:42, 8 December 2020

= Distribution Localization statistics

Summary

Generate per language statistics about the current localization support for the whole Fedora Operating System. Provide a static website with results and useful files for translators (as an example: translation memories).

Owner

Current status

  • Targeted release: Fedora 34
  • Last updated: 2020-12-08
  • 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

Language support is a transversal activity, there is no way to know the actual language support provided by Fedora as an Operating System.

Because language support and translations are part of each upstream software, the Linux language community is as spread as the Free Libre and Open Source community is.

The ability to share efforts is limited (with data, tools, etc.):

  • because translators often have a low level of technical knowledge,
  • because development experts are more keen to use English by default, and don't know much about languages support requirements,
  • because of the complexity to get an overview of the current localization status of the Linux community.

Debian did something similar (20 years ago) https://www.debian.org/international/l10n/ (code: https://salsa.debian.org/webmaster-team/webwml/-/commits/master/english/international/l10n/scripts/transmonitor-check)

Feedback

  • Why not reuse the code from Debian? This source code is deeply integrated with Debian infrastructure, and uses a language that doesn't allow to share easily with existing i18n/l10n tooling/libraries. We do use translation-finder used by Weblate, language data from Weblate, polib from David Jean Louis, Translate Toolkit from translatehouse.org.


Benefit to Fedora

Help the Linux community to face understand the language support challenges by providing measurement. Increase the contributor effectiveness by providing translation memories and other tools. Opens the possibility to change the translation file release process.

Scope

All of the work is isolated, as long as dnf works, the automation works. The closer to mirror the cheaper it is for network cost (all Fedora is downloaded at each execution).

  • Proposal owners:
  • Francois Andrieu integrate the existing scripts into containers to allow execution into openshift
  • Infra team:
    • provide some space for script execution (50 GB per release)
    • provide a location for static website (about 2 GB per release, may increase over time)


  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

A draft with simplistic template is there: https://jibecfed.fedorapeople.org/partage/fedora-localization-statistics/f32/language/fr/ Code and "documentation" are there: https://pagure.io/fedora-localization-statistics

N/A (not a System Wide Change)

Release Notes