todogroup · anajsana · Nov 5, 2024 · Aug 13, 2024 · Aug 13, 2024 · Aug 13, 2024
diff --git a/content/zh-CN/guides/building-leadership.md b/content/zh-CN/guides/building-leadership.md
diff --git a/content/zh-CN/guides/career-development.md b/content/zh-CN/guides/career-development.md
diff --git a/content/zh-CN/guides/create-program.md b/content/zh-CN/guides/create-program.md
diff --git a/content/zh-CN/guides/diversity-inclusion.md b/content/zh-CN/guides/diversity-inclusion.md
diff --git a/content/zh-CN/guides/impact.md b/content/zh-CN/guides/impact.md
diff --git a/content/zh-CN/guides/management-tools.md b/content/zh-CN/guides/management-tools.md
diff --git a/content/zh-CN/guides/marketing-open-source-projects.md b/content/zh-CN/guides/marketing-open-source-projects.md
diff --git a/content/zh-CN/guides/measuring.md b/content/zh-CN/guides/measuring.md
diff --git a/content/zh-CN/guides/organizing-and-managing-open-source-events.md b/content/zh-CN/guides/organizing-and-managing-open-source-events.md
diff --git a/content/zh-CN/guides/os-commercial-ecosystem.md b/content/zh-CN/guides/os-commercial-ecosystem.md
diff --git a/content/zh-CN/guides/ospo-simple-faq.md b/content/zh-CN/guides/ospo-simple-faq.md
@@ -1,25 +1,23 @@
 ---
-title: Open Source Program Office (OSPO) Easy FAQ
+title: 开源项目办公室（OSPO）简单的常见问题解答 
 ---
 
-The OSPO Easy FAQ (Work in Progress) addresses key aspects of establishing and running an Open Source Program Office (OSPO), clarifying fundamental concepts and offering practical insights. 
-This FAQ aims to be a go-to resource for navigating the world of open source and building a framework for compliance, strategy, governance, and community within companies.
+易懂的开源办公室常见问题解答（进展中）解决构建和运行开源项目办公室（Open Source Program Office，OSPO）中的关键方面，澄清基础概念和提供实用见解。本常见问题解答旨在成为帮助您遨游开源世界并为公司合规、战略、治理和社区构建框架的资源指南。
 
-Please note this aims to be a living document that will be regularly updated to reflect the ongoing progress of the OSPO Simple FAQ
 
-## 💚 About OSPO FAQ work and contributors
+请注意，本指南旨在成为一份动态更新的文档，将根据简易版开源项目办公室常见问题解答的持续进展进行定期更新。
 
-![source: ospo easy faq cover](/img/guides/easy-faq-ospo.png)
+## 💚 关于开源项目办公室的常见问题解答工作和贡献者
 
