guix/documentation-manual — Chinese (Simplified) (zh

Zen

Translation

English type: quotation

Chinese (Simplified) (zh_CN)

Needs editing

Skip

	English	Chinese (Simplified) (zh_CN)	Actions
	A contributor (who may or may not have commit access) wishing to block a proposal bears a special responsibility for finding alternatives, proposing ideas/code or explain the rationale for the status quo to resolve the deadlock. To learn what consensus decision making means and understand its finer details, you are encouraged to read @url{https://www.seedsforchange.org.uk/consensus}.	希望阻止提案的贡献者（可能拥有或不拥有提交权限）承担着寻找替代方案、提出想法/代码或解释现状以解决僵局的特殊责任。要了解共识决策的含义并理解其细微细节，建议您阅读 @url{https://www.seedsforchange.org.uk/consensus}。
	commit access, for developers	提交权限，针对开发者
	Everyone can contribute to Guix without having commit access (@pxref{Submitting Patches}). However, for frequent contributors, having write access to the repository can be convenient. As a rule of thumb, a contributor should have accumulated fifty (50) reviewed commits to be considered as a committer and have sustained their activity in the project for at least 6 months. This ensures enough interactions with the contributor, which is essential for mentoring and assessing whether they are ready to become a committer. Commit access should not be thought of as a ``badge of honor'' but rather as a responsibility a contributor is willing to take to help the project.	每个人都可以在没有提交权限的情况下为 Guix 做出贡献（@pxref{提交补丁}）。然而，对于频繁的贡献者来说，拥有对代码库的写入权限可能会很方便。作为经验法则，贡献者应积累五十（50）个经过审查的提交，以被视为提交者，并在项目中持续活动至少 6 个月。这确保了与贡献者之间有足够的互动，这对于指导和评估他们是否准备好成为提交者至关重要。提交权限不应被视为“荣誉徽章”，而应被视为贡献者愿意承担的责任，以帮助项目。
	Committers are in a position where they enact technical decisions. Such decisions must be made by @emph{actively building consensus} among interested parties and stakeholders. @xref{Making Decisions}, for more on that.	提交者处于执行技术决策的位置。这些决策必须通过 @emph{积极建立共识} 在相关方和利益相关者之间做出。有关更多信息，请参见 @xref{做出决策}。
	The following sections explain how to get commit access, how to be ready to push commits, and the policies and community expectations for commits pushed upstream.	以下部分解释了如何获得提交权限、如何准备推送提交，以及推送到上游的提交的政策和社区期望。
	Applying for Commit Access	提交权利
	When you deem it necessary, consider applying for commit access by following these steps:	当您认为有必要时，请考虑按照以下步骤申请提交权限：
	Find three committers who would vouch for you. You can view the list of committers at @url{https://savannah.gnu.org/project/memberlist.php?group=guix}. Each of them should email a statement to @email{guix-maintainers@@gnu.org} (a private alias for the collective of maintainers), signed with their OpenPGP key.	找到三位愿意为您担保的提交者。您可以在 @url{https://savannah.gnu.org/project/memberlist.php?group=guix} 查看提交者列表。他们每个人都应向 @email{guix-maintainers@@gnu.org}（维护者集体的私人别名）发送一份声明，并用他们的 OpenPGP 密钥签名。
	Committers are expected to have had some interactions with you as a contributor and to be able to judge whether you are sufficiently familiar with the project's practices. It is @emph{not} a judgment on the value of your work, so a refusal should rather be interpreted as ``let's try again later''.	提交者应与您作为贡献者有过一些互动，并能够判断您是否对项目的实践足够熟悉。这并不是对您工作的价值的评判，因此拒绝应被理解为“让我们稍后再试”。
	Send @email{guix-maintainers@@gnu.org} a message stating your intent, listing the three committers who support your application, signed with the OpenPGP key you will use to sign commits, and giving its fingerprint (see below). See @uref{https://emailselfdefense.fsf.org/en/}, for an introduction to public-key cryptography with GnuPG.	向 @email{guix-maintainers@@gnu.org} 发送一条消息，说明您的意图，列出支持您申请的三位提交者，并使用您将用于签署提交的 OpenPGP 密钥进行签名，并提供其指纹（见下文）。有关 GnuPG 公钥密码学的介绍，请参见 @uref{https://emailselfdefense.fsf.org/en/}。
	Set up GnuPG such that it never uses the SHA1 hash algorithm for digital signatures, which is known to be unsafe since 2019, for instance by adding the following line to @file{~/.gnupg/gpg.conf} (@pxref{GPG Esoteric Options,,, gnupg, The GNU Privacy Guard Manual}):	设置 GnuPG，使其永远不使用 SHA1 哈希算法进行数字签名，因为自 2019 年以来已知不安全，例如通过将以下行添加到 @file{~/.gnupg/gpg.conf} 中（@pxref{GPG Esoteric Options,,, gnupg, The GNU Privacy Guard Manual}）：
	digest-algo sha512	digest-algo sha512
	Maintainers ultimately decide whether to grant you commit access, usually following your referrals' recommendation.	维护者最终决定是否授予您提交访问权限，通常会遵循您推荐的建议。
	OpenPGP, signed commits	OpenPGP，签名提交
	If and once you've been given access, please send a message to @email{guix-devel@@gnu.org} to say so, again signed with the OpenPGP key you will use to sign commits (do that before pushing your first commit). That way, everyone can notice and ensure you control that OpenPGP key.	如果您获得了访问权限，请向 @email{guix-devel@@gnu.org} 发送一条消息以说明这一点，再次使用您将用于签署提交的 OpenPGP 密钥进行签名（在推送您的第一次提交之前这样做）。这样，大家都可以注意到并确保您控制该 OpenPGP 密钥。
	Important	重要
	Before you can push for the first time, maintainers must:	在您第一次推送之前，维护者必须：
	add your OpenPGP key to the @code{keyring} branch;	将您的 OpenPGP 密钥添加到 @code{keyring} 分支；
	add your OpenPGP fingerprint to the @file{.guix-authorizations} file of the branch(es) you will commit to.	将您的 OpenPGP 指纹添加到您将提交的分支的 @file{.guix-authorizations} 文件中。
	Make sure to read the rest of this section and... profit!	确保阅读本节的其余部分并... 获利！
	Maintainers are happy to give commit access to people who have been contributing for some time and have a track record---don't be shy and don't underestimate your work!	维护者乐于向那些已经贡献了一段时间并有良好记录的人授予提交访问权限——不要害羞，也不要低估您的工作！
	However, note that the project is working towards a more automated patch review and merging system, which, as a consequence, may lead us to have fewer people with commit access to the main repository. Stay tuned!	但是，请注意，该项目正在朝着更自动化的补丁审查和合并系统努力，因此可能导致我们拥有更少的人拥有主存储库的提交访问权限。请保持关注！
	All commits that are pushed to the central repository on Savannah must be signed with an OpenPGP key, and the public key should be uploaded to your user account on Savannah and to public key servers, such as @code{keys.openpgp.org}. To configure Git to automatically sign commits, run:	所有推送到 Savannah 中央存储库的提交必须使用 OpenPGP 密钥签名，并且公钥应上传到您在 Savannah 的用户帐户和公共密钥服务器，例如 @code{keys.openpgp.org}。要配置 Git 自动签署提交，请运行：
	git config commit.gpgsign true	git config commit.gpgsign true
	# Substitute the fingerprint of your public PGP key. git config user.signingkey CABBA6EA1DC0FF33	# 替换为您的公共 PGP 密钥的指纹。 git config user.signingkey CABBA6EA1DC0FF33
	To check that commits are signed with correct key, use:	要检查提交是否使用正确的密钥签名，请使用：
	@xref{Building from Git} for running the first authentication of a Guix checkout.	@xref{Building from Git} 以运行 Guix 检出的第一次身份验证。
	To avoid accidentally pushing unsigned or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.	为了避免意外将未签名或使用错误密钥签名的提交推送到 Savannah，请确保根据 @xref{Configuring Git} 配置 Git。
	Commit Policy	提交权利
	If you get commit access, please make sure to follow the policy below (discussions of the policy can take place on @email{guix-devel@@gnu.org}).	如果您获得提交访问权限，请确保遵循以下政策（政策讨论可以在 @email{guix-devel@@gnu.org} 上进行）。
	Ensure you're aware of how the changes should be handled (@pxref{Managing Patches and Branches}) prior to being pushed to the repository, especially for the @code{master} branch.	在推送到仓库之前，请确保您了解如何处理更改 (@pxref{Managing Patches and Branches})，尤其是对于 @code{master} 分支。

Loading…

mt:weblate-translation-memory

Suggestion added

English

Chinese (Simplified) (zh_CN) 0 characters edited Current translation

a month ago

pelzflorian

Translation uploaded

English

Chinese (Simplified) (zh_CN) 0 characters edited Current translation Needs editing

a month ago

clsty

Translation uploaded

English

Chinese (Simplified) (zh_CN) 2 characters edited Current translation Translated

2 months ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Has been translated

This string has been translated in the past

Reset

Glossary

English	Chinese (Simplified) (zh_CN)
No related strings found in the glossary.

6536627 String information

Source string description

type: quotation

Flags

ignore-same, no-wrap

Source string location

guix-git/doc/contributing.texi:2827 • guix-git/doc/guix.texi:722 • guix-git/doc/guix.texi:754 • guix-git/doc/guix.texi:22728 • guix-git/doc/guix.texi:36678 • guix-git/doc/guix.texi:37713

String age

4 years ago

Last updated

4 days ago

Source string age

4 years ago

Translation file

po/doc/guix-manual.zh_CN.po, string 755

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.