Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the translation of Maturity model #20

Merged
merged 5 commits into from
Dec 28, 2022
Merged

Conversation

WillemJiang
Copy link
Owner


InnerSource projects thrive when contributors become active and participate. As a result, making contribution easier should be balanced with pure technical goals.
贡献者主动参与到内源项目可以让项目获得更好的发展。因此,需要让贡献和追求完美的技术目标之间达到平衡。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

需要在使贡献更容易和追求完美的技术目标之间达到平衡。

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。

* DP-1: Development teams use shared code repositories, internally. Some teams develop their own CI process, using non corporate or standard CI tools. There is no code review process defined, although some projects teams do it internally.
* DP-2: The organization sponsors and promotes a shared repository for collective knowledge. Some teams develop their own CI process, using corporate CI tools. There are CI environments. Code review process defined, and used by some projects. Sometimes code review is done by outside team members.
* DP-3: Most teams develop their own CI process, using corporate CI tools. There are CI environments. Code review process defined, and used. Code review is done by both, internal and external team members.
* DP-0: 互相区隔的开发团队。各团队有自己的开发流程和工具。没有和其他团队共享知识和工件。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

工件 改为 作品

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。

* DP-2: The organization sponsors and promotes a shared repository for collective knowledge. Some teams develop their own CI process, using corporate CI tools. There are CI environments. Code review process defined, and used by some projects. Sometimes code review is done by outside team members.
* DP-3: Most teams develop their own CI process, using corporate CI tools. There are CI environments. Code review process defined, and used. Code review is done by both, internal and external team members.
* DP-0: 互相区隔的开发团队。各团队有自己的开发流程和工具。没有和其他团队共享知识和工件。
* DP-1: 公司内开发团队之间共享代码库。部分团队有自己的CI工具,没有使用公司统一的CI工具。部分团队内部有自己的代码评审流程。但是公司没有统一的代码评审流程。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

部分团队有自己的CI流程,没有使用公司统一或标准的CI工具。

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。

* DP-3: Most teams develop their own CI process, using corporate CI tools. There are CI environments. Code review process defined, and used. Code review is done by both, internal and external team members.
* DP-0: 互相区隔的开发团队。各团队有自己的开发流程和工具。没有和其他团队共享知识和工件。
* DP-1: 公司内开发团队之间共享代码库。部分团队有自己的CI工具,没有使用公司统一的CI工具。部分团队内部有自己的代码评审流程。但是公司没有统一的代码评审流程。
* DP-2: 建设公司级的知识共享库。部分团队使用公司CI工具来使能自己的CI流程。公司存在统一的CI环境和代码检视流程。部分项目已经应用。代码审查会邀请外部团队成员协助完成。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

使能 改为 开发

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。


When working in host teams mistakes will automatically be widely visible. In order keep contribution levels up, corporate culture needs to celebrate failure as an opportunity for growth and learning.
团队成员内部可以深入学习和了解曾经遇到的问题和解决的方法。为了让团队外部人员了解到曾经遇到的问题,需要建设跨团队共享经验的文化,在企业内鼓励共享成功或失败的经验,促进其他团队的成长。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

当在东道主团队中工作时,错误会自动被广泛看见。为了保持贡献水平,企业文化需要庆祝失败,作为大家共同成长和学习的机会。

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。


For silos to be reduced colleagues need to be comfortable sharing feedback openly. One easy way to support that is to use the same communication principles across hierarchies.
为了减少工作间壁垒(silos),同事们需要坦诚地分享反馈意见。一个简单的支持方式是跨层级使用相同的通信原则。
理想情况下,您最终会建立起适当的沟通渠道,这被整个组织中被广泛使用。这些渠道将聚焦于不同的目标(公告、用户支持、开发渠道、非正式讨论、等)。你将逐渐形成一套最佳实践,例如采用网络礼仪准则,为每一个新的内源项目开辟一套成熟的标准化沟通渠道(即时存档的、可公开访问的、可搜索的)。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“这被整个组织中被广泛使用。”改为 “并被整个组织广泛使用。”
“(即时存档的、可公开访问的、可搜索的)。“ 改 为” (消息即时存档、可公开访问、可搜索的渠道)。”

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(消息即时存档、可公开访问、可搜索的渠道) 改为 (消息即时存档、可公开访问、提供搜索功能)

