Translate OSPO definition into Chinese#29
Open
cybershang wants to merge 1 commit intotodogroup:mainfrom
Open
Conversation
Create README-zh.md by translating README.md Signed-off-by: Yingjie Shang <dev@yingjie.space>
node
suggested changes
Oct 29, 2024
|
|
||
| # 开源项目办公室 (OSPO) 定义及指南 | ||
|
|
||
| 开源[与现代技术的发展交织在一起](https://openforumeurope.org/open-source-impact-study/)，并作为所有行业和技术领域(如人工智能和机器学习或网络安全)的大多数代码库的基础。 |
Member
There was a problem hiding this comment.
The better option: 开源与现代科技的发展密不可分
PS：去年我们翻译了一个中文版本（仅供参考 https://mp.weixin.qq.com/s/I0EcMQlHyXalPxHuGRO3pg ） ，提交到了术语表的仓库，目前几个仓库的同步和划分有些不清晰，所以导致信息同步不一致。
|
|
||
| 开源办公室 101 是一个模块化课程，包含管理开源办公室所需的一切知识：<https://github.com/todogroup/ospo101> | ||
|
|
||
| ## OSPO Examples |
|
|
||
| * [如何创建一个开源办公室](https://todogroup.org/resources/guides/how-to-create-an-open-source-program-office/) | ||
| * [评估你的开源办公室](https://todogroup.org/resources/guides/measuring-your-open-source-programs-success/) | ||
| * [用来管理你开源办公室的工具`](https://todogroup.org/resources/guides/tools-for-managing-open-source-programs/) |
| * 确保公司能够有效的在商业产品和服务中使用开源软件 | ||
| * 参与开发者社区，鼓励采纳战略性开源项目 | ||
|
|
||
| *每个开源办公室都是根据商业，产品和货物的不同需求而定制的。* |
|
|
||
| ### 商业导向的细分 | ||
|
|
||
| 降低风险，优化工程师实践，带来经济收益。（提示:恐惧、爱情和金钱) |
Member
There was a problem hiding this comment.
提示： -> 助记词 ；
爱情 -> 热爱
PS：这里的 fear, love , money 是为了方便读者记忆这三类动机：害怕风险、工程师热爱开源、财务收益
|
|
||
| > OSPO的发音是[ah -spoh] | ||
|
|
||
| **[是什么]** 开源办公室（OSPO）是一个组织对开源进行运营和计划的中心。其负责指定和实现战略及政策，以指导开源活动。包括制定围绕代码的使用、分发、选择、审计、贡献等关键方面的政策；为参与开源活动中的人们（组织的内部及外部）提供教育和培训。通过鼓励以可持续方式使用开源组件来提高软件开发效率，并在适当情况下将改进回馈开源项目。在需要时，指导研发团队将软件开源；确保工程效率；确保法律合规；并推广和构建社区参与。[内部开源](https://innersourcecommons.org/)是开源的近邻，经常和开源办公室合作或是开源办公室的一部分。 |
Member
There was a problem hiding this comment.
建议优化下句号、逗号、分号的运用，使之更加贴近庄文表达习惯，并方便读者阅读和理解。该部分主要是对定义的内容的介绍，及其基本职责的分类介绍。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Create README-zh.md by translating README.md
I also noticed #22 (comment) suggesting to support i18n on whole glossary repos, and I'll put it on my plan.