Weekly Regular Documentation Revisions 03.23-03.29 - develop

docs/Project-guidelines-and-policies.md

@@ -56,7 +56,7 @@ What can make any PR more controversial and requiring a higher level maintainer'
 - Mixing contribution types
 - Current level of maintainers not being sure about whether they can judge this PR
 
-### Contribution process
+## Contribution process
 
 To ensure your contribution goes smoothly, please stick to the following process when contributing to the project:
 1. **Check whether there is already an open Pull Request** for whatever you want to contribute. If there is - comment on it and see if you can help with it instead of starting your own first. We hate to discard otherwise valid work just because it's a duplicate.

docs/locale/zh_CN/LC_MESSAGES/Project-guidelines-and-policies.po

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Phobos \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-03-01 12:45+0800\n"
+"POT-Creation-Date: 2026-03-25 00:33+0800\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -58,8 +58,7 @@ msgid ""
 msgstr "这些角色根据拉取请求的复杂性和贡献者的经验进行分配，并非一成不变。此外这里只列出了常用的角色，在必要情况下负责人可为贡献者单独分配权限。"
 
 msgid "Suggested reviewing amount"
-msgstr ""
-"关于审查工作量的建议"
+msgstr "关于审查工作量的建议"
 
 #, python-format
 msgid ""
@@ -70,13 +69,13 @@ msgid ""
 "125%-150% of they submit). Only in this way can we continuously reduce "
 "the number of backlogged PRs."
 msgstr ""
-"维护者审查的代码量应大致与其自身提交的 PR 代码量相当。然而，考虑到目前已有大量 PR 积压，我们建议维护者审查的代码量应超过其提交量（例如，达到其提交量的 125% 至 150%）。唯有如此，我们才能持续减少积压的 PR 数量。"
+"维护者审查的代码量应大致与其自身提交的 PR 代码量相当。然而，考虑到目前已有大量 PR "
+"积压，我们建议维护者审查的代码量应超过其提交量（例如，达到其提交量的 125% 至 150%）。唯有如此，我们才能持续减少积压的 PR 数量。"
 
 msgid ""
 "At present this is not a hard rule, but we hope that each maintainer can "
 "try their best to achieve this."
-msgstr ""
-"目前这并非硬性规定，但我们希望每位维护者都能尽力遵循这一建议。"
+msgstr "目前这并非硬性规定，但我们希望每位维护者都能尽力遵循这一建议。"
 
 msgid "Types of contributions"
 msgstr "贡献类型"
@@ -195,6 +194,85 @@ msgid ""
 "this PR"
 msgstr "当前维护者不确定能否准确评估该拉取请求"
 
+msgid "Contribution process"
+msgstr ""
+"贡献流程"
+
+msgid ""
+"To ensure your contribution goes smoothly, please stick to the following "
+"process when contributing to the project:"
+msgstr ""
+"为了确保您的贡献顺利加入，请在为项目做出贡献时遵循以下流程："
+
+msgid ""
+"**Check whether there is already an open Pull Request** for whatever you "
+"want to contribute. If there is - comment on it and see if you can help "
+"with it instead of starting your own first. We hate to discard otherwise "
+"valid work just because it's a duplicate."
+msgstr ""
+"**检查是否存在** 与您打算贡献的内容相关的 **已打开的拉取请求**。如果存在——请对其发表评论，看看您是否能够提供帮助，而不是直接打开你自己的拉取请求。"
+"我们并不希望 **您的有效工作** 仅仅因为重复而 **被放弃**。"
+
+msgid ""
+"If all is clear - you should **get in touch with maintainers** of level "
+"respective to the complexity of your PR (see [Types of contributions"
+"](#types-of-contributions)) to review/merge your upcoming PR and **talk "
+"with them about key design aspects before you even submit a "
+"contribution**."
+msgstr ""
+"如果确认不会重复，您应当 **与** 和您 PR 复杂程度（见 [贡献类型](#types-of-contributions)）相匹配的 **维护者取得联系**，以便他们审查／合并您即将提交的 PR 以"
+"及 **在您提交贡献前进行关键设计方面的讨论**。"
+
+msgid ""
+"This is *especially* important for bigger and more fundamental "
+"improvements, when you're learning and when you're exploring \"uncharted "
+"territories\". Staying engaged in communication with the maintainers will"
+" help you to avoid unnecessary wasted effort and reworks later on and "
+"make sure that your contribution is aligned with how we do things. Not "
+"only that, but it also allows you to essentially get early reviews on "
+"important things and faster merges (which is especially important in "
+"light of our large amount of PRs) with higher level of confidence."
+msgstr ""
+"对于较大、较根本性的更改，当您还在学习阶段以及当您正在探索“未知领域”时这 *尤其* 重要。"
+"与维护者保持沟通有助于您避免不必要的精力浪费和返工以及确保您的贡献符合我们的工作方式。"
+"不仅如此，这还可以使您在重要事项上尽早得到审查以及以更高的信心尽快得到合并（考虑到我们"
+"已有大量 PR，这点尤为重要）"
+
+msgid ""
+"Currently the Phobos channel on Discord is the best place to brainstorm "
+"things like that, as it's the most accessible place to reach out to "
+"maintainers and discuss your ideas (or if there's nobody around - try "
+"messaging experienced maintainers privately)."
+msgstr ""
+"目前 Discord 上的 Phobos 频道是进行此类讨论的最佳场所，因为这是联系维护者和讨论您想法最便捷的场所"
+"（如果无人回应，可以尝试私信联系经验丰富的维护者）。"
+
+msgid ""
+"GitHub issues, discussions and draft PRs (with not a lot of work done "
+"yet) are also OK to discuss things, but they are not as fast as Discord "
+"and are better used for persistent storage of info, and usually it's "
+"easier to grab someone's attention if you approach them personally in "
+"chat."
+msgstr ""
+"GitHub 的议题、讨论模块以及（尚未完成大量工作的）PR 草稿也同样可以用来讨论，但它们不如 Discord 那样迅捷"
+"并且更适合用于长期存储信息，而且通常在即时聊天中直接与某人沟通更容易引起他们的注意。"
+
+msgid ""
+"It's also a good thing to get opinions of multiple maintainers and not "
+"always consult specific one or a separate part of them. We should try to "
+"stay interconnected with each other, even if initially divided by "
+"language or habitually."
+msgstr ""
+"向多位维护者寻求意见也是一个很好的做法——不要总是咨询特定某一位或者某一部分维护者。"
+"即便起初由于语言或习惯有所隔阂，我们也应当努力保持彼此之间的相互联系。"
+
+msgid ""
+"When we all have a clear idea of the plan you have in mind - all that is "
+"left to do is to finalize the design and implementation in the PR, and "
+"we'll review the minor things left and merge it."
+msgstr ""
+"当我们都对您所想的计划有了清晰的想法后，剩下的就是完成拉取请求中的设计和实现，我们将审查剩余的小问题，然后合并它。"
+
 msgid "Project structure"
 msgstr "项目结构"