Documentation/articles/committers-guide/_index

Translation status

1,102	Strings		32%	Browse Translate
28,898	Words		19%	Browse Translate

Strings status

1,102	All strings — 28,898 words	Browse Translate Zen
359	Translated strings — 5,761 words	Browse Translate Zen
743	Unfinished strings — 23,137 words	Browse Translate Zen
250	Untranslated strings — 9,866 words	Browse Translate Zen
493	Strings marked for edit — 13,271 words	Browse Translate Zen
743	Unfinished strings without suggestions — 23,137 words	Browse Translate Zen
870	Strings with any failing checks — 25,021 words	Browse Translate Zen
127	Translated strings with any failing checks — 1,884 words	Browse Translate Zen
37	Translated strings with dismissed checks — 671 words	Browse Translate Zen
132	Failing check: Unchanged translation — 1,901 words	Browse Translate Zen
743	Failing check: Has been translated — 23,137 words	Browse Translate Zen
1,102	Strings without a label — 28,898 words	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
Glossary Doc Glossary BSD-2-Clause	82%	3	6	41	3	0	0	0

books/handbook/basics/_index BSD-2-Clause		0	0	0	0	0	0	0

articles/fonts/_index BSD-2-Clause		0	0	0	0	0	0	0

articles/linux-emulation/_index BSD-2-Clause		0	0	0	0	0	0	0

books/developers-handbook/_index BSD-2-Clause		0	0	0	0	0	0	0

books/arch-handbook/scsi/_index BSD-2-Clause		0	0	0	0	0	0	0

books/handbook/partiii BSD-2-Clause		0	0	0	0	0	0	0

articles/nanobsd/_index BSD-2-Clause		0	0	0	0	0	0	0

books/_index BSD-2-Clause		0	0	0	0	0	0	0

articles/cups/_index BSD-2-Clause		0	0	0	0	0	0	0

Browse all components

Overview

Project website	docs.freebsd.org/en
Translation license	BSD 2-Clause "Simplified" License
Translation process	Translations can be made directly. Translation suggestions can be made. Only chosen users can contribute. The translation uses bilingual files.
File mask	`documentation/content/*/articles/committers-guide/_index.po`
Translation file	Download `documentation/content/ru/articles/committers-guide/_index.po`
Last change	Aug. 15, 2025, 9:28 p.m.
Last author	Vladlen Popolitov

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		1,102		28,898		183,937
Translated	32%	359	19%	5,761	21%	39,720
Needs editing	44%	493	45%	13,271	45%	84,590
Read-only	0%	0	0%	0	0%	0
Failing checks	78%	870	86%	25,021	85%	157,680
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	22%	250	34%	9,866	32%	59,627

Last 12 months Previous

Activity in last 12 months


Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr	May	Jun	Jul

Quick numbers

28,898

Hosted words

1,102

Hosted strings

32%

Translated

Contributors

and previous 30 days

Trends of last 30 days

+1%

Hosted words

+100%

+1%

Hosted strings

+100%

+32%

Translated

+1%

—

Contributors

+100%

None Committed changes Documentation / articles/committers-guide/_index — Russian	Committed changes yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English The best way is to simply tell Git you always want to sign commits, tags, and pushes. You can do this by setting a few configuration variables: Russian 0 characters edited Current translation Translated Лучший способ — просто указать Git, что вы всегда хотите подписывать коммиты, теги и отправки. Это можно сделать, установив несколько переменных конфигурации: yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English The rationale behind signing pushes can be found in the https://github.com/git/git/commit/a85b377d0419a9dfaca8af2320cc33b051cbed04[commit that introduced the feature]. Russian 0 characters edited Current translation Translated Обоснование подписания отправок можно найти в https://github.com/git/git/commit/a85b377d0419a9dfaca8af2320cc33b051cbed04[коммите, где представлена эта функция]. yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English A more in-depth documentation on signing commits and tags can be found in the https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work[Git Tools - Signing Your Work] chapter of the Git's book. Russian 0 characters edited Current translation Translated Более подробная документация по подписанию коммитов и тегов доступна в главе https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work[Инструменты Git - Подписание вашей работы] книги по Git. yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English Git knows how to sign commits, tags, and pushes. When you sign a Git commit or a tag, you can prove that the code you submitted came from you and wasn't altered while you were transferring it. You also can prove that you submitted the code and not someone else. Russian 0 characters edited Current translation Translated Git умеет подписывать коммиты, теги и отправки (push). Когда вы подписываете Git-коммит или тег, вы можете доказать, что отправленный код действительно принадлежит вам и не был изменён во время передачи. Вы также можете подтвердить, что именно вы отправили код, а не кто-то другой. yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English Signing the commits, tags, and pushes, with GnuPG Russian 0 characters edited Current translation Translated Подписание коммитов, тегов и отправок с помощью GnuPG yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English You would then build/install that version. If it's good you'd type `git bisect good` otherwise `git bisect bad`. If the version doesn't compile, type `git bisect skip`. You will get a similar message to the above after each step. When you are done, report the bad version to the developer (or fix the bug yourself and send a patch). `git bisect reset` will end the process and return you back to where you started (usually tip of `main`). Again, the git-bisect manual (linked above) is a good resource for when things go wrong or for unusual cases. Russian 0 characters edited Current translation Translated Затем вы собираете и устанавливаете эту версию. Если она работает корректно, введите `git bisect good`, в противном случае — `git bisect bad`. Если версия не компилируется, введите `git bisect skip`. После каждого шага вы будете получать сообщение, аналогичное приведённому выше. По завершении сообщите о проблемной версии разработчику (или исправьте ошибку самостоятельно и отправьте патч). Команда `git bisect reset` завершит процесс и вернёт вас туда, откуда вы начали (обычно на вершину ветки `main`). Ещё раз, руководство по git-bisect (ссылка выше) — это хороший ресурс на случай возникновения проблем или нестандартных ситуаций. yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English Set the 'good' version first, then set the bad (though the order doesn't matter). When you set the bad version, it will give you some statistics on the process: Russian 0 characters edited Current translation Translated Установите сначала «хорошую» версию, затем установите «плохую» (хотя порядок не имеет значения). При установке «плохой» версии вы получите некоторую статистику по процессу: yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English shows me moving the working tree to the `main` branch (a816...) and then updating from upstream (to 5ef0...). In this case, bad would be HEAD (or 5ef0bd68b515) and good would be a8163e165c5b. As you can see from the output, HEAD@{1} also often works, but isn't foolproof if you have done other things to your Git tree after updating, but before you discover the need to bisect. Russian 0 characters edited Current translation Translated показывает, как я перемещаю рабочее дерево в ветку `main` (a816...) и затем обновляю его из вышестоящего репозитория (до 5ef0...). В этом случае, bad будет HEAD (или 5ef0bd68b515), а good — a8163e165c5b. Как видно из вывода, HEAD@{1} также часто работает, но не является безошибочным, если вы выполняли другие действия с деревом Git после обновления, но до того, как обнаружили необходимость в бисекции. yesterday
v.popolitov Translation changed Documentation / articles/committers-guide/_index — Russian	English If you want to know the last version you checked out, you should use `git reflog`: Russian 0 characters edited Current translation Translated Если вы хотите узнать последнюю версию, которую вы извлекли, используйте `git reflog`: yesterday

Browse all translation changes

Quick downloads

1,102	File in original format as translated in the repository	gettext PO file
1,102	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX
743	Unfinished strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2025-07-17 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2025-07-17 AND state:<=needs-editing`	Add