Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary fedora-docs-l10n/package-maintainers CC-BY-SA-3.0 0 0 0 0 0 0 0
master/antora.yml CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/bug_status CC-BY-SA-3.0 100% 0 0 0 0 1 0 0
master/pages/CommonRpmlintIssues CC-BY-SA-3.0 100% 0 0 0 0 1 0 0
master/pages/How_to_Get_Sponsored_into_the_Packager_Group CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/How_to_Sponsor_a_New_Contributor CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/index CC-BY-SA-3.0 100% 0 0 0 0 3 0 0
master/pages/Installing_Packager_Tools CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Joining_the_Package_Maintainers CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/New_Package_Process_for_Existing_Contributors CC-BY-SA-3.0 100% 0 0 0 0 2 0 0
master/pages/New_Package_Process_for_New_Contributors CC-BY-SA-3.0 100% 0 0 0 0 33 0 0
master/pages/Package_Maintenance_Guide CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Package_Orphaning_Process CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Package_Renaming_Process CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Package_Retirement_Process CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Package_Review_Process CC-BY-SA-3.0 100% 0 0 0 0 4 0 0
master/pages/Package_Update_Guide CC-BY-SA-3.0 100% 0 0 0 0 1 0 0
master/pages/Packaging_Tutorial CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Packaging_Tutorial_1_banner CC-BY-SA-3.0 100% 0 0 0 0 18 0 0
master/pages/Packaging_Tutorial_2_GNU_Hello CC-BY-SA-3.0 100% 0 0 0 0 4 0 0
master/pages/Pull_Request_Guide CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Reporting_Issues CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Staying_Close_to_Upstream_Projects CC-BY-SA-3.0 100% 0 0 0 0 1 0 0
master/pages/Upstream_Release_Monitoring CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/Using_the_Koji_Build_System CC-BY-SA-3.0 100% 0 0 0 0 4 0 0
master/pages/Utilities CC-BY-SA-3.0 0 0 0 0 0 0 0
master/partials/attributes CC-BY-SA-3.0 0 0 0 0 0 0 0
master/partials/mailing_lists CC-BY-SA-3.0 0 0 0 0 0 0 0
nav CC-BY-SA-3.0 0 0 0 0 0 0 0

Overview

Project website pagure.io/fedora-docs-l10n/package-maintainers
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,900,209
8 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,319 26,700 191,791
Translated 100% 1,319 100% 26,700 100% 191,791
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 1,319 100% 26,700 100% 191,791
Failing checks 5% 72 5% 1,380 5% 10,468
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 75 changes 0 changes 11 changes 0 changes 59 changes 0 changes 223 changes 0 changes 16 changes 0 changes 135 changes 0 changes 45 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 24 changes 1,457 changes 16 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

26,700
Hosted words
1,319
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “pot/master/pages/Package_Update_Guide.pot” file was changed. 3 weeks ago
User avatar None

String added in the repository
The latter is important if any builds depend on previous ones in the side tag. Use `koji wait-repo --request --build <package-nvr> <side-tag>` to ensure that the respective build is available in the build root for subsequent builds. Including `--request` is important since Koji switched to on-demand repo generation. It asks Koji to re-generate the repo immediately if the build is not currently in it.
The latter is important if any builds depend on previous ones in the side tag. Use `koji wait-repo --request --build <package-nvr> <side-tag>` to ensure that the respective build is available in the build root for subsequent builds. Including `--request` is important since Koji switched to on-demand repo generation. It asks Koji to re-generate the repo immediately if the build is not currently in it.
3 weeks ago
User avatar None

String added in the repository
Only if there are no dependents (the original package to update is a "leaf package"), or none of the dependents require any action, the single-package workflow can be used. In all other cases, the full tree of affected dependencies needs to be updated together. Note that the `fedrq` invocation above is not recursive. In case a dependent needs to be modified, the same impact check needs to be done for that package, and any further affected packages included in the update.
Only if there are no dependents (the original package to update is a "leaf package"), or none of the dependents require any action, the single-package workflow can be used. In all other cases, the full tree of affected dependencies needs to be updated together. Note that the `fedrq` invocation above is not recursive. In case a dependent needs to be modified, the same impact check needs to be done for that package, and any further affected packages included in the update.
3 weeks ago
User avatar None

String added in the repository
Some or all of listed dependents may be affected and require action. The simplest case is where there is no breakage and nothing needs to be done. The second case is an ABI break that can be resolved by simply rebuilding the dependent while using the new dependency version. In more complicated cases, the dependents may need to be updated to compatible versions or (hopefully temporarily) patched to work with the new dependency version.
Some or all of listed dependents may be affected and require action. The simplest case is where there is no breakage and nothing needs to be done. The second case is an ABI break that can be resolved by simply rebuilding the dependent while using the new dependency version. In more complicated cases, the dependents may need to be updated to compatible versions or (hopefully temporarily) patched to work with the new dependency version.
3 weeks ago
User avatar None

String added in the repository
$ fedrq whatrequires-src --branch rawhide --format source --exclude-subpackages python-pydantic
fawltydeps
fedrq
input-remapper
matrix-synapse
psi4
⋮
$ fedrq whatrequires-src --branch rawhide --format source --exclude-subpackages python-pydantic
fawltydeps
fedrq
input-remapper
matrix-synapse
psi4
⋮
3 weeks ago
User avatar None

String added in the repository
First step in determining the possible impact is to list dependencies. This can be done using the `fedrq` tool:
First step in determining the possible impact is to list dependencies. This can be done using the `fedrq` tool:
3 weeks ago
User avatar None

String added in the repository
It is important to include all the needed packages in the update. Even if you initially just intend to update a single package, ABI or API incompatibility may require updating also other packages.
It is important to include all the needed packages in the update. Even if you initially just intend to update a single package, ABI or API incompatibility may require updating also other packages.
3 weeks ago
User avatar None

String added in the repository
Finding dependents
Finding dependents
3 weeks ago
User avatar None

Resource updated
The “pot/master/pages/Utilities.pot” file was changed. 3 weeks ago
User avatar None

Resource updated
The “pot/master/pages/Installing_Packager_Tools.pot” file was changed. 3 weeks ago
Browse all changes for this language