From 2a25e44ecfdc354b7212642e78595982728c0c83 Mon Sep 17 00:00:00 2001 From: peartown Date: Mar 25 2024 23:25:44 +0000 Subject: Some Antora-asciidoc formatting changes, few trivial text modifications in index.adoc hosting.adoc --- diff --git a/modules/ROOT/pages/hosting.adoc b/modules/ROOT/pages/hosting.adoc index 008470e..c2700b1 100644 --- a/modules/ROOT/pages/hosting.adoc +++ b/modules/ROOT/pages/hosting.adoc @@ -6,31 +6,31 @@ include::{partialsdir}/attributes.adoc[] == Fedora's online translation platform -The Fedora Project runs {WEBLATE}[a Weblate instance] available at {WEBLATE}, which is used for translation of Fedora subprojects be it a software development project, a website or the documentation. +The Fedora Project runs a web-based online translation platform powered by https://weblate.org[Weblate]. This Fedora {WEBLATE}[Weblate instance] is available at {WEBLATE} and is used by Fedora translators for translating Fedora subprojects, be it a software development project, a website or the documentation. === Considerations to upstream projects -In line with its vision of "a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities" any free and open source software project is welcome to use this platform. +In line with the Fedora Project's vision of a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities any free and open source software project is welcome to use this platform. Few examples of motivation behind this approach: -* We support any project sharing the same values as the Fedora Project +* We support any project sharing the *same xref:project:ROOT:index.adoc[values]* as the Fedora Project * To improve upstream i18n support * A potential source of growth in the Fedora Community itself -As the Fedora l10n Team, we believe we are enough _"`mature and consistent with our values to be ready to welcome projects which have different technical choices from those the Fedora implements`"_ (Jean-Baptiste Holcroft, a member of the Fedora l10n Team, 2020). +As the Fedora l10n Team, we believe we are enough _"mature and consistent with our values to be ready to welcome projects which have different technical choices from those the Fedora implements"_ (Jean-Baptiste Holcroft, a member of the Fedora L10N Team, 2020). //// +Here could go what a project can expect from us +and on the other hand what they should be ready for + What makes us different with https://hosted.weblate.org? We are a structured community sharing open-source values with experienced translators -* Structured community: we have language teams -https://fedoraproject.org/wiki/L10N_Teams and a global translator -mailing list -https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/ -* we have open-source values: -https://docs.fedoraproject.org/en-US/project/#_freedom +* Structured community: we have language teams https://fedoraproject.org/wiki/L10N_Teams and a global {TRANSML}[translator +mailing list] +* we have open-source values: https://docs.fedoraproject.org/en-US/project/#_freedom Rule examples: * announce translation readiness to translators one week before release? @@ -38,38 +38,51 @@ Rule examples: * allow translation of website and man-pages //// - == Request a new translation project on Weblate In spite of the effort to be open and inclusive as much as possible, some associated concerns has led us to enforce it is not possible to create a translation project in the platform for everyone: * A translation of an (open source) project has to be ensured + _Not what an individual has decided to translate._ + * A project does not have to learn the weblate internals * Configuring Weblate is not so obvious + _Preferable is to do the first configuration for a project by us to reduce e.g. the migration costs._ -To make a request to set up a new translation project in {weblate}[Weblate], open a link:https://pagure.io/fedora-l10n/tickets[ticket]. + +In order to request an establishment of a new translation project in {weblate}[Weblate], open a link:https://pagure.io/fedora-l10n/tickets[ticket]. // Do we want to prepare a 'request template'? .Project request template -[example] +==== Project: // debbuild + Website: //https://github.com/debbuild/debbuild + Repository: //https://github.com/debbuild/debbuild + Name of the development branch: + Filemask: //po/* + Username: //ngompa + Optional: + Any announcement/warning you would like to display to the translators? (it will be displayed in Weblate) + A need to activate any specific checks? (this is a setting per component) + A need to automatically detect new translation files? (typical usecase: website translation with one translation file per page) +==== // These features has already been implemented in Weblate //// two features in Weblate to respect Fedora values: - set a lincence in every component -- licence change should trigger a notification +- licence change should trigger a notification //// // Should be a licence a part of the template? // [optional] what is the license of translation? (please use a code from https://spdx.org/licenses/) @@ -77,7 +90,6 @@ two features in Weblate to respect Fedora values: The specified username(s) will be set in the initial configuration of the project in Weblate as the project's administrator(s). -Once the initial configuration is made you will be notified. +Once the initial configuration is made the project contact(s) will be notified. Request made by upstream projects will be reviewed on an individual basis upon submission of the ticket. Priority will be given to projects that create software packaged for Fedora. // or 'by Fedora'?? - diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 1ee9295..02baf7a 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -7,7 +7,8 @@ image::translation.png[] The goal of the Fedora Localization Team (L10N) is to bring everything around Fedora (software, documentation, websites, and the culture) closer to local communities (countries, languages and in general cultural groups). Usually, this involves doing translations via PO files but is certainly not limited to that. -Beside the focus on translating, a part of the Fedora L10N Team's responsibilites is to develop and maintain neccessary tools and related processes which facilitate flows of a localization content between projects and translators; thus, projects can concentrate on development, while translators purely on translation. +Beside the focus on translating, a part of the Fedora L10N Team's responsibilites is to develop and maintain neccessary tools and related processes which facilitate flows of a localization content between projects and translators; +thus, projects can concentrate on development, while translators purely on translation. [[find-l10n]] == Where to find Fedora l10n team @@ -20,8 +21,8 @@ Questions or problems associated with localization can be filed as an issue in h == Next reading -Translators can continue with reading information about a xref:join.adoc[membership] of this team and our little guide to our online xref:weblate.adoc[translation platform]. +Translators, particularly those new-coming, can continue with reading information about a xref:join.adoc[membership] of this team and a short guide to our online xref:weblate.adoc[translation platform]. Some insights into our translation tooling used in the Fedora Project, for example for translating the https://docs.fedoraproject.org[Fedora documentation] can be found xref:doc_l10n.adoc[here]. - -Projects that are considering the use of our translation platform for their translations might find relevant information xref:hosting.adoc[here]. + +Projects considering the use of our translation platform for their translations might find relevant information xref:hosting.adoc[here].