-The OSPO Easy FAQ is still a work in progress. The efforts are being made by members from the Japan OSPO Local Meetup in Japanese, with the support of [OpenChain](https://www.openchainproject.org/) Japan WG 
-and the TODO Group. The original version is being documented in Japanese as part of the bi-weekly OSPO Japan Local Meetups, and the activity is facilitated by Kiyoshi Owada.
+![source: ospo easy faq cover](/static/img/guides/easy-faq-ospo.png)
 
-* To participate in the meetings, people can [join the online community platform](https://community.linuxfoundation.org/events/details/lfhq-ospo-local-meetup-japan-japanese-speaking-presents-9th-japan-ospo-local-meetup-supported-by-todo-group-and-openchain-japan-wg/)
-* Daily conversations happen via [TODO Group's slack channel](https://join.slack.com/t/thetodogroup/shared_invite/zt-169ok18cz-Pi6tpVHTeW9254d1FpkLew) `#chapter-japan` 
+关于开源项目办公室简易的常见问题解答目前仍在进展中。该项目由日本开源项目办公室当地见面会成员使用日语编写，并得到了 [OpenChain](https://www.openchainproject.org/) 日本工作组和 TODO Group 的支持。原始版本以日语的形式在每两周一次的日本开源项目办公室成员的当地见面会上进行记录，此活动由小和田喜代志先生主持。
 
-## 📝 Documentation
 
-* [Download OSPO Easy FAQ in Japanese (Work in Progress)](https://github.com/todogroup/todogroup.org/files/11635143/OSPO_SimpleQA.pdf)
-* [Download OSPO Easy FAQ in English (Work in Progress)](https://github.com/todogroup/todogroup.org/files/11635329/OSPO_SimpleQA_en.pdf)
+* 参加会议，人们可以[加入在线社区平台](https://community.linuxfoundation.org/events/details/lfhq-ospo-local-meetup-japan-japanese-speaking-presents-9th-japan-ospo-local-meetup-supported-by-todo-group-and-openchain-japan-wg/)
+* 通过[TODO Group 的 slack 频道](https://join.slack.com/t/thetodogroup/shared_invite/zt-169ok18cz-Pi6tpVHTeW9254d1FpkLew) 参与日常对话。`#chapter-japan` 
 
+## 📝 文档
 
+* [下载日语的开源项目办公室简易常见问题解答（进展中）](https://github.com/todogroup/todogroup.org/files/11635143/OSPO_SimpleQA.pdf)
+* [下载英语的开源项目办公室简易常见问题解答（进展中）](https://github.com/todogroup/todogroup.org/files/11635143/OSPO_SimpleQA_en.pdf)
diff --git a/content/zh-CN/guides/outbound-oss.md b/content/zh-CN/guides/outbound-oss.md
diff --git a/content/zh-CN/guides/participating.md b/content/zh-CN/guides/participating.md
diff --git a/content/zh-CN/guides/recruiting-developers.md b/content/zh-CN/guides/recruiting-developers.md
diff --git a/content/zh-CN/guides/shutting-down.md b/content/zh-CN/guides/shutting-down.md
diff --git a/content/zh-CN/guides/strategy.md b/content/zh-CN/guides/strategy.md
diff --git a/content/zh-CN/guides/todo-contribution-guidelines.md b/content/zh-CN/guides/todo-contribution-guidelines.md
@@ -1,67 +1,66 @@
 ---
-title: Open Source Program Office Case Study Guidelines
+title: 开源项目办公室案例指南
 ---
 
-The TODO OSPO Case Study initiative features real-world use cases and the impact OSPO Programs and open source are having on an organization.
-OSPO Use Cases build narratives around open source organization’s journey that includes Open Source Program Office highlighted activities, organizational structure,
-best practices, goals, and success stories, showcasing rganizations as leaders in the OSPO and open source management ecosystem.
+TODO OSPO案例计划聚焦于真实世界里的实践案例以及OSPO/开源对具体组织的影响。OSPO案例围绕开源组织的历程构建叙述，其中包括开源项目办公室OSPO的重点活动、组织结构、最佳实践、目标和成功案例，展示这些组织在OSPO和开源管理生态中的领导者地位。
 
-## Requirements
 
-**Who can be featured in an OSPO Case Study?**
+## 案例要求
 
-As a rule, OSPO case studies feature:
+**谁可以成为OSPO案例？**
 
-* Private and public organizations running an OSPO or an open source initiative
-* TODO Members
+原则上，OSPO案例需满足：
 
-All case studies must demonstrate at least one tangible business impact of OSPOs or open source management within the
-organization and/or the open source ecosystem. Examples from published case studies include:
+* 运行一个OSPO或一个开源计划的私营及公共组织
+* TODO成员
 
-* Compliance, legal, and developer education
-* Evangelizing Open Source Culture and Usage
-* Hosting Open Source Projects
-* Growing Open Source Communities
-* Improving leadership and becoming a decision-making partner
-* OSPO or Open Source management Best practices (e.g tooling, documentation, etc)
+所有案例必须展示至少一个开源项目办公室或开源管理在组织和/或开源生态内的有形的业务影响，来自已发布案例的参考包括：
+* 合规遵从、法务，和开发者赋能
+* 传播开源文化及使用
+* 托管开源项目
+* 发展扩大开源社区
+* 提升领导力，成为决策伙伴
+* OSPO或开源管理最佳实践（例如工具、文档等）
 
-## OSPO Case Study Process
-OSPO case studies follow a self-service model with editorial support and guidance provided by TODO Group and the Linux Foundation.
 
-The self-service follows a five-step process:
+## OSPO案例流程
+OSPO案例遵循自助服务模式（TODO Group和Linux基金会提供编辑支持和指导）。
 
-**1. Proposal**
+自助服务遵循五步流程：
 
-Organizations submit a case study proposal via a Github Issue form
+**1.提案**
 
-IMPORTANT: This form is still in work in progress. Meanwhile, interested participants, please open an [issue](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22use+case%22) using the 'use case' tag providing a description.
+组织通过Github Issue表单来提交案例提案
 
-**2. Review**
-* TODO steering committee team reviews proposal within 30 working days
-* If the proposal meets the criteria, the TODO PM sends a case study pack to the contact info provided
-* If the proposal doesn’t meet the criteria, TODO Program Manager will provide feedback and the organization is invited to resubmit.
+重要提示：此表单仍在运作中。同时，有兴趣的参与者，请使用“use case”标签来新建一个[issue](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22use+case%22) 来提供案例的描述及说明。
 
-**3. Creation**
+**2.评审**
+* TODO指导委员会团队在30个工作日内评审提案
+* 如果提案符合标准，TODO项目经理会将一个案例包发送给提案中提供的联系人
+* 如果提案不符合标准，TODO项目经理将提供反馈，并邀请组织重新提交。
 
-Primary contact writes a case study following the required style documented in the case study pack
+**3.撰写**
 
-**4. Editing**
-* TODO Group reviews the case study and makes any necessary edits as suggestions
-* Edits are based on the style guide.
-* Primary contact is welcome to make further edits or additions to the case study
-* Primary contact confirms when the draft is final and manages any approval processes
+主要联系人按照案例包中记录的指定样式来撰写案例
 
-**5. Publishing**
-* TODO and LF prepare the case study for publication
-* Primary Contact will receive a preview link, to view the case study before it goes live.
-* Case Study is published to todogroup.org and OSPO guide
-* Promotion cycle begins
+**4.编辑**
+* TODO Group评审案例，并根据建议进行必要的编辑
+* 编辑以风格指南为基础
+* 欢迎主要联系人对案例进行进一步编辑或添加
+* 主要联系人确认何时是终稿，并管理任何审批流程
 
-**6. Promotion**
-* Case studies are published on todogorup.org. TODO Group and LF market the case studies online, through social media, blog promotion, and the TODO OSPO newsletter.
+**5.发布**
+* TODO和LF基金会准备发布案例
+* 主要联系人将收到一个预览链接，以便在案例上线前查看该案例
+* 案例被发布到todogroup.org和OSPO指南
+* 推广周期开始
 
-## To get started
+**6.推广**
+*案例被发布在todogorup.org上，TODO Group和LF通过社交媒体、博客推广和TODO OSPO newsletter邮件来在线推广案例。
 
-Propose a case study and send it to the team directly by opening a [issue](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22use+case%22) using the use case tag
 
-If you have any questions or feedback about the OSPO Case Study initiative, please send an email to [email protected].
+## 开始行动吧
+
+提议一个案例，并通过使用“use case”标签来新建一个[issue](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22use+case%22) 来将它直接发给TODO团队。
+
+如果您对OSPO案例计划有任何疑问或反馈，请发送电子邮件至[email protected]。
diff --git a/content/zh-CN/guides/todo-guides-contribution-guidelines.md b/content/zh-CN/guides/todo-guides-contribution-guidelines.md
@@ -25,7 +25,7 @@ TODO Github 仓库是一个基于 CC-BY 4.0 许可的开源项目，这意味着
 
 * 创建一个以 `[TODO Guide] Add the Guide title here` 为格式的 Issue，并在其中描述这份指南将如何惠及 OSPO 生态系统和潜在的参与者。此外，请提供所建议指南的初稿（日后可修改）。这个议题的目的是为了寻求 TODO 社区的反馈和吸引新的贡献者。
 
-* 提交一个关联到该议题的 PR：这个 PR 应在 `content/en/guides` 目录中进行编辑，并添加一个新的 .md 文件。举例来说，如果您建议的 TODO 指南是 “how to set up an OSPO”，那么 .md 文件应命名为 “how-to-set-up-an-ospo.md”。
+* 提交一个关联到该议题的 PR：为添加 PR，可以在 todogroup.org `guides` 目录下添加一个新的 .md 文件。举例来说，如果您建议的 TODO 指南是关于 “how to set up an OSPO”，那么 .md 文件应命名为 “how-to-set-up-an-ospo.md”。
 
 > 中文译者按：为了方便沟通与 review，请以英文创建 Issue 和 PR。
 
@@ -39,4 +39,4 @@ TODO 项目经理、指导委员会和 TODO 社区可以对 PR 进行 Review并
 
 **第四步：宣传推广**
 
-新指南将在 TODO SM channels、OSPO 通讯月刊和 OSPOlogy 会议上进行推广。此外，参与撰写本指南的贡献者可以通过发送邮件至 [email protected] 来请求将该指南作为文章发布在 Linux Foundation 的博客上。
+新指南将在 TODO SM channels、OSPO 通讯月刊和 OSPOlogy 会议上进行推广。此外，参与撰写本指南的贡献者可以发送邮件至 [email protected]，请求将该指南作为文章发布在 Linux Foundation 的博客上。
diff --git a/content/zh-CN/guides/whitepaper-guidelines.md b/content/zh-CN/guides/whitepaper-guidelines.md
@@ -1,58 +1,56 @@
 ---
-title: TODO Whitepaper Guidelines
+title: TODO 白皮书指南
 ---
 
-The TODO Whitepapers inform about specific open source topics demanded by the OSPO community, in order to help the community 
-to understand an issue, provide more documentation, or solve a problem.
+TODO 白皮书介绍了 OSPO 社区要求的特定开源主题，以帮助社区了解问题、提供更多文档或解决问题。
 
-# How to contribute
+# 如何贡献
 
-There are many ways you can directly contribute to a TODO whitepapaer:
+您可以通过多种方式直接为 TODO 白皮书做出贡献：
 
-* 1. Feature a new TODO Whitepapaer
-* 2. Contirbute to a WIP TODO Whitepaper
-* 3. Fix editorial inconsistencies or inaccuracies from existing Whitepapaers
-* 4. Translate Whitepapaers into other languages
+* 1. 推出新的 TODO 白皮书
+* 2. 为进行中的 TODO 白皮书做出贡献
+* 3. 修复现有白皮书中的编辑不一致或不准确之处
+* 4. 将白皮书翻译为其他语言
 
-## 1. Feature a new TODO Whitepapaer
+## 1. 推出新的 TODO 白皮书
 
-**Idea submission:** 
+**想法提交：** 
 
-A request is submitted by opening an [issue at TODO governance repo](https://github.com/todogroup/governance/issues) using the tag `whitepapaer`
+[在 TODO governance 仓库新建问题](https://github.com/todogroup/governance/issues) 并使用标签 `whitepapaer` ，以提出你的想法。
 
-**Steering Committee Review:** 
+**指导委员会评审：** 
 
-The TODO Steering Committee reviews the proposal
+TODO 指导委员会评审该提案。
 
-**Community feedback:** 
+**社区反馈：** 
 
-The issue is shared to the TODO Community asking for feedback and interested contributors.
+分享该提案到 TODO 社区，寻求反馈和感兴趣的贡献者。
 
-**Creation proces:**
+**创建流程：**
 
-TODO PM creates a new repo that gather the whitepapaer content. Bi-weekly sync meetigns can be requested to review whitepapaer's evolution.
+TODO PM 创建一个新仓库来收集白皮书内容。可以要求每两周一次的同步会议来回顾白皮书的进展。
 
-**Publication process:**
+**发布流程：**
 
-Once the final version for the whitepaper content is approved, TODO PM sends this to LF team to work on design and starts publication and promotion process through the main TODO and LF communication channels.
+一旦白皮书内容的最终版本获得批准，TODO PM 会将其发送给 LF 团队进行设计，并通过 TODO 和 LF 主要沟通渠道开始发布和推广流程。
 
-## 2. Contirbute to a WIP TODO Whitepaper
+## 2. 为进行中的 TODO 白皮书做出贡献
 
-Bellow is a list of current WIP Whitepapaers and their dedicated repos. Please check the `CONTRIBUTING.md` file on each repo to learn more.
+以下是当前进行中的白皮书作者及其专用软件仓库的列表。请查看每个软件仓库的 `CONTRIBUTING.md` 文件了解更多信息。
 
-* [Outbound OSS Whitepaper](https://github.com/todogroup/outbound-oss)
+* [对外开源白皮书](https://github.com/todogroup/outbound-oss)
 
-# Examples
+# 示例
 
-Bellow is a list of published and WIP TODO Whitepapers:
+以下是已发布和待发布的 TODO 白皮书列表：
 
-**Why Open Source Matters to your Enterprise**
+**为什么开源对企业至关重要**
 
-[This paper](https://www.linuxfoundation.org/tools/todo-group-why-open-source-matters-to-your-enterprise/), published by the European Chapter of the TODO Group, aims to provide a balanced and quick overview of the 
-business pros and cons of using open source software.
+[本论文](https://www.linuxfoundation.org/tools/todo-group-why-open-source-matters-to-your-enterprise/) 由 TODO Group 欧洲分会出版，旨在均衡、快速地概述使用开源软件的商业利弊。
 
-**Outbound OSS**
+**对外开源**
 
-A WIP Whitepaper maintained by the TODO European Chapter which content is being managed in a dedicated TODO Org repo. [This repo](https://github.com/todogroup/outbound-oss) contains documentation and guidance for 
-handling outbound OSS in organzations.
+A WIP Whitepaper maintained by the TODO European Chapter which content is being managed in a dedicated TODO Org repo. [This repo](https://github.com/todogroup/outbound-oss) contains documentation and guidance for handling outbound OSS in organzations.
+由 TODO Group 欧洲分会维护的进行中的白皮书，其内容由专门的 TODO 组织仓库管理。[此仓库](https://github.com/todogroup/outbound-oss)包含在组织中处理对外开源软件的文档和指南。
 
diff --git a/content/zh-CN/search.md b/content/zh-CN/search.md
@@ -1,6 +1,6 @@
 ---
-title: Search
-description: Search this site using Pagefind
+title: 搜索
+description: 使用 Pagefind 搜索本站
 ---
 
-{{< search_form >}}
+{{< search_form >}}
diff --git a/static/img/guides/outbound-oss1-t.png b/static/img/guides/outbound-oss1-t.png
diff --git a/static/img/guides/outbound-oss2-t.png b/static/img/guides/outbound-oss2-t.png
diff --git a/static/img/guides/outbound-oss3-t.png b/static/img/guides/outbound-oss3-t.png
diff --git a/static/img/guides/outbound-oss4-t.png b/static/img/guides/outbound-oss4-t.png