InnerSource projects encourage employees to contribute to projects outside of the direct influence of their direct line manager. This needs a culture of trust.
* LS-0:在一个高度层级化的组织中,大家奉行的是指挥与控制文化。
* LS-1:一些领导人愿意接受反馈,并创造一个让人们感到能够安全反馈的环境。
* LS-2:一些领导人愿意接受反馈,并创造一个让人们感到能够安全反馈的环境。领导者在理解所有成员是否都感到有权力和能够分享时表现出消极的态度。组织鼓励领导者积极寻找对话中没有出现的声音,以求包容。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“一些” 改 “多数“

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。

* RW-0:没有奖励。
* RW-1:内源项目的管理者鼓励协作,想要奖励那些对项目作出卓越贡献的个人或组织,但是没有制定政策和流程来作为支撑。
* RW-2 制定了标准的流程和制度来鼓励内源项目开发团队之外的组织和个人参与协作,并进行奖励,奖励谁是由项目管理者或者项目管理委员会来决定的。
* RW-3:奖励不仅由组织提出,社区也会提出他们认为的更有价值的奖励。内源社区有责任决定谁应该得到奖励。内源社区应该声明鼓励协作,并在社区层面给予认可。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“”内源社区应该声明鼓励协作,并在社区层面给予认可。“这一句英文原文没有。

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已删除。

* SM-0: 由核心开发或支持团队给予支持和维护,通过商业合同来保证产品的支持和维护。团队之外对产品一无所知。
* SM-1: 有由专门的支持团队提供的规则和制度,来使对产品的支持和维护正式确立。
* SM-2: 通过内源模式来使内源贡献的支持得以正式确立,如:[30天保修](./30-day-warranty.md)或[服务与库](./service-vs-library.md)。
* SM-3: 有由成熟社区提供的规则和制度,来使对产品的支持和维护正确立。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

有成熟社区的规则和制度正式支持产品。

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。

InnerSource comes with explicit roles. While in early stages some patterns may be useable without adopting those roles, communicating within projects using explicit role titles becomes easier.
* RO-0: 没有具体角色帮助内源夯实。只有常见的开发角色:开发人员、分析师、测试人员等。
* RO-1: 偶尔有个人和团队参与其他项目。这些是技术贡献,即用户/贡献者角色。对于某些团队,可以指定至少一个成员作为技术指导,该成员向其他开发团队成员解释开发过程。他/她可以作为受信任的提交者(trusted committer)角色的候选人。
* RO-2: 内源管理者角色负责治理和支持,包括流程等。识别教育需求,并确保向组织提供教育需求。内源领导和教练负责组织参与内源项目。第一个正式步骤是:定义内源愿景和路标。组织定义了受信任的提交者(trusted committer)角色,不仅为开发团队成员,而且为外部贡献者提供联系/参考。有一个标准的流程描述如何为社区做出贡献,贡献者角色是存在的。数据安全员角色负责管理内源活动留下的操作日志,这是需要衡量内源演变所必需的。受信任的提交者(trusted committer)角色将演变为更具技术性的形象,社区管理员将负责“激励”社区,他的主要职责是吸引和留住新的开发者/用户(贡献者/社区成员)。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

识别教育需求,并确保向组织提供所需的教育和培训。

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已采纳。

@WillemJiang WillemJiang merged commit 0e33453 into translation-cn Dec 28, 2022
@WillemJiang WillemJiang deleted the maturity-model branch December 28, 2022 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants