Translation status

34 Strings 0%
Browse Translate
802 Words 0%
5,311 Characters 0%

Strings status

Strings Words Characters
34 802 5,311
All strings Browse Translate Zen
34 802 5,311
Unfinished strings Browse Translate Zen
34 802 5,311
Untranslated strings Browse Translate Zen
1 1 10
Strings with suggestions Browse Translate Zen
33 801 5,301
Unfinished strings without suggestions Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/council
Instructions for translators

Mailing list for translators: <trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/council.git
Repository branch master
Last remote commit automatic update of pot/po files ca0637dea
♪ I'm a bot, bot, bot ♪ authored a month ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) 81e89aa40
User avatar farribeiro authored 2 weeks ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-council/nav/
File mask po/*/master/pages/historical/board_stable_updates_vision.po
Translation file Download po/te/master/pages/historical/board_stable_updates_vision.po
Last change Oct. 20, 2023, 10:03 p.m.
Last change made by None
Language Telugu
Language code te
Text direction Left to right
Number of speakers 101,457,360
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 34 802 5,311
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 2% 1 1% 1 1% 10
Untranslated strings 100% 34 100% 802 100% 5,311
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 13 changes 0 changes 0 changes 0 changes
DecJanFebMarAprMayJunJulAugSepOctNov

Quick numbers

802
Hosted words
34
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
—
—
Contributors
—
User avatar None

Resource updated
The “po/te/master/pages/historical/board_stable_updates_vision.po” file was changed. a year ago
User avatar None

String updated in the repository
xref:fesco::Updates_Policy.adoc[Updates Policy]
 
a year ago
User avatar None

String updated in the repository
Stable releases, pre-release branches, and Rawhide have a graduated approach to what types of updates are expected. For example, a pre-release branch should accept some updates which a stable release would not, and rawhide would accept updates that are not appropriate for either a stable release or a pre-release.
 
a year ago
User avatar None

String updated in the repository
More skilled and/or intrepid users are encouraged to use xref:releases:rawhide.adoc[_Rawhide_] along with participating in testing of stable branches during the development and pre-release period.
 
a year ago
User avatar None

String updated in the repository
Another factor to keep in mind is Fedora's rapid development cycle. A six-month development cycle for a release allows Fedora to integrate the latest and greatest releases from upstream projects into the 'rawhide' distribution and have that body of work available to the user base in a relatively short amount of time. Ideally, this rapid paced release cycle allows both developers and users the chance to focus on a coherent, consistent, and well functioning set of software content per release.
 
a year ago
User avatar None

String updated in the repository
Updates offered by our built-in tools under the auspices of the Fedora Project are seen as authoritative by users. While a user fitting these criteria is likely to file a bug when something goes wrong, the user does not therefore automatically expect new issues to emerge in a stable release as a result of consuming those updates. When such issues do emerge, the user's confidence in the platform is undermined.
 
a year ago
User avatar None

String updated in the repository
A shifting platform and visible behavioral changes will affect the user's productivity because the user must take time away from the desired tasks to discover what has changed, adjust the way they perform supporting tasks, and refocus on their original objectives. Because productivity is postulated as important to this user, this outcome is undesirable. Similarly, dealing with a large number of updates on a regular basis is distracting from the user's desired productivity tasks.
 
a year ago
User avatar None

String updated in the repository
When creating an updates overview, there are some factors that need to be taken into account. The first, and foremost, is keeping in mind https://www.redhat.com/archives/fedora-advisory-board/2009-October/msg00350.html[the broad criteria] the Board set out for the target audience of the entire Fedora distribution, which describe someone who:
 
a year ago
User avatar None

String updated in the repository
By creating this statement, it is the Board's belief that:
 
a year ago
User avatar None

String updated in the repository
For these reasons, the Fedora Board is issuing a stable release update vision statement to help guide the creation and implementation of a Fedora Updates policy. This policy is not meant to govern the introduction of new packages.
 
a year ago
Browse all translation changes