Source strings

73 Strings
100%
Browse Translate
1,562 Words
100%
10,988 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
73 1,562 10,988
All strings Browse Translate Zen
73 1,562 10,988
Read-only strings Browse Translate Zen
1 77 530
Strings with any failing checks Browse Translate Zen
1 77 530
Failing check: Unpluralised Browse Translate Zen

Summary

Project website pagure.io
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/program_management.git
Repository branch master
Last remote commit automatic update of pot/po files 9642392d
♪ I'm a bot, bot, bot ♪ authored 3 weeks ago
Last commit in Weblate Update translation files acbbd23b
Weblate authored 3 weeks ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-program_management/nav/
File mask po/*/master/pages/changes_policy.po
Translation file Download pot/master/pages/changes_policy.pot
Last change Sept. 30, 2025, 10:14 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,003,224
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 73 1,562 10,988
Translated 100% 73 100% 1,562 100% 10,988
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 73 100% 1,562 100% 10,988
Failing checks 1% 1 4% 77 4% 530
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
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 2 changes 0 changes 0 changes 18 changes
NovDecJanFebMarAprMayJunJulAugSepOct

Quick numbers

1,562
Hosted words
73
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “pot/master/pages/changes_policy.pot” file was changed. a month ago
User avatar None

String added in the repository
Do not close tracking bugs when a change is complete. Instead, please comment on your tracking bug that this change is complete. The Change Wrangler (FOA) will auto-close tracking bugs as part of release housekeeping.
Do not close tracking bugs when a change is complete. Instead, please comment on your tracking bug that this change is complete. The Change Wrangler (FOA) will auto-close tracking bugs as part of release housekeeping.
a month ago
User avatar None

String added in the repository
Approved change proposals will have Bugzilla issues created by the Change Wrangler (FOA). The following status fields should be used to reflect the status of the change:
Approved change proposals will have Bugzilla issues created by the Change Wrangler (FOA). The following status fields should be used to reflect the status of the change:
a month ago
User avatar None

String added in the repository
Changes do not have to be accepted by this deadline, but they must have been submitted to the Change Wrangler (FOA) by then.
Changes do not have to be accepted by this deadline, but they must have been submitted to the Change Wrangler (FOA) by then.
a month ago
User avatar None

String added in the repository
FESCo will re-review the status of changes one week before the beta freeze following an Incomplete Changes report from the Change Wrangler (FOA). At this time, FESCo typically decides whether to activate the contingency plan. Any change for which FESCo can't make this decision one week before beta must include a note on its Change wiki page and tracking bug. Changes that cannot be completed will automatically be deferred to the next release and do not require re-submission unless substantial revisions are made.
FESCo will re-review the status of changes one week before the beta freeze following an Incomplete Changes report from the Change Wrangler (FOA). At this time, FESCo typically decides whether to activate the contingency plan. Any change for which FESCo can't make this decision one week before beta must include a note on its Change wiki page and tracking bug. Changes that cannot be completed will automatically be deferred to the next release and do not require re-submission unless substantial revisions are made.
a month ago
User avatar None

String added in the repository
The Change Wrangler (FOA) will create Bugzilla trackers in the _Changes Tracking_ component and issues in the Release Notes repository for approved changes.
The Change Wrangler (FOA) will create Bugzilla trackers in the _Changes Tracking_ component and issues in the Release Notes repository for approved changes.
a month ago
User avatar None

String added in the repository
Occasionally, FESCo assigns the change to one of the FESCo members or a trusted community member within the functional area (a _change shepherd_), who follows the detailed status of the change with FESCo and helps with processes within Fedora. For example, the change shepherd may communicate high-impact aspects of the change, or point out that a buildroot will be necessary. The shepherd follows the status of the change until final release.
Occasionally, FESCo assigns the change to one of the FESCo members or a trusted community member within the functional area (a _change shepherd_), who follows the detailed status of the change with FESCo and helps with processes within Fedora. For example, the change shepherd may communicate high-impact aspects of the change, or point out that a buildroot will be necessary. The shepherd follows the status of the change until final release.
a month ago
User avatar None

String added in the repository
FESCo will then vote to approve or deny a change proposal in accordance with the xref:fesco:ROOT:index.adoc#_ticket_policy[FESCo ticket policy]. Do not implement your proposal until the FESCo vote has ended. When the Change Wrangler (FOA) creates a tracking bug for your issue, that is your indication to proceed.
FESCo will then vote to approve or deny a change proposal in accordance with the xref:fesco:ROOT:index.adoc#_ticket_policy[FESCo ticket policy]. Do not implement your proposal until the FESCo vote has ended. When the Change Wrangler (FOA) creates a tracking bug for your issue, that is your indication to proceed.
a month ago
User avatar None

String added in the repository
Occasionally, more information is needed on some proposals, and FESCo members may use the ticket filed for clarificiation instead of waiting for the meeting.
Occasionally, more information is needed on some proposals, and FESCo members may use the ticket filed for clarificiation instead of waiting for the meeting.
a month ago
User avatar None

String added in the repository
Change owners are subscribed to the FESCo ticket once it has been created by the Program Manager.
Change owners are subscribed to the FESCo ticket once it has been created by the Program Manager.
a month ago
Browse all translation changes