diff --git a/config/urls.yaml b/config/urls.yaml index 45a7ff28..5e65cb90 100644 --- a/config/urls.yaml +++ b/config/urls.yaml @@ -8,9 +8,7 @@ # URLs of video locations. video: # URL on the innersourcecommons.org site. - isc: https://innersourcecommons.org/resources/learningpath/introduction/index - # URL on the innersourcecommons.net site. - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/01 + isc: https://innersourcecommons.org/learn/learning-path/introduction/01 # URL on the O'Reilly learning plarform. oreilly: https://learning.oreilly.com/videos/introduction-to-innersource/9781492041504/9781492041504-video321606 # URL on YouTube. @@ -21,308 +19,256 @@ # URL in GitHub. github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/introduction/01-introduction.asciidoc # URL on the innersourcecommons.org site. - isc: https://innersourcecommons.org/resources/learningpath/introduction/index - # URL on the innersourcecommons.net site. - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/01 + isc: https://innersourcecommons.org/learn/learning-path/introduction/01 # URL on the O'Reilly learning plarform. oreilly: '' - section: introduction video: - isc: https://innersourcecommons.org/resources/learningpath/introduction/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/02/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/02/ oreilly: https://learning.oreilly.com/videos/introduction-to-innersource/9781492041504/9781492041504-video321607 youtube: https://www.youtube.com/watch?v=v9fL-E3ZVdc article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/introduction/02-problems-solved.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/introduction/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/02/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/02/ oreilly: '' - section: introduction video: - isc: https://innersourcecommons.org/resources/learningpath/introduction/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/03/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/03/ oreilly: https://learning.oreilly.com/videos/introduction-to-innersource/9781492041504/9781492041504-video321608 youtube: https://www.youtube.com/watch?v=jPPwnaEBd8U article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/introduction/03-how-works.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/introduction/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/03/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/03/ oreilly: '' - section: introduction video: - isc: https://innersourcecommons.org/resources/learningpath/introduction/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/04/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/04/ oreilly: https://learning.oreilly.com/videos/introduction-to-innersource/9781492041504/9781492041504-video321609 youtube: https://www.youtube.com/watch?v=PFLmOWCEpi4 article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/introduction/04-benefits.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/introduction/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/04/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/04/ oreilly: '' - section: introduction video: - isc: https://innersourcecommons.org/resources/learningpath/introduction/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/05/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/05/ oreilly: https://learning.oreilly.com/videos/introduction-to-innersource/9781492041504/9781492041504-video321610 youtube: https://www.youtube.com/watch?v=rLiDsM3w5YM article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/introduction/05-principles.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/introduction/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/05/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/05/ oreilly: '' - section: introduction video: - isc: https://innersourcecommons.org/resources/learningpath/introduction/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/06/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/06/ oreilly: https://learning.oreilly.com/videos/introduction-to-innersource/9781492041504/9781492041504-video321611 youtube: https://www.youtube.com/watch?v=cFmg-c9IunM article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/introduction/06-conclusion.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/introduction/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/introduction/06/ + isc: https://innersourcecommons.org/learn/learning-path/introduction/06/ oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/index - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/01 + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/01 oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323925 youtube: https://www.youtube.com/watch?v=2FdD9Gup6Yc article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/01-introduction.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/index - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/01 + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/01 oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/02/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/02/ oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323926 youtube: https://www.youtube.com/watch?v=QQ1z9DHlbhg article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/02-ensuring-product-quality.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/02/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/02/ oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/03/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/03/ oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323927 youtube: https://www.youtube.com/watch?v=aLGtTTzkQec article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/03-keeping-the-community-healthy.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/03/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/03/ oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/04/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/04/ oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323928 youtube: https://www.youtube.com/watch?v=452IVT7TKsE article: anchor: pass:[#upleveling] github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/04-uplevelling-community-members.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/04/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/04/ oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/05/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/05/ oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323929 youtube: https://www.youtube.com/watch?v=0Ztb6k5Y17o article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/05-lowering-the-barriers-to-entry.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/05/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/05/ oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/06/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/06/ oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323930 youtube: https://www.youtube.com/watch?v=sqE-Uif_giA article: anchor: pass:[#advocating] github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/06-advocating-for-the-communitys-needs.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/06/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/06/ oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/07/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/07/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/07/ oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323931 youtube: https://www.youtube.com/watch?v=nZp8jlr9l-k article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/07-becoming-a-trusted-committer.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/07/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/07/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/07/ oreilly: '' - section: trusted committer video: - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/08/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/08/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/08/ oreilly: https://learning.oreilly.com/videos/the-trusted-committer/9781492047599/9781492047599-video323932 youtube: https://www.youtube.com/watch?v=qlVpZn_2KMs article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-committer/08-conclusion.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/trusted-committer/08/ - isc.net: https://innersourcecommons.net/learn/learning-path/trusted-committer/08/ + isc: https://innersourcecommons.org/learn/learning-path/trusted-committer/08/ oreilly: '' - section: product owner video: - isc: https://innersourcecommons.org/resources/learningpath/product-owner/index - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/01 + isc: https://innersourcecommons.org/learn/learning-path/product-owner/01 oreilly: https://learning.oreilly.com/videos/innersource-product-owners/9781492046707/9781492046707-video325229 youtube: https://www.youtube.com/watch?v=urbkSMsJXZ0 article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/product-owner/01-opening-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/product-owner/index - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/01 + isc: https://innersourcecommons.org/learn/learning-path/product-owner/01 oreilly: '' - section: product owner video: - isc: https://innersourcecommons.org/resources/learningpath/product-owner/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/02/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/02/ oreilly: https://learning.oreilly.com/videos/innersource-product-owners/9781492046707/9781492046707-video325230 youtube: https://www.youtube.com/watch?v=PQwlatm5Kak article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/product-owner/02-how-difficult-it-is-to-be-a-middle-manager-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/product-owner/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/02/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/02/ oreilly: '' - section: product owner video: - isc: https://innersourcecommons.org/resources/learningpath/product-owner/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/03/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/03/ oreilly: https://learning.oreilly.com/videos/innersource-product-owners/9781492046707/9781492046707-video325231 youtube: https://www.youtube.com/watch?v=UGX7khGbtx0 article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/product-owner/03-major-benefits-are-built-into-the-innersource-process-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/product-owner/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/03/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/03/ oreilly: '' - section: product owner video: - isc: https://innersourcecommons.org/resources/learningpath/product-owner/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/04/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/04/ oreilly: https://learning.oreilly.com/videos/innersource-product-owners/9781492046707/9781492046707-video325232 youtube: https://www.youtube.com/watch?v=afXNJjt2ReI article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/product-owner/04-new-roles-and-responsibilities-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/product-owner/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/04/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/04/ oreilly: '' - section: product owner video: - isc: https://innersourcecommons.org/resources/learningpath/product-owner/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/05/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/05/ oreilly: https://learning.oreilly.com/videos/innersource-product-owners/9781492046707/9781492046707-video325233 youtube: https://www.youtube.com/watch?v=LO5ouFdgyBY article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/product-owner/05-recap-takeaways-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/product-owner/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/05/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/05/ oreilly: '' - section: product owner video: - isc: https://innersourcecommons.org/resources/learningpath/product-owner/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/06/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/06/ oreilly: https://learning.oreilly.com/videos/innersource-product-owners/9781492046707/9781492046707-video325234 youtube: https://www.youtube.com/watch?v=0beNc9V-tro article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/product-owner/06-closing-and-contact-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/product-owner/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/product-owner/06/ + isc: https://innersourcecommons.org/learn/learning-path/product-owner/06/ oreilly: '' - section: contributor video: - isc: https://innersourcecommons.org/resources/learningpath/contributor/index - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/01 + isc: https://innersourcecommons.org/learn/learning-path/contributor/01 oreilly: https://learning.oreilly.com/learning-paths/learning-path-the/0636920338833/0636920338802-video329499 youtube: https://www.youtube.com/watch?v=ncPO1fz5fRg article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/contributor/index - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/01 + isc: https://innersourcecommons.org/learn/learning-path/contributor/01 oreilly: '' - section: contributor video: - isc: https://innersourcecommons.org/resources/learningpath/contributor/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/02/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/02/ oreilly: https://learning.oreilly.com/learning-paths/learning-path-the/0636920338833/0636920338802-video329500 youtube: https://www.youtube.com/watch?v=v3aRZkbTSmY article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/02-becoming-a-contributor-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/contributor/02/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/02/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/02/ oreilly: '' - section: contributor video: - isc: https://innersourcecommons.org/resources/learningpath/contributor/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/03/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/03/ oreilly: https://learning.oreilly.com/learning-paths/learning-path-the/0636920338833/0636920338802-video329501 youtube: https://www.youtube.com/watch?v=iQu-l3j2kCg article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/03-contributor-ethos-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/contributor/03/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/03/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/03/ oreilly: '' - section: contributor video: - isc: https://innersourcecommons.org/resources/learningpath/contributor/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/04/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/04/ oreilly: https://learning.oreilly.com/learning-paths/learning-path-the/0636920338833/0636920338802-video329502 youtube: https://www.youtube.com/watch?v=wv3uylJC4K0 article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/04-mechanics-of-contributing-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/contributor/04/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/04/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/04/ oreilly: '' - section: contributor video: - isc: https://innersourcecommons.org/resources/learningpath/contributor/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/05/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/05/ oreilly: https://learning.oreilly.com/learning-paths/learning-path-the/0636920338833/0636920338802-video329503 youtube: https://www.youtube.com/watch?v=HMBW0B1XPi0 article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/05-benefits-of-contribution-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/contributor/05/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/05/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/05/ oreilly: '' - section: contributor video: - isc: https://innersourcecommons.org/resources/learningpath/contributor/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/06/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/06/ oreilly: https://learning.oreilly.com/learning-paths/learning-path-the/0636920338833/0636920338802-video329504 youtube: https://www.youtube.com/watch?v=5SztKQyeUiM article: anchor: '' github: https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/06-conclusion-article.asciidoc - isc: https://innersourcecommons.org/resources/learningpath/contributor/06/ - isc.net: https://innersourcecommons.net/learn/learning-path/contributor/06/ + isc: https://innersourcecommons.org/learn/learning-path/contributor/06/ oreilly: '' diff --git a/contributor/01-introduction-article.asciidoc b/contributor/01-introduction-article.asciidoc index 21faa52f..f46baff2 100644 --- a/contributor/01-introduction-article.asciidoc +++ b/contributor/01-introduction-article.asciidoc @@ -12,15 +12,15 @@ If you're not getting what you need, you can make the change you need directly i The Contributor role describes a person that makes contributions to the repos of an InnerSource community project. This person may or may not be part or see themselves as part of the community. However, for quite a few people there is a sort of journey that contributors can make from just knowing about the community to using the community's product to interacting with members of the community and finally starting to contribute. -Finally, some of them may become https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Trusted Committers]. +Finally, some of them may become https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Trusted Committers]. === Relationship to other roles -As a Contributor in an InnerSource community you will interact with people playing other roles of InnerSource, such as https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] or https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] and possibly with other contributors. +As a Contributor in an InnerSource community you will interact with people playing other roles of InnerSource, such as https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] or https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] and possibly with other contributors. At times, these roles can be played by the same person, such as Trusted Committer and Product Owner in small grassroots style projects. -This section gives you a very short overview of the other two roles, but we'd like to encourage you to read the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[introductory article of the Trusted Committer role], and we recommended you read the https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[Lowering the barriers to entry] article, too, before you delve deeper into the details of the Contributor role in this section. -You can also watch the videos (https://innersourcecommons.org/resources/learningpath/trusted-committer/index[introduction], https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[lowering the barriers to entry]) instead of reading the articles. +This section gives you a very short overview of the other two roles, but we'd like to encourage you to read the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[introductory article of the Trusted Committer role], and we recommended you read the https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[Lowering the barriers to entry] article, too, before you delve deeper into the details of the Contributor role in this section. +You can also watch the videos (https://innersourcecommons.org/learn/learning-path/trusted-committer/01[introduction], https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[lowering the barriers to entry]) instead of reading the articles. ==== Trusted Committer @@ -33,7 +33,7 @@ Caring for the community involves keeping it healthy, upleveling it and its part ==== Product Owner -The role of the https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] has some similarity with the product owner role of your average project. +The role of the https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] has some similarity with the product owner role of your average project. However, there are differences - depending on the size of the project, this role is often filled by the same person that acts as trusted committer. In larger projects, or in teams that only partially use InnerSource as an approach to fill their needs by accepting contributions, this role is likely filled by a person separate from a trusted committer. @@ -42,7 +42,7 @@ You might work with the product owner role to make sure that general aspects of Last but not least, someone acting as product owner might have been involved in bringing the project, its benefits and community to your attention. -If you want to learn in more detail what these other roles are about, and we encourage you to do so, we've prepared separate sections about the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] and the https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_]. +If you want to learn in more detail what these other roles are about, and we encourage you to do so, we've prepared separate sections about the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] and the https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_]. === Section overview diff --git a/contributor/04-mechanics-of-contributing-article.asciidoc b/contributor/04-mechanics-of-contributing-article.asciidoc index 5fe49a3b..28640b7b 100644 --- a/contributor/04-mechanics-of-contributing-article.asciidoc +++ b/contributor/04-mechanics-of-contributing-article.asciidoc @@ -36,7 +36,7 @@ This effect can be observed with Open Source as well, you can read more about it In your classic teams everyone had an idea of the expected lead times. Within an InnerSource context this might not be the case, either due to large time-zone differences (e.g. Seattle, USA with PDT vs Berlin, Germany with CEST) or you not being available full-time as with your original team, even if they are in the same physical location as you are. Thus, to prevent frustration on both sides, impatience and other non-trust-building effects, you'll need to explicitly do expectations management with regards to your expected reaction times. -One approach is to just quickly react with a "I'll look into it, I won't get to it in the next few days though" to a https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer's_] feedback if you know that you'll only be able to come back to them in a few days. +One approach is to just quickly react with a "I'll look into it, I won't get to it in the next few days though" to a https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer's_] feedback if you know that you'll only be able to come back to them in a few days. Ideally, you can provide them with a rough estimate when you will likely have time to take a look at their input. Doing so builds trust by reliability even over non-physical contact, longer distance or otherwise asynchronous media. Established trust will allow you to overcome uncertainty bumps in the collaborative road ahead of you. @@ -60,7 +60,7 @@ This challenge is a frequent one, and many team relationships suffered from not Make yourself and the host team happy (and possibly save some work) by getting agreement from the host team on the user/technical design of the contribution _before_ working on the changes and submitting a pull request. You'll have to understand how the host team would like you to reach out for this. -It's best to ask a https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] about how to best discuss your proposal. +It's best to ask a https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] about how to best discuss your proposal. It is time-and-again-proven wisdom from the Open Source arena that, if you get to select how to discuss your proposal, you should try to select a written way. Ideally, choose the way where artifacts are public, searchable and perma-linkable to enable referencing your proposal in later discussions on this future contribution or other contributions to come - by you or others. @@ -103,19 +103,19 @@ Project teams are often happy to receive additions, updates or corrections for t We all have our preferences and opinions on code style, indentation, etc. The host team's project has them as well. -Try to adapt and match those preferences even if it's not what you would normally do, and even if it is not specified in the projects' https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[_`CONTRIBUTING.md`_]. +Try to adapt and match those preferences even if it's not what you would normally do, and even if it is not specified in the projects' https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[_`CONTRIBUTING.md`_]. If you are unsure, you can always ask politely. Nevertheless, a guest contribution for a feature or a bug fix is not the time to introduce a new way of structuring or formatting project code. === Submitting the pull request You've completed all the essential work, figured out all the quirks of the problem and the project you are contributing to, the time you've planned for the new feature to be used comes nearer, and you want to make sure your contribution gets merged in as fast and smooth as possible. -Here's what you can do to make reviewing and merging as easy as possible for the the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] and the host team. +Here's what you can do to make reviewing and merging as easy as possible for the the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] and the host team. This might actually be pretty similar to what you may already be doing on your own project to get your changes accepted. If that's the case - great, this is going to come natural to you! ==== Testing and automation -The basic point here is to enable the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] to validate the contribution without your presence and to ensure easy maintainability. +The basic point here is to enable the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] to validate the contribution without your presence and to ensure easy maintainability. Imagine you've built a feature or handling of an unsolvable quirk, or an important performance tweak, and your code is not entirely obvious (or might even look hacky / wrong at the first glance). If you have covered this with a test - and ideally have shed some words on the rationale behind it in a comment - a future editor will get reminded about the purpose of the code, and the test(s) will ensure that the value your code realizes will be kept, even in the new implementations. To achieve this, do the following: @@ -141,11 +141,11 @@ To make the actual code review as easy as possible for the trusted committer or * Provide a clear description of what this pull request changes, why it does so, and which issue and design documents (if there were any) it refers to. * If there is anything uncommon or unexpected in the pull request, highlight it and provide the explanation. This will make it easier to reason about and solve potential blocking questions that a reviewer might have during the review. ** The same goes for the scenario where you were unsure of the implementation or your approach - highlight it and ask for an insight. - ** Be civil and expect civility from the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer's_] review. + ** Be civil and expect civility from the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer's_] review. * Making pull requests too broad and large makes them more difficult to review, so it will take much longer before they're accepted. ** If you have a larger feature that you are contributing, it often helps to split it in multiple pull requests that are submitted, reviewed and accepted sequentially. You can still bind them together with an issue that you are referring to. - *** Some tools also have Draft / WIP pull request functionality that you can use to explicitly mark unfinished and non-polished work and still get early feedback from your host team's https://innersourcecommons.org/resources/learningpath/trusted-committer/02/[_Trusted Committers_]. + *** Some tools also have Draft / WIP pull request functionality that you can use to explicitly mark unfinished and non-polished work and still get early feedback from your host team's https://innersourcecommons.org/learn/learning-path/trusted-committer/02/[_Trusted Committers_]. *** This allows you to ensure that you are going down a path that your host team is happy to merge once it's done, adhering to the "release early, release often" idea in a way. *** The host team's responsibility is to create an atmosphere where sharing and discussing not-totally-polished work is possible and welcome. If you can't fail safe, you can't innovate, and collaboration becomes very hard. *** Try to balance between asking for a review early and providing meaningful changes to review. diff --git a/contributor/de/01-introduction-article-de.asciidoc b/contributor/de/01-introduction-article-de.asciidoc index 598c9713..a890f573 100644 --- a/contributor/de/01-introduction-article-de.asciidoc +++ b/contributor/de/01-introduction-article-de.asciidoc @@ -12,17 +12,17 @@ Wenn Du nicht bekommst, was Du benötigst, kannst Du die notwendige Änderung di Die Rolle des Contributors beschreibt eine Person, die zu den Repositories einer InnerSource Community beiträgt. Diese Person kann, muss aber nicht, Teil der Communitiy sein. Für nicht wenige Leute gibt es einen Weg, wie man als Contributor vom Zustand "ich kenne die Gemeinschaft" über "ich nutze das Produkt der Community und interagiere mit ihr" bis hin zu "ich trage zum Produkt der Community bei" gelangt. -Am Ende werden einige sogar https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Trusted Committers]. +Am Ende werden einige sogar https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Trusted Committers]. === Zusammenspiel mit anderen Rollen Als Contributor in einer InnerSource Community interagiert man mit Personen in anderen Rollen der InnerSource Community, wie dem -https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] oder dem https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] und wahrscheinlich mit anderen Contributoren. +https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] oder dem https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] und wahrscheinlich mit anderen Contributoren. Manchmal übernimmt eine Person mehrere Rollen, z. B. die des Trusted Committer und des Product Owner speziell in kleineren Projekten. Im Folgenden findest Du einen sehr kurzen Überblick über die anderen Rollen, aber wir möchten Dich ermutigen, die weiterführenden Artikel -https://innersourcecommons.org/resources/learningpath/trusted-committer/index[introductory article of the Trusted Committer role] und https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[Lowering the barriers to entry] zu lesen, bevor Du Dich tiefer in die Details der Contributor Rolle in diesem Abschnitt einarbeitest. -Alternativ kannst Du Dir auch unsere Videos zu den Themen anschauen: https://innersourcecommons.org/resources/learningpath/trusted-committer/index[introduction], https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[lowering the barriers to entry]. +https://innersourcecommons.org/learn/learning-path/trusted-committer/01[introductory article of the Trusted Committer role] und https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[Lowering the barriers to entry] zu lesen, bevor Du Dich tiefer in die Details der Contributor Rolle in diesem Abschnitt einarbeitest. +Alternativ kannst Du Dir auch unsere Videos zu den Themen anschauen: https://innersourcecommons.org/learn/learning-path/trusted-committer/01[introduction], https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[lowering the barriers to entry]. ==== Trusted Committer @@ -35,7 +35,7 @@ Sich um die Community zu kümmern beinhaltet es, die Community attraktiv zu halt ==== Product Owner -Die Rolle des https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] ähnelt der Rolle des Product Owners im klassischen Sinn. +Die Rolle des https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] ähnelt der Rolle des Product Owners im klassischen Sinn. Trotzdem gibt es Unterschiede - abhängig von der Größe des Projekts hat diese Rolle oft die gleiche Person inne, die auch als Trusted Committer agiert. In größeren Projekten oder in Teams, die InnerSource nur teilweise als Ansatz verwenden um ihre Anforderungen durch das Akzeptieren von Beiträgen zu erfüllen, werden die Rollen des Product Owners und des Trusted Committers in der Regel von unterschiedlichen Personen wahrgenommen. @@ -43,7 +43,7 @@ Deine Zusammenarbeit mit dem Product Owner wird sich wahrscheinlich darauf konze Möglicherweise ist der Product Owner auch daran beteiligt, Dich auf das Projekt, auf seine Vorteile, und auf die Cummunity selbst aufmerksam zu machen. -Wir emutigen Dich mehr über die anderen Rollen zu lernen, und haben deshalb weitere Artikel über den https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] und den https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] für Dich vorbereitet. +Wir emutigen Dich mehr über die anderen Rollen zu lernen, und haben deshalb weitere Artikel über den https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] und den https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] für Dich vorbereitet. === Kapitel Übersicht diff --git a/contributor/it/01-introduction-article-it.asciidoc b/contributor/it/01-introduction-article-it.asciidoc index 6651b7ab..ea5e040e 100644 --- a/contributor/it/01-introduction-article-it.asciidoc +++ b/contributor/it/01-introduction-article-it.asciidoc @@ -12,15 +12,15 @@ Se non ottieni quello di cui hai bisogno, puoi apportare le modifiche richieste Il ruolo del Contributore descrive una persona che dà contributi ai repository di un progetto comunitario InnerSource. Questa persona può o non può far parte o vedersi come parte della comunità. Tuttavia, per un bel po' di persone inizia una specie di viaggio che i contributori possono fare a partire dalla semplice conoscenza della comunità all'utilizzo del prodotto della comunità fino all'interazione con i membri della comunità e infine iniziare a contribuire. -Infine, alcuni di loro possono diventare https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Trusted Committers]. +Infine, alcuni di loro possono diventare https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Trusted Committers]. === Relazione con gli altri ruoli -Come Contributore all'interno di una comunità InnerSource andrai ad interagire con persone che ricoprono altri ruoli InnerSource, come il https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] o il https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] e possibilmente con altri contributori. +Come Contributore all'interno di una comunità InnerSource andrai ad interagire con persone che ricoprono altri ruoli InnerSource, come il https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] o il https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] e possibilmente con altri contributori. A volte, questi ruoli possono essere ricoperti dalla stessa persona, come ad esempio il Trusted Committer ed il Product Owner in piccole basi di progetti. -Questa sezione illustra una panoramica molto breve degli altri due ruoli, ma vorremmo incoraggiarti a leggere l'https://innersourcecommons.org/resources/learningpath/trusted-committer/index[articolo di introduzione del ruolo del Trusted Committer], e raccomandiamo anche di leggere l'articolo su come https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[Abbassare le barriere di ingresso], prima che tu approfondisca i dettagli del ruolo del Contributore in questa sezione. -Puoi anche guardare i video (https://innersourcecommons.org/resources/learningpath/trusted-committer/index[introduzione], https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[abbassare le barriere di ingresso]) invece di leggere gli articoli. +Questa sezione illustra una panoramica molto breve degli altri due ruoli, ma vorremmo incoraggiarti a leggere l'https://innersourcecommons.org/learn/learning-path/trusted-committer/01[articolo di introduzione del ruolo del Trusted Committer], e raccomandiamo anche di leggere l'articolo su come https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[Abbassare le barriere di ingresso], prima che tu approfondisca i dettagli del ruolo del Contributore in questa sezione. +Puoi anche guardare i video (https://innersourcecommons.org/learn/learning-path/trusted-committer/01[introduzione], https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[abbassare le barriere di ingresso]) invece di leggere gli articoli. ==== Trusted Committer @@ -33,7 +33,7 @@ Prendersi cura della comunità implica mantenerla in salute, migliorarla insieme ==== Product Owner -Il ruolo del https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] ha qualche somiglianza con il ruolo del product owner del tuo progetto di media dimensione. +Il ruolo del https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] ha qualche somiglianza con il ruolo del product owner del tuo progetto di media dimensione. Comunque, ci sono delle differenze - che dipendono dalla dimensione del progetto, questo ruolo è spesso ricoperto dalla stessa persona che agisce come truster committer. In progetti più grandi, o nei team che usano InnerSource solo parzialmente come approccio per coprire le loro necessità di accettazione di contributi, questo ruolo è probabilmente ricoperto da una persona diversa dal truster committer. @@ -42,7 +42,7 @@ Potresti lavorare con il ruolo del product owner per assicurarti che gli aspetti Ultimo ma non meno importante, qualcuno che agisce come product owner potrebbe essere stato coinvolto nel portare alla tua attenzione il progetto, i suoi benefici e la community. -Se vuoi sapere con maggior dettaglio di cosa trattano questi altri ruoli, e ti incoraggiamo a farlo, abbiamo preparato sezioni riguardo il https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] e sul https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_]. +Se vuoi sapere con maggior dettaglio di cosa trattano questi altri ruoli, e ti incoraggiamo a farlo, abbiamo preparato sezioni riguardo il https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] e sul https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_]. === Panoramica della sezione diff --git a/contributor/it/04-mechanics-of-contributing-article-it.asciidoc b/contributor/it/04-mechanics-of-contributing-article-it.asciidoc index 7b1ac691..8c3bc988 100644 --- a/contributor/it/04-mechanics-of-contributing-article-it.asciidoc +++ b/contributor/it/04-mechanics-of-contributing-article-it.asciidoc @@ -38,7 +38,7 @@ Questo effetto può essere osservato anche con l'Open Source, puoi leggere di pi Nei tuoi team classici tutti avevano un'idea dei tempi di consegna previsti. All'interno del contesto InnerSource questo potrebbe non essere il caso, a causa di grandi differenze di fuso orario (ad esempio Seattle, USA con PDT contro Berlin, Germania con CEST) o non sei disponibile a tempo pieno come il tuo team originale, anche se sono nella stessa posizione fisica in cui ti trovi. Pertanto, per prevenire la frustazione da entrambe le parti, come l'impazienza e altri effetti che non incentivano la fiducia, dovrai quindi gestire esplicitamente le aspettative per quanto riguarda i tempi di reazione previsti. -Un approccio consiste nel reagire rapidamente con un "Lo analizzerò, mi serviranno alcuni giorni" ad un feedback del https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer's_] se sai che potrai lavorarci in pochi giorni. +Un approccio consiste nel reagire rapidamente con un "Lo analizzerò, mi serviranno alcuni giorni" ad un feedback del https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer's_] se sai che potrai lavorarci in pochi giorni. Idealmente, puoi fornire loro una stima di massima di quando avrai il tempo per visionare il loro contributo. Facendo in questo modo costruisci fiducia per affidabilità anche per contatti non fisici, distanze maggiori o canali altrimenti asincroni. La fiducia stabilita ti permetterà di superare i momenti di incertezza nella strada collaborativa che hai da percorrere. @@ -62,7 +62,7 @@ Questa sfida è frequente e a molte relazioni tra team è capitato di incrinarsi Rendi felici te stesso e l'host team (e possibilmente risparmia un po' di lavoro) ottenendo un accordo dall'host team sulla progettazione tecnica / utente del contributo _prima_ di lavorare sulle modifiche ed inviare la pull request. Devi capire come l'host team vorrebbe che ti mettessi in contatto per questo. -La cosa migliore è chiedere al https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] come discutere al meglio la tua proposta. +La cosa migliore è chiedere al https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] come discutere al meglio la tua proposta. E' saggezza provata più volte nell'area Open Source che, se puoi scegliere come discutere la tua proposta, dovresti provare a selezionare un modo scritto. Idealmente, scegli la modalità dove gli artefacci sono pubblici, ricercabili e con link unici per consentire di fare riferimento alla tua proposta nelle discussioni successive su questo contributo futuro o su altri contributi a venire tuoi o di altri. @@ -104,18 +104,18 @@ I team di progetto sono spesso felici di ricevere aggiunte, aggiornamenti o corr Tutti noi abbiamo le nostre preferenze e opinioni sullo stile del codice, l'identazione, ecc. Anche il progetto dell'host team ne ha. -Cerca di adattare ed abbinare queste preferenze anche se non sono quello che tu avresti normalmente fatto, e anche se non è specificato nel file https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[_`CONTRIBUTING.md`_]. +Cerca di adattare ed abbinare queste preferenze anche se non sono quello che tu avresti normalmente fatto, e anche se non è specificato nel file https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[_`CONTRIBUTING.md`_]. Se non siete sicuri, potete sempre chiedere educatamente. Tuttavia, per un contributo di una funzionalità o per un bug fix non è il momento di introdurre un nuovo modo di struttrare o formattare il codice del progetto. === Invio della pull request Hai completato tutto il lavoro essenziale, capito tutte le stranezze del problema e il progetto a cui stai contribuendo, il momento che avevi pianificato per la nuova funzionalità si avvicina, e vuoi assicurarti che il tuo contributo venga usato tramite merge nel modo più veloce e fluido possibile. -Ecco quì quello che puoi fare per rendere la revisione ed il merging più facile possibile per il https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] e l'host team. +Ecco quì quello che puoi fare per rendere la revisione ed il merging più facile possibile per il https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] e l'host team. Questo potrebbe attualmente essere abbastanza simile a quello che potresti già fare sul tuo progetto per far accettare le tue modifiche. Se è così - fantastico, ti verrà naturale! ==== Test e automazione -Il punto fondamentale quì è abilitare il https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] a validare il contributo senza la tua presenza e assicurare una facile manutenibilità. +Il punto fondamentale quì è abilitare il https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] a validare il contributo senza la tua presenza e assicurare una facile manutenibilità. Immagina di aver creato una funzionalità o la gestione di una stranezza irrisolvibile, o di un'importante modifica delle prestazioni ed il tuo codice non è del tutto ovvio (o potrebbe persino sembrare orrendo / sbagliato a prima vista). Se l'hai coperta con un test - ed idealmente hai scritto due parole sul razionale che c'è dietro in un commento - ad un futuro editor verrà ricordato lo scopo del codice, ed i test assicureranno che il valore realizzato del tuo codice sarà mantenuto, anche nelle nuove implementazioni. Per ottenere ciò, procedi nel seguente modo: @@ -141,11 +141,11 @@ Per rendere la revisione del codice attuale quanto più semplice possibile per i * Fornisci una descrizione chiara di cosa viene modificato da questa pull request, perché lo fa in questo modo, e a quale issue e documenti di progettazione (se ce ne sono) fa riferimento. * Se c'è qualcosa di non comune o inaspettato nella pull request, sottolinealo e fornisci una spiegazione. Questo renderà più facile ragionarci sopra e risolvere potenziali domande bloccanti che un reviewer potrebbe avere durante la revisione. ** Lo stesso vale per lo scenario dove non eri sicuro dell'implementazione o del tuo approccio - sottolinealo e chiedi un approfondimento. - ** Sii civile e aspettati civiltà dalla revisione del https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer's_]. + ** Sii civile e aspettati civiltà dalla revisione del https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer's_]. * Fare pull request troppo ampie e grandi le rende più difficile da revisionare, quindi sarà necessario molto più tempo prima che vengano accettate. ** Se hai una funzionalità più grande che stai per contribuire, spesso aiuta dividerla in più pull request che sono da inviare, revisionare e accettare sequenzialmente. Puoi ancora raccoglierle insieme in una issue a cui fai riferimento. - *** Alcuni tool hanno anche la funzionalità di pull request per Draft / WIP che puoi usare per marchiare esplicitamente un lavoro non finito e non finalizzato e ricevi ancora un feedback immediato dal https://innersourcecommons.org/resources/learningpath/trusted-committer/02/[_Trusted Committers_] dell'host team. + *** Alcuni tool hanno anche la funzionalità di pull request per Draft / WIP che puoi usare per marchiare esplicitamente un lavoro non finito e non finalizzato e ricevi ancora un feedback immediato dal https://innersourcecommons.org/learn/learning-path/trusted-committer/02/[_Trusted Committers_] dell'host team. *** Questo ti permette di assicurare che stai procedendo verso un percorso che il tuo host team è felice di accogliere una volta fatto, aderendo all'approccio "rilascia presto, rilascia spesso". *** La responsabilità dell'host team è quella di creare un'atmosfera dove la condivisione e la discussione sul lavoro non del tutto finalizzato è possibile e benvenuta. Se non puoi fallire al sicuro, non puoi innovare, e la collaborazione diventa molto difficile. *** Cerca di trovare un equilibrio tra il chiedere per una revisione in anticipo e fornire modifiche significative alla revisione. diff --git a/contributor/ja/01-introduction-article-ja.asciidoc b/contributor/ja/01-introduction-article-ja.asciidoc index 1680bdee..cf1d144e 100644 --- a/contributor/ja/01-introduction-article-ja.asciidoc +++ b/contributor/ja/01-introduction-article-ja.asciidoc @@ -12,15 +12,15 @@ InnerSourceの原則を組み込んだプロジェクトでは、必要な機能 コントリビューターの役割は、InnerSourceコミュニティプロジェクトのリポジトリに貢献する人と表されます。 この人はコミュニティの一部の人であるかも知れないし、そうでないかも知れません。 しかし、かなりの数の人にとってコントリビューターとは、単にコミュニティについて知るだけのことから、コミュニティのプロダクトを使用し、コミュニティのメンバーと対話し、そして最終的に貢献を始めることができるという旅のようなものです。 -最終的に、そのうち何人かは https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Trusted Committer (トラステッドコミッター)] になるかも知れません。 +最終的に、そのうち何人かは https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Trusted Committer (トラステッドコミッター)] になるかも知れません。 === 他の役割との関係 -InnerSourceコミュニティにおけるコントリビューターとしてあなたは、 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_トラステッドコミッター_] や https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner (プロダクトオーナー)_] などのInnerSourceの他の役割を担っている人や、おそらく他のコントリビューターとも交流することになります。 +InnerSourceコミュニティにおけるコントリビューターとしてあなたは、 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_トラステッドコミッター_] や https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner (プロダクトオーナー)_] などのInnerSourceの他の役割を担っている人や、おそらく他のコントリビューターとも交流することになります。 まれに、小さな草の根スタイルのプロジェクトでは、トラステッドコミッターとプロダクトオーナーなどの役割は同じ人が行うことができます。 -この節では、他の2つの役割について非常に短い概要を説明しますが、 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[トラステッドコミッターの役割の紹介記事] と https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[参加障壁を下げる] 記事を、コントリビューターの役割をより深く掘り下げて説明する前に読むことを推奨します。 -記事を読む代わりに、ビデオ (https://innersourcecommons.org/resources/learningpath/trusted-committer/index[入門]、 https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[参入障壁を下げる]) を見ることもできます。 +この節では、他の2つの役割について非常に短い概要を説明しますが、 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[トラステッドコミッターの役割の紹介記事] と https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[参加障壁を下げる] 記事を、コントリビューターの役割をより深く掘り下げて説明する前に読むことを推奨します。 +記事を読む代わりに、ビデオ (https://innersourcecommons.org/learn/learning-path/trusted-committer/01[入門]、 https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[参入障壁を下げる]) を見ることもできます。 ==== トラステッドコミッター @@ -35,7 +35,7 @@ InnerSourceコミュニティにおけるコントリビューターとしてあ ==== プロダクトオーナー -https://innersourcecommons.org/resources/learningpath/product-owner/index[_プロダクトオーナー_] の役割は、平均的なプロジェクトのプロダクトオーナーの役割と、いくつかの類似点があります。 +https://innersourcecommons.org/learn/learning-path/product-owner/01[_プロダクトオーナー_] の役割は、平均的なプロジェクトのプロダクトオーナーの役割と、いくつかの類似点があります。 しかし、プロジェクトのサイズによって違いがありますが、この役割はトラステッドコミッターとして行動する同じ人が担当することがよくあります。 大規模なプロジェクトや、貢献を受け容れることで彼らのニーズを満たす部分にだけInnerSourceのアプローチを用いるチームでは、この役割はトラステッドコミッターとは別の人が担当する可能性があります。 @@ -44,7 +44,7 @@ https://innersourcecommons.org/resources/learningpath/product-owner/index[_プ 最後に重要なことですが、プロダクトオーナーとして行動している誰かは、プロジェクトやその利点およびコミュニティに対して、あなたの注目を引くことに関わっている可能性があります。 -もし、これらの他の役割に関する詳細を学びたい場合は、 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_トラステッドコミッター_] と https://innersourcecommons.org/resources/learningpath/product-owner/index[_プロダクトオーナー_] のセクションを別に用意してありますので、そちらをお勧めします。 +もし、これらの他の役割に関する詳細を学びたい場合は、 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_トラステッドコミッター_] と https://innersourcecommons.org/learn/learning-path/product-owner/01[_プロダクトオーナー_] のセクションを別に用意してありますので、そちらをお勧めします。 === セクションの概要 diff --git a/contributor/ja/04-mechanics-of-contributing-article-ja.asciidoc b/contributor/ja/04-mechanics-of-contributing-article-ja.asciidoc index 2bc5bd4c..044fa0c1 100644 --- a/contributor/ja/04-mechanics-of-contributing-article-ja.asciidoc +++ b/contributor/ja/04-mechanics-of-contributing-article-ja.asciidoc @@ -38,7 +38,7 @@ 従来のチームでは、誰もが予想されるリードタイムを知っていました。 InnerSouceのコンテキストでは、タイムゾーンの大きな違い（例えば、米国・シアトルのPDT（太平洋標準夏時間）とドイツ・ベルリンのCEST（中央ヨーロッパ夏時間））や、物理的に同じ場所にいたとしても所属元チームのようにフルタイムで対応できないなどの理由で。これが当てはまらないケースがあります。 したがって、双方のフラストレーションや焦り、その他の信頼構築以外への影響を防ぐために、予想される反応時間に関しての期待管理を明示的に行う必要があります。 -1つのアプローチは、もしあなたが数日後にしか彼らに反応できないことが分かっている場合に、 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] のフィードバックに対して、「調査しますが、数日では終わりそうにないです」とすばやく反応することです。 +1つのアプローチは、もしあなたが数日後にしか彼らに反応できないことが分かっている場合に、 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] のフィードバックに対して、「調査しますが、数日では終わりそうにないです」とすばやく反応することです。 理想的には、彼らのインプットを見る時間があると思われるときに、大まかな見積もりを提示することができます。 そうすることで、非物理的な接触、長距離、または非同期メディアを介しても信頼性による信頼が構築されます。 信頼関係の構築は、あなたの前にある共同道路での不確実性の壁を克服を可能にします。 @@ -62,7 +62,7 @@ InnerSourceでは、特にプロジェクトの決定に関して、文書によ 変更に取り組む前にコントリビューションのユーザー/技術面の設計についてホストチームから同意を得てから、プルリクエストを提出することで、自分自身とホストチームを幸せに(そしておそらくいくらか作業を節約)します。 あなたは、ホストチームがどのように手を差し伸べてほしいのかを理解する必要があります。 -あなたの提案をどのように議論するのが良いか、 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] に尋ねてみるのがベストです。 +あなたの提案をどのように議論するのが良いか、 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] に尋ねてみるのがベストです。 オープンソースの領域では何度も証明されているように、もしあなたの提案を議論する方法を選択できるとしたら、文書による方法を選択してみるべきです。 理想的には、あなたや他の誰かが後でこの機能のコントリビューションや他のコントリビューションに関してディスカッションする際に、あなたの提案を参照できるように、成果物が公開され、検索可能で、永続的にリンク可能である方法を選択することです。 @@ -106,7 +106,7 @@ InnerSourceでは、特にプロジェクトの決定に関して、文書によ 私たちは皆、コーディングスタイルやインデントなどについて好みや意見を持っています。 ホストチームのプロジェクトにも、それがあります。 -プロジェクトの https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[_`CONTRIBTING.md`_] で指定されておらず、あなたの通常の設定とは異なる場合でも、これらの設定を適合して一致するようにしてください。 +プロジェクトの https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[_`CONTRIBTING.md`_] で指定されておらず、あなたの通常の設定とは異なる場合でも、これらの設定を適合して一致するようにしてください。 もしわからなければ、いつでも丁寧に質問することができます。 しかし、機能やバグ修正に対するゲストの貢献は、プロジェクト・コードを構造化したりフォーマットしたりする新しい方法を導入するタイミングではありません。 @@ -115,13 +115,13 @@ InnerSourceでは、特にプロジェクトの決定に関して、文書によ あなたは、すべての重要な作業を完了し、問題と貢献しているプロジェクトのクセをすべて理解した上で、新しい機能を使用するために計画した時間が近くなり、できるだけ早くスムーズにあなたのコントリビューションがマージされるか確認したいと考えています。 -https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] とホストチームに対して、レビューとマージをできるだけ簡単に行えるようにするためにできることは、次のとおりです。 +https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] とホストチームに対して、レビューとマージをできるだけ簡単に行えるようにするためにできることは、次のとおりです。 これは実際に、自分のプロジェクトで変更を受け入れるために既に行っていることと非常によく似ているかもしれません。 もしそうであれば、すばらしい！あなたには、自然なものとなるでしょう。 ==== テストと自動化 -ここでの基本的なポイントは、 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] が、あなたなしでコントリビューションを検証し、保守性を確保しやすくすることです。 +ここでの基本的なポイントは、 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] が、あなたなしでコントリビューションを検証し、保守性を確保しやすくすることです。 あなたが解決できないようなクセのある機能や処理、あるいは重要なパフォーマンス調整を作成したのに、コードは完全には明らかでない(あるいは、一見したところハッキーで間違っているようにも見える)ことを想像してみてください。 もしあなたがこれをテストでこれをカバーしていて、理想的にはその背後にある理論的根拠についていくつかのコメントを残していたなら、将来の編集者はコードの目的を思い出すだろうし、テストはあなたのコードが実現する値が新しい実装でも維持されることを保証できるでしょう。 これを実現するには、次のことを行います。 @@ -147,10 +147,10 @@ https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_T * このプルリクエストの変更内容、変更の理由、参照する問題と設計ドキュメント(存在する場合)の明確な説明を提供してください。 * プルリクエストに一風変わったものや予期しないものが含まれている場合は、それをハイライトして説明してください。これにより、レビュー担当者がレビュー中に直面するかもしれない潜在的なブロックになる質問の理由付けや解決が容易になります。 ** 同じことが、実装やあなたのアプローチに確信が持てないシナリオにも当てはまります。それをハイライトして、洞察を求めてください。 - ** 礼儀正しく振る舞い、 https://innersourcecommons.org/resources/learningpath/trusted-committer/02/[_Trusted Committers_] からも礼儀正しさを期待しましょう + ** 礼儀正しく振る舞い、 https://innersourcecommons.org/learn/learning-path/trusted-committer/02/[_Trusted Committers_] からも礼儀正しさを期待しましょう * プルリクエストの範囲が広すぎたり大きすぎたりするとレビューが難しくなるため、受け入れられるまでにかなり時間がかかります。 ** より大きな機能を提供する場合は、その機能を複数のプルリクエストに分割して、順番に送信、レビュー、承認するようにすると助かることがよくあります。あなたが参照している問題と一緒にそれらをバインドすることもできます。 - *** 一部のツールにはドラフト/WIPプルリクエスト機能もあり、この機能を使用すると、未完了および未研磨の作業に明示的にマークを付けて、ホストチームの https://innersourcecommons.org/resources/learningpath/trusted-committer/02/[_Trusted Committers_] から早い段階でフィードバックを得ることができます。 + *** 一部のツールにはドラフト/WIPプルリクエスト機能もあり、この機能を使用すると、未完了および未研磨の作業に明示的にマークを付けて、ホストチームの https://innersourcecommons.org/learn/learning-path/trusted-committer/02/[_Trusted Committers_] から早い段階でフィードバックを得ることができます。 *** こうすることで、「早期リリース、頻繁なリリース」という考え方を堅持しながら、完了したらホストチームが喜んでマージできるような道を進むことができます。 *** ホストチームの責任は、完全に洗練されていない仕事を共有して議論することが可能で歓迎されるという雰囲気を作り出すことです。フェイルセーフできなければ、革新もできず、コラボレーションは非常に困難になります。 *** 早期にレビューを依頼することと、レビューに意味のある変更を提供することのバランスを取るようにしてください。 diff --git a/contributor/outline.asciidoc b/contributor/outline.asciidoc index 61c05edc..fd9a428e 100644 --- a/contributor/outline.asciidoc +++ b/contributor/outline.asciidoc @@ -7,7 +7,7 @@ * Summary of the roles of InnerSource and how each relates to _Contributor_. * Summary of the upcoming segments and what each covers. -Outline for this section inspired by the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Trusted Committer introduction video]. +Outline for this section inspired by the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Trusted Committer introduction video]. === Becoming an InnerSource Contributor @@ -143,4 +143,4 @@ Review what we've learned/taught together. * Summary of the other sections in the learning path with invitation to watch. * Summary of the InnerSource Commons and invitation to join. -Outline for this section inspired by the https://innersourcecommons.org/resources/learningpath/trusted-committer/08/[Trusted Committer conclusion]. +Outline for this section inspired by the https://innersourcecommons.org/learn/learning-path/trusted-committer/08/[Trusted Committer conclusion]. diff --git a/contributor/video-proposal.asciidoc b/contributor/video-proposal.asciidoc index 50050d09..fec36d57 100644 --- a/contributor/video-proposal.asciidoc +++ b/contributor/video-proposal.asciidoc @@ -42,8 +42,8 @@ This section teaches the mindset, the habits, technical approaches and other det ==== Prerequisites * Please watch the https://www.safaribooksonline.com/videos/introduction-to-innersource/9781492041504[Intro to InnerSource Video] -* Also watch the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Introduction] to the Trusted Committer role. -* The https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[Lowering the Barriers to Entry] video of the Trusted Committer role can be a good addition to understand more of why the Trusted Committer might ask for different things. +* Also watch the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Introduction] to the Trusted Committer role. +* The https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[Lowering the Barriers to Entry] video of the Trusted Committer role can be a good addition to understand more of why the Trusted Committer might ask for different things. ==== Materials or downloads needed in advance diff --git a/contributor/zh/01-introduction-zh.asciidoc b/contributor/zh/01-introduction-zh.asciidoc index 7e863478..a0f2a164 100644 --- a/contributor/zh/01-introduction-zh.asciidoc +++ b/contributor/zh/01-introduction-zh.asciidoc @@ -10,7 +10,7 @@ ### 与其他角色的关系 -作为 InnerSource 社区中的贡献者，你将与 InnerSource 的其他角色（例如 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_Trusted Committer_] 或 https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品所有者（Product Owner）_] ）进行交互，也可能与其他贡献者进行交互。有时，这些角色可以由同一个人扮演，例如小型基础项目中的“Trusted Committer”和“产品所有者”。 +作为 InnerSource 社区中的贡献者，你将与 InnerSource 的其他角色（例如 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_Trusted Committer_] 或 https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品所有者（Product Owner）_] ）进行交互，也可能与其他贡献者进行交互。有时，这些角色可以由同一个人扮演，例如小型基础项目中的“Trusted Committer”和“产品所有者”。 本节为你简要概述了其他两个角色，但我们想鼓励你去阅读 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_“Trusted Committer”的介绍文章_] ，也推荐你在深入研究本节的“贡献者”角色之前阅读 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/05/[_降低准入门槛_] 一文，你也可以观看视频（ https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_介绍_]、 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/05/[_降低准入门槛_]）而无需阅读文章。 @@ -22,14 +22,14 @@ Trusted Committer是社区的主人，他们对项目代码把关，审核你贡 ### 产品所有者（Product Owner） -https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品所有者（Product Owner）_]的角色与普通项目的产品所有者角色有些相似，但根据项目的大小会有所不同。此角色通常和Trusted Committer是同一个人，但在大项目或部分通过使用 InnerSource 的贡献来满足需求的团队中，此角色可能与受信任提交者不是同一个人。 +https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品所有者（Product Owner）_]的角色与普通项目的产品所有者角色有些相似，但根据项目的大小会有所不同。此角色通常和Trusted Committer是同一个人，但在大项目或部分通过使用 InnerSource 的贡献来满足需求的团队中，此角色可能与受信任提交者不是同一个人。 你需与产品所有者沟通以确保你的贡献与对通用产品和产品发展路线的相一致。你可与产品所有者一同以确保在合并你贡献是相关的文档或UI / UX时都保持一致。 最后重要的一点，有些原本可能涉及该项目的产品所有者，你需关注他带来的收益和对社区的影响。 如果你想更深入的了解这些其他角色，我们也鼓励你这样做，为此我们准备了有关 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_Trusted Committer_] -或 https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品所有者（Product Owner）_] 的单独部分。 +或 https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品所有者（Product Owner）_] 的单独部分。 ### 概述 diff --git a/contributor/zh/04-mechanics-of-contributing-zh.asciidoc b/contributor/zh/04-mechanics-of-contributing-zh.asciidoc index 957b3a8c..972d6df6 100755 --- a/contributor/zh/04-mechanics-of-contributing-zh.asciidoc +++ b/contributor/zh/04-mechanics-of-contributing-zh.asciidoc @@ -21,7 +21,7 @@ ==== 期望管理 -在你以往的团队中，每个人都对预期的交付周期有一个概念。在InnerSource中可能不是这样的，这可能是由于时差较大（例如美国西雅图的PDT与德国柏林的CEST）或你将不能像以往的团队一样全职工作，即使你们在一个地区。因此，为了防止双方都感到沮丧、不耐烦和其他不信任的影响，你需要明确地对自己的预期的反应时间进行期望管理。一种方法是快速的回复 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] ：“我得过几天后才能看看”，如果你知道你得几天后才有空。理想情况下，当你有空时可以给他们一个粗略的时间预估。这样做即使在非物理接触，在更长的距离或其他异步媒介上也可以通过可靠性建立信任。建立起的信任会让你克服合作道路上的不确定性。 +在你以往的团队中，每个人都对预期的交付周期有一个概念。在InnerSource中可能不是这样的，这可能是由于时差较大（例如美国西雅图的PDT与德国柏林的CEST）或你将不能像以往的团队一样全职工作，即使你们在一个地区。因此，为了防止双方都感到沮丧、不耐烦和其他不信任的影响，你需要明确地对自己的预期的反应时间进行期望管理。一种方法是快速的回复 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] ：“我得过几天后才能看看”，如果你知道你得几天后才有空。理想情况下，当你有空时可以给他们一个粗略的时间预估。这样做即使在非物理接触，在更长的距离或其他异步媒介上也可以通过可靠性建立信任。建立起的信任会让你克服合作道路上的不确定性。 ==== 建立信任 @@ -33,7 +33,7 @@ InnerSource重视书面交流-特别是在项目决策方面。 这是否意味 你有想要贡献的大型的功能吗？太棒了！如果你所有的工作都被浪费了，岂不是很恐怖？当项目团队已经在做了非常相似的东西，打算弃用该项目或觉得你提供的不适合他们的项目时，就会发生这种情况。这一挑战时经常发生的，许多团队关系都因没有事先对一个贡献是否适合项目形成统一意见而受到影响。 -在进行改动和 pull requests 之前，先征得维护团队对用户/技术设计的同意，以使自己和维护团队都满意（且可能可以节省一些工作）。你必须了解维护团队希望你如何做到这一点，最好是向 https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_]请教如何最好的讨论你的提案。 +在进行改动和 pull requests 之前，先征得维护团队对用户/技术设计的同意，以使自己和维护团队都满意（且可能可以节省一些工作）。你必须了解维护团队希望你如何做到这一点，最好是向 https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_]请教如何最好的讨论你的提案。 开源领域经过反复验证出的明智的做法是，如果你在考虑选择哪种方式讨论你的提案，你应该尝试选择书面方式。理想情况下，在将来关于你的贡献的讨论中，选择材料公开的，可搜索的和可永久链接到的文档来引用你的提案。 diff --git a/introduction/03-how-works.asciidoc b/introduction/03-how-works.asciidoc index 5637ff8d..52cef5a2 100644 --- a/introduction/03-how-works.asciidoc +++ b/introduction/03-how-works.asciidoc @@ -20,9 +20,9 @@ These concepts around a home visit are a metaphor for the attitude and behaviors Let's take a closer look at how the mechanics of the InnerSource process can work. To aid in this explanation, we'll name a few key individuals on the guest and host teams. -First, the https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] determines what functionality the host team is willing to accept as a contribution. -The https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributor_] is the individual on the guest team that submits the code contribution for review by the host team. -The https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] represents the host team in providing any timely support and mentorship that the contributor needs to successfully submit the pull request. +First, the https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] determines what functionality the host team is willing to accept as a contribution. +The https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributor_] is the individual on the guest team that submits the code contribution for review by the host team. +The https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] represents the host team in providing any timely support and mentorship that the contributor needs to successfully submit the pull request. On small, grass roots efforts a single person often fills _both_ the product owner and trusted committer roles. With those definitions, here is the basic outline of an InnerSource contribution. diff --git a/introduction/04-benefits.asciidoc b/introduction/04-benefits.asciidoc index a79fe14a..6667b151 100644 --- a/introduction/04-benefits.asciidoc +++ b/introduction/04-benefits.asciidoc @@ -21,7 +21,7 @@ Beyond the raw work that the host team is able to accomplish in its system, regu A host team can do its best requirements gathering on the work it produces, but when the consumer itself is the one submitting the work the chances are much higher that the resulting change is aligned to just what the consumer needs. While it may be only one single guest team submitting the change, that team is likely representative of many other consumers. -In addition to this alignment, there is also a general training and education of https://innersourcecommons.org/resources/learningpath/contributor/index[contributors] as they work with and learn from https://innersourcecommons.org/resources/learningpath/trusted-committer/index[trusted committers]. +In addition to this alignment, there is also a general training and education of https://innersourcecommons.org/learn/learning-path/contributor/01[contributors] as they work with and learn from https://innersourcecommons.org/learn/learning-path/trusted-committer/01[trusted committers]. This interaction helps contributors to learn and grow in their career, resulting in *higher job satisfaction*. Project documentation improves to enable these contributions at scale. Contributors feel a stake in the host team project. diff --git a/introduction/05-principles.asciidoc b/introduction/05-principles.asciidoc index eac5b914..936fed36 100644 --- a/introduction/05-principles.asciidoc +++ b/introduction/05-principles.asciidoc @@ -45,8 +45,8 @@ This communication should be done in a manner that can be easily queried and und === Prioritized Mentorship -_Mentorship_ from host team to guest team via https://innersourcecommons.org/resources/learningpath/trusted-committer/index[trusted committers] is a key aspect of InnerSource. -https://innersourcecommons.org/resources/learningpath/contributor/index[Contributors] on guest teams are upleveled so that they understand enough about the host team's project/repo to change it successfully. +_Mentorship_ from host team to guest team via https://innersourcecommons.org/learn/learning-path/trusted-committer/01[trusted committers] is a key aspect of InnerSource. +https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] on guest teams are upleveled so that they understand enough about the host team's project/repo to change it successfully. In the process of doing so, they come to better understand the host team's software system as a general consumer and ambassador for the project/software. This individual contributor can, over time and with experience, take on a broader role in the project as a trusted committer. diff --git a/introduction/06-conclusion.asciidoc b/introduction/06-conclusion.asciidoc index cb92de8f..f3251f77 100644 --- a/introduction/06-conclusion.asciidoc +++ b/introduction/06-conclusion.asciidoc @@ -3,7 +3,7 @@ In this learning path, we've given an introduction to InnerSource. InnerSource applies open source best practices and principles to internal software development. It gives an additional option to consumers when producing teams are not able to deliver a needed feature request. -Successful InnerSource involves a https://innersourcecommons.org/resources/learningpath/product-owner/index[_product owner_] and https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_trusted committer_] from the *host team* as well as a https://innersourcecommons.org/resources/learningpath/contributor/index[_contributor_] from the *guest team*. +Successful InnerSource involves a https://innersourcecommons.org/learn/learning-path/product-owner/01[_product owner_] and https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_trusted committer_] from the *host team* as well as a https://innersourcecommons.org/learn/learning-path/contributor/01[_contributor_] from the *guest team*. Done effectively, InnerSource brings many benefits to both participating teams. They key principles upon-which effective InnerSource works are *voluntary code contribution* and *prioritized mentorship*. diff --git a/introduction/de/03-how-works-de.asciidoc b/introduction/de/03-how-works-de.asciidoc index d137473e..bbae084e 100644 --- a/introduction/de/03-how-works-de.asciidoc +++ b/introduction/de/03-how-works-de.asciidoc @@ -20,9 +20,9 @@ Diese Konzepte rund um einen Besuch sind eine Metapher für Einstellung und Verh Werfen wir einen genaueren Blick darauf, wie der InnerSource-Prozess funktioniert. Bevor wir in das Thema tiefer einsteigen, schauen wir uns einige wichtige Rollen in den Gast- und Gastgeberteams an. -Zunächst legt der https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] fest, welche Funktionen das Hostteam als Beitrag zu akzeptieren bereit ist. -Der https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributor_] ist die Person im Gastteam, die den Codebeitrag einreicht, welcher dann durch das Hostteam geprüft und ggf. akzeptiert wird. -Der https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] steht dem Hostteam als zusätzliche Unterstützung für Review- und Mentoringaufgaben bei, um letztendlich den Contributor mit seinem Pullrequest zu unterstützen. +Zunächst legt der https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] fest, welche Funktionen das Hostteam als Beitrag zu akzeptieren bereit ist. +Der https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributor_] ist die Person im Gastteam, die den Codebeitrag einreicht, welcher dann durch das Hostteam geprüft und ggf. akzeptiert wird. +Der https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] steht dem Hostteam als zusätzliche Unterstützung für Review- und Mentoringaufgaben bei, um letztendlich den Contributor mit seinem Pullrequest zu unterstützen. Bei kleinen, einfacheren Projekten füllt oft eine einzelne Person _sowohl_ die Rolle des Product Owners als auch die des Trusted Committer aus. Basierend auf diesen Rollen können wir nun den InnerSource-Prozesses grob skizzieren. diff --git a/introduction/de/04-benefits-de.asciidoc b/introduction/de/04-benefits-de.asciidoc index cc57c626..8aad2c6b 100644 --- a/introduction/de/04-benefits-de.asciidoc +++ b/introduction/de/04-benefits-de.asciidoc @@ -21,7 +21,7 @@ Neben der einfachen Verbesserung der Funktionalität die das Hostteam erzielen k Ein Hostteam kann mit größtem Aufwand Anforderungen für Ihr Produkt sammeln, wenn jedoch der Nutzer selbst die jeweilige Anforderung einreicht, sind die Chancen erheblich höher, dass die daraus resultierende Änderung genau auf die Bedürfnisse des Nutzers abgestimmt ist. Weiterhin gilt, während es möglicherweise nur ein einziges Gastteam die Änderung einreicht, ist dieses Team wahrscheinlich auch repräsentativ für andere Nutzer. -Zusätzlich zu den oben aufgezeigten Vorteilen, bietet diese Art der Zusammenarbeit auch eine Chance zur Weiterbildung der https://innersourcecommons.org/resources/learningpath/contributor/index[Contributors], während sie mit ihnen arbeiten und von ihnen als https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Trusted Committers] lernen. +Zusätzlich zu den oben aufgezeigten Vorteilen, bietet diese Art der Zusammenarbeit auch eine Chance zur Weiterbildung der https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors], während sie mit ihnen arbeiten und von ihnen als https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Trusted Committers] lernen. Diese Interaktionen helfen den Mitwirkenden in zu lernen und zu wachsen, was zu letztendlich zu einer *höheren Arbeitszufriedenheit* führt. Weiterhin wird im Allgemeinen die Projektdokumentation schrittweise verbessert, um Gastbeiträge in großem Maßstab zu ermöglichen und zu fördern. Natürlich ist auch nicht zu vergessen, dass sich die Mitwirkenden am Projekt des Hostteams beteiligt fühlen. diff --git a/introduction/de/05-principles-de.asciidoc b/introduction/de/05-principles-de.asciidoc index e040ef0e..9271f369 100644 --- a/introduction/de/05-principles-de.asciidoc +++ b/introduction/de/05-principles-de.asciidoc @@ -45,8 +45,8 @@ Diese Kommunikation sollte auf eine Weise erfolgen, sodass die Information für === Priorisierte Betreuung -_Mentorship_ vom Hostteam zum Gastteam durch https://innersourcecommons.org/resources/learningpath/trusted-committer/index[Trusted Committers] ist ein Schlüsselaspekt von InnerSource. -https://innersourcecommons.org/resources/learningpath/contributor/index[Contributors] in Gastteams sind auf dem neuesten Stand, sodass sie genug über das Projekt / Repo des Host-Teams wissen um es erfolgreich verändern zu können. +_Mentorship_ vom Hostteam zum Gastteam durch https://innersourcecommons.org/learn/learning-path/trusted-committer/01[Trusted Committers] ist ein Schlüsselaspekt von InnerSource. +https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] in Gastteams sind auf dem neuesten Stand, sodass sie genug über das Projekt / Repo des Host-Teams wissen um es erfolgreich verändern zu können. Dabei lernen sie die Software des Hostteams sowohl als genereller Nutzer als auch als Botschafter für das Projekt / die Software besser verstehen. Diese einzelnen Mitarbeiter können im Laufe der Zeit und mit wachsender Erfahrung eine breitere Rolle im Projekt als Trusted Committer zu übernehmen. diff --git a/introduction/de/06-conclusion-de.asciidoc b/introduction/de/06-conclusion-de.asciidoc index 3246fceb..1735e119 100644 --- a/introduction/de/06-conclusion-de.asciidoc +++ b/introduction/de/06-conclusion-de.asciidoc @@ -3,7 +3,7 @@ In dieser Serie haben wir eine Einführung in InnerSource gegeben. InnerSource wendet Open Source Praktiken und Prinzipien auf die firmeninterne Softwareentwicklung an. Es bietet Nutzern eine zusätzliche Option, speziell wenn Produktionsteams nicht in der Lage sind, ein erforderliches Requirement im notwendigen Zeitraum zu liefern. -Erfolgreiche InnerSource Projekte betreffen https://innersourcecommons.org/resources/learningpath/product-owner/index[_Produkt Owner_] und https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-Committer/01-Introduction.asciidoc [_Trusted Committer_] vom *Hostteam* sowie ein https://innersourcecommons.org/resources/learningpath/contributor/index [_Contributor_] vom *Gastteam*. +Erfolgreiche InnerSource Projekte betreffen https://innersourcecommons.org/learn/learning-path/product-owner/01[_Produkt Owner_] und https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/trusted-Committer/01-Introduction.asciidoc [_Trusted Committer_] vom *Hostteam* sowie ein https://innersourcecommons.org/learn/learning-path/contributor/01 [_Contributor_] vom *Gastteam*. Richtig betriebenes InnerSource bietet beiden teilnehmenden Teams viele Vorteile. Die Schlüsselprinzipien, nach denen gut geführte InnerSource Projekte funktionieren, sind *freiwilliger Code-Beitrag* und *Mentoring Fokus*. diff --git a/introduction/it/03-how-works.asciidoc b/introduction/it/03-how-works.asciidoc index f21af779..547c63e9 100644 --- a/introduction/it/03-how-works.asciidoc +++ b/introduction/it/03-how-works.asciidoc @@ -20,9 +20,9 @@ Questi concetti intorno alla visita a casa sono una metafora per l'attitudine ed Diamo un'occhiata più da vicino a come possono funzionare le meccaniche relative al processo InnerSource. Per aiutare in questa spiegazione, nomineremo alcune persone chiave nei team guest e host. -Per primo, il https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] decide quale funzionalità l'host team è disposto ad accettare come una contribuzione. -Il https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributor_] è l'individuo nel guest team che invia il codice della contribuzione in revisione da parte dell'host team. -Il https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] rappresenta l'host team nel fornire supporto tempestivo e mentoring di cui il contributore ha bisogno per inviare con successo la pull request. +Per primo, il https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] decide quale funzionalità l'host team è disposto ad accettare come una contribuzione. +Il https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributor_] è l'individuo nel guest team che invia il codice della contribuzione in revisione da parte dell'host team. +Il https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] rappresenta l'host team nel fornire supporto tempestivo e mentoring di cui il contributore ha bisogno per inviare con successo la pull request. Con piccoli sforzi dal basso, una singola persona spesso ricopre _entrambi_ i ruoli di product owner e trusted committer. diff --git a/introduction/it/04-benefits.asciidoc b/introduction/it/04-benefits.asciidoc index a570df60..5045dcfb 100644 --- a/introduction/it/04-benefits.asciidoc +++ b/introduction/it/04-benefits.asciidoc @@ -20,7 +20,7 @@ Oltre la lavoro grezzo che l'host team è in grado di svolgere nel proprio siste Un host team può soddisfare al meglio la raccolta dei requisiti nel lavoro che produce, ma quando è l'utente stesso a presentare il lavoro, le possibilità sono molto più alte che il cambiamento risultante sia allineato a ciò di cui l'utente ha bisogno. Mentre potrebbe esserci solamente un singolo cambiamento inviato al guest team, questo team è probabilmente rappresentativo di molti altri utenti. -In aggiunta a questo allineamento, c'è anche la formazione e istruzione generale dei https://innersourcecommons.org/resources/learningpath/contributor/index[contributors] mentre lavorano ed imparano dai https://innersourcecommons.org/resources/learningpath/trusted-committer/index[trusted committers]. +In aggiunta a questo allineamento, c'è anche la formazione e istruzione generale dei https://innersourcecommons.org/learn/learning-path/contributor/01[contributors] mentre lavorano ed imparano dai https://innersourcecommons.org/learn/learning-path/trusted-committer/01[trusted committers]. Questa interazione aiuta i contributori ad imparare e accrescere le loro carriere, con conseguente *maggiore soddisfazione del lavoro*. La documentazione del progetto migliora per abilitare queste contribuzioni su larga scala. I contributori sentono un interesse nel progetto dell'host team. diff --git a/introduction/it/05-principles.asciidoc b/introduction/it/05-principles.asciidoc index 522a42fb..d1320157 100644 --- a/introduction/it/05-principles.asciidoc +++ b/introduction/it/05-principles.asciidoc @@ -43,8 +43,8 @@ Questa comunicazione dovrebbe essere fatta in maniera tale che possa essere faci === Tutoraggio prioritizzato -Il _tutoraggio_ dall'host team al guest team attraverso i https://innersourcecommons.org/resources/learningpath/trusted-committer/index[trusted committers] è un aspetto chiave dell'InnerSource. -I https://innersourcecommons.org/resources/learningpath/contributor/index[Contributors] nel guest team vengono allineati contestualmente in modo tale da far loro capire abbastanza il progetto/repository dell'host team al fine di poterlo modificare con successo. +Il _tutoraggio_ dall'host team al guest team attraverso i https://innersourcecommons.org/learn/learning-path/trusted-committer/01[trusted committers] è un aspetto chiave dell'InnerSource. +I https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] nel guest team vengono allineati contestualmente in modo tale da far loro capire abbastanza il progetto/repository dell'host team al fine di poterlo modificare con successo. Nel fare ciò, arrivano a capire meglio il sistema software dell'host team come un utente e ambasciatore del progetto/software. Questo singolo contributore può, con il passare del tempo e con l'esperienza, assumere un ruolo più alto nel progegtto com quello di trusted committer. diff --git a/introduction/it/06-conclusion.asciidoc b/introduction/it/06-conclusion.asciidoc index 53cd0cd5..7422ebee 100644 --- a/introduction/it/06-conclusion.asciidoc +++ b/introduction/it/06-conclusion.asciidoc @@ -3,7 +3,7 @@ In questo percorso formativo, abbiamo introdotto l'InnerSource. L'InnerSource applica principi e best practice dell'open source allo sviluppo software interno. Questo approccio rende disponibile un'opzione ulteriore agli utenti quando i team di produzione non sono in grado di consegnare una richiesta di funzionalità necessaria. -L'InnerSource di successo coinvolge un https://innersourcecommons.org/resources/learningpath/product-owner/index[_product owner_] e un https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_trusted committer_] dell'*host team* così come un https://innersourcecommons.org/resources/learningpath/contributor/index[_contributor_] del *guest team*. +L'InnerSource di successo coinvolge un https://innersourcecommons.org/learn/learning-path/product-owner/01[_product owner_] e un https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_trusted committer_] dell'*host team* così come un https://innersourcecommons.org/learn/learning-path/contributor/01[_contributor_] del *guest team*. Fatto in modo efficare, l'InnerSource porta molti vantaggi ad entrambi i team partecipanti. I principi chiave su cui si basa l'InnerSource sono *contribuzione volontaria al codice* ed il *tutoraggio prioritizzato*. diff --git a/introduction/ja/03-how-works-ja.asciidoc b/introduction/ja/03-how-works-ja.asciidoc index 635c4ff5..54239f78 100644 --- a/introduction/ja/03-how-works-ja.asciidoc +++ b/introduction/ja/03-how-works-ja.asciidoc @@ -21,9 +21,9 @@ _ゲスト_ や _ホスト_ の用語は、自宅にお客を招くような感 それでは、InnerSourceのプロセスの仕組みがどのように機能するかを見てみましょう。 この説明の補足として、ここでゲストチームとホストチームそれぞれのキーパーソンとなる人に名前を付けておきます。 -まず、 https://innersourcecommons.org/resources/learningpath/product-owner/index[_プロダクトオーナー_] は、ホストチームが受け入れるコントリビューションがどの機能かを決定します。 -https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] は、ゲストチーム内の個人で、ホストチームにレビューしてもらうためにコードを投稿します。 -https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_トラステッドコミッター_] は、ホストチームを代表する人であり、コントリビューターがプルリクエストを正しく投稿するために必要な指導やタイムリーなサポートを提供します。 +まず、 https://innersourcecommons.org/learn/learning-path/product-owner/01[_プロダクトオーナー_] は、ホストチームが受け入れるコントリビューションがどの機能かを決定します。 +https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] は、ゲストチーム内の個人で、ホストチームにレビューしてもらうためにコードを投稿します。 +https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_トラステッドコミッター_] は、ホストチームを代表する人であり、コントリビューターがプルリクエストを正しく投稿するために必要な指導やタイムリーなサポートを提供します。 小さな草の根活動的な取り組みでは、一人でプロダクトオーナーとトラステッドコミッター _両方_ の役目をすることがあります。 これらの定義を用いて、InnerSourceのコントリビューションに関する基本的なアウトラインを説明すると、次のようになります。 diff --git a/introduction/ja/04-benefits-ja.asciidoc b/introduction/ja/04-benefits-ja.asciidoc index be56c8ff..1be44025 100644 --- a/introduction/ja/04-benefits-ja.asciidoc +++ b/introduction/ja/04-benefits-ja.asciidoc @@ -21,7 +21,7 @@ InnerSourceは、組織が必要とする時と場所にエンジニアリング ホストチームは、作成した作業について最高の要件収集を行うことができますが、利用者自信が作業を提出する場合、結果として、行われた変更が利用者のニーズと合致する可能性がはるかに高くなります。 変更を提出しているのは、1つのゲストチームだけかもしれませんが、そのチームが他の多くの利用者を代表している可能性があります。 -こうした調整に加えて、 https://innersourcecommons.org/resources/learningpath/contributor/index[コントリビューター] が https://innersourcecommons.org/resources/learningpath/trusted-committer/index[トラステッドコミッター] と一緒に働き、そこから学ぶことは、一般的なトレーニングや教育にもなります。 +こうした調整に加えて、 https://innersourcecommons.org/learn/learning-path/contributor/01[コントリビューター] が https://innersourcecommons.org/learn/learning-path/trusted-committer/01[トラステッドコミッター] と一緒に働き、そこから学ぶことは、一般的なトレーニングや教育にもなります。 こうした対話は、コントリビューターのキャリア形成における成長や学習に寄与し、結果として *仕事への満足度が高くなります* 。 プロジェクトのドキュメントは、大規模なコントリビューションを可能にするために改善されます。 コントリビューターは、ホストチームのプロジェクトとの一体感を感じます。 diff --git a/introduction/ja/05-principles-ja.asciidoc b/introduction/ja/05-principles-ja.asciidoc index 3049fea0..559cc386 100644 --- a/introduction/ja/05-principles-ja.asciidoc +++ b/introduction/ja/05-principles-ja.asciidoc @@ -45,8 +45,8 @@ InnerSourceのコントリビューションを彼らのプロジェクトに受 === 優先的なメンターシップ -https://innersourcecommons.org/resources/learningpath/trusted-committer/index[トラステッドコミッター] によるホストチームからゲストチームへの _メンターシップ_ は、InnerSourceの重要な点になります。 -ゲストチームの https://innersourcecommons.org/resources/learningpath/contributor/index[コントリビューター] は、ホストチームのプロジェクト/リポジトリについて十分理解し、成功裏に変更できるようにレベルアップされます。 +https://innersourcecommons.org/learn/learning-path/trusted-committer/01[トラステッドコミッター] によるホストチームからゲストチームへの _メンターシップ_ は、InnerSourceの重要な点になります。 +ゲストチームの https://innersourcecommons.org/learn/learning-path/contributor/01[コントリビューター] は、ホストチームのプロジェクト/リポジトリについて十分理解し、成功裏に変更できるようにレベルアップされます。 この過程で、彼らはプロジェクト/ソフトウェアの一般的な利用者かつアンバサダーとして、ホストチームのソフトウェアシステムをより良く理解するようになります。 この個人のコントリビューターは、経験を重ねることで、トラステッドコミッターとしてプロジェクトでより広範な役割を果たすことができます。 diff --git a/introduction/ja/06-conclusion-ja.asciidoc b/introduction/ja/06-conclusion-ja.asciidoc index 644d6640..b7b62025 100644 --- a/introduction/ja/06-conclusion-ja.asciidoc +++ b/introduction/ja/06-conclusion-ja.asciidoc @@ -3,7 +3,7 @@ このラーニングパスでは、InnerSourceの紹介をしました。 InnerSourceは、企業内のソフトウェア開発にオープンソースのベストプラクティスと原則を適用したものです。 これは、提供側のチームが必要な機能要件を提供することができない時に、利用者に追加オプションを提供するものです。 -InnroSourceの成功には、 *ホストチーム* の https://innersourcecommons.org/resources/learningpath/product-owner/index[_プロダクトオーナー_] と https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_トラステッドコミッター_] 、そして *ゲストチーム* の https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] が関わります。 +InnroSourceの成功には、 *ホストチーム* の https://innersourcecommons.org/learn/learning-path/product-owner/01[_プロダクトオーナー_] と https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_トラステッドコミッター_] 、そして *ゲストチーム* の https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] が関わります。 効果的に行うと、InnerSourceは両方の参加チームに多くの効果をもたらします。 効果的なInnerSource実施の主要な原則は、 *自発的なコードコントリビューション* と *優先的なメンターシップ* です。 diff --git a/introduction/ru/03-how-works.asciidoc b/introduction/ru/03-how-works.asciidoc index 9888fd18..cb375759 100644 --- a/introduction/ru/03-how-works.asciidoc +++ b/introduction/ru/03-how-works.asciidoc @@ -20,9 +20,9 @@ Теперь рассмотрим механику InnerSource. Для начала представим ключевых лиц процесса. -* https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_] или Владелец Продукта. Определяет функционал, который команда хозяев готова принять от гостевых команд. -* https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributor_] или Контрибьютор. Член гостевой команды, который отправляет код на ревью команде хозяев. -* https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] или Доверенный Коммиттер. Представитель команды хозяев, наставляет и обучает Контрибьюторов, помогая создать и отправить Pull Request. В небольших продуктах роли Product Owner и Trusted Committer могут выполняться одним человеком. +* https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_] или Владелец Продукта. Определяет функционал, который команда хозяев готова принять от гостевых команд. +* https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributor_] или Контрибьютор. Член гостевой команды, который отправляет код на ревью команде хозяев. +* https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] или Доверенный Коммиттер. Представитель команды хозяев, наставляет и обучает Контрибьюторов, помогая создать и отправить Pull Request. В небольших продуктах роли Product Owner и Trusted Committer могут выполняться одним человеком. Теперь рассмотрим план входящей контрибьюции по InnerSource. diff --git a/introduction/ru/06-conclusion.asciidoc b/introduction/ru/06-conclusion.asciidoc index ad1ca968..96a603cd 100644 --- a/introduction/ru/06-conclusion.asciidoc +++ b/introduction/ru/06-conclusion.asciidoc @@ -3,7 +3,7 @@ В этом обучении мы получили вводную информацию по InnerSource. InnerSource применяет лучшие практики и принципы из мира open source к внутренней разработке. Подход даёт возможность командам получить необходимый функционал в соседних командах, неспособных выполнить запрос на доработку. -Успешный InnerSource включает в себя работу https://innersourcecommons.org/resources/learningpath/product-owner/index[_Владельца продукта_] и https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] из *хост-команды* и https://innersourcecommons.org/resources/learningpath/contributor/index[_Контрибьютера_] из *гостевой команды*. +Успешный InnerSource включает в себя работу https://innersourcecommons.org/learn/learning-path/product-owner/01[_Владельца продукта_] и https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] из *хост-команды* и https://innersourcecommons.org/learn/learning-path/contributor/01[_Контрибьютера_] из *гостевой команды*. При эффективном использовании InnerSource даёт преимущества обеим командам. *Приоритетное менторство* и *Добровольная Контрибьюция Кода* – принципы, влияющие на эффективность InnerSource. diff --git a/introduction/zh/03-how-works-zh.asciidoc b/introduction/zh/03-how-works-zh.asciidoc index fc2e005d..20a2203e 100644 --- a/introduction/zh/03-how-works-zh.asciidoc +++ b/introduction/zh/03-how-works-zh.asciidoc @@ -4,7 +4,7 @@ 在这个例子中，我们称团队A为 _调用(Guest)_ 团队 ，称团队B为 _维护(Host)_ 团队 。 _协同（Guest）_ 和 _主导（Host）_ 这两个术语暗示了一种类似于在家里接待客人的情况。在这种情况下，大多数人都想成为一个好主人。为了迎接协同方的到来，他们确保所有的东西都保持整洁。来访者在门口受到欢迎并被邀请进来。他们可以使用家中公共区域的功能和公用设施。可能会有一些客人被要求遵守的家规。同样的，大多数客人也想表现出对家庭和主人的尊重。他们对房子里的东西很小心，在他们逗留期间遵守规则。只要他们有礼貌，他们就会希望收到新的访问邀请。这些围绕着家访的概念是一个隐喻，它是团队在一个主导向另一个协同贡献代码库时应该采取的态度和行为。 -让我们仔细看看InnerSource的流程机制是如何工作的。为了帮助解释，我们将列出调用团队和维护团队中的几个关键人物。首先， https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品所有者（Product Owner）_] 确定维护团队愿意接受哪些功能作为贡献。 https://innersourcecommons.org/resources/learningpath/zh/contributor/index[_贡献者（Contributor）_] 是调用团队中提交代码贡献以供主人团队评审的个人。 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_Trusted Committer_] 代表维护团队在提供一个成功的拉取请求所需的任何及时支持和指导。在小规模的基层工作中，一个人通常同时担任产品所有者和受信任提交者的角色。 +让我们仔细看看InnerSource的流程机制是如何工作的。为了帮助解释，我们将列出调用团队和维护团队中的几个关键人物。首先， https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品所有者（Product Owner）_] 确定维护团队愿意接受哪些功能作为贡献。 https://innersourcecommons.org/resources/learningpath/zh/contributor/index[_贡献者（Contributor）_] 是调用团队中提交代码贡献以供主人团队评审的个人。 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_Trusted Committer_] 代表维护团队在提供一个成功的拉取请求所需的任何及时支持和指导。在小规模的基层工作中，一个人通常同时担任产品所有者和受信任提交者的角色。 有了这些定义，下面是一个InnerSource的贡献的基本概要。 diff --git a/introduction/zh/06-conclusion-zh.asciidoc b/introduction/zh/06-conclusion-zh.asciidoc index 6a0ad51a..f1479b87 100644 --- a/introduction/zh/06-conclusion-zh.asciidoc +++ b/introduction/zh/06-conclusion-zh.asciidoc @@ -2,8 +2,8 @@ 在这个学习过程中，我们已经介绍了InnerSource。 InnerSource将开放源码的最佳实践和原则应用于内部软件开发。 当维护团队（Host Team）无法交付所需的特性请求时，它为使用者提供了一个额外的选项。 -成功的InnerSource包括来自 *维护团队* 的 https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品所有者（Product Owner）_] 产品所有者和 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_Trusted Committer_] ， -以及来自 *调用团队(Guest Team)* 的 https://innersourcecommons.org/resources/learningpath/contributor/index[_贡献者（Contributor）_] 。 +成功的InnerSource包括来自 *维护团队* 的 https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品所有者（Product Owner）_] 产品所有者和 https://innersourcecommons.org/resources/learningpath/trusted-committer/zh/index[_Trusted Committer_] ， +以及来自 *调用团队(Guest Team)* 的 https://innersourcecommons.org/learn/learning-path/contributor/01[_贡献者（Contributor）_] 。 如果处理有效，InnerSource将为参与团队带来很多好处。有效的InnerSource可以带来 *自愿代码贡献* 和 *优先指导* 。 虽然本培训包含了关于InnerSource的高级概述，但是在InnerSource真正为您的团队工作方面还有更多有用的细节。 diff --git a/product-owner/01-opening-article.asciidoc b/product-owner/01-opening-article.asciidoc index e4e148d6..be2d48fd 100644 --- a/product-owner/01-opening-article.asciidoc +++ b/product-owner/01-opening-article.asciidoc @@ -18,4 +18,4 @@ You can also get a copy of the booklet I wrote with O'Reilly there at http://inn Please watch the other videos first. See the links below. -It helps to be familiar with the Agile or Lean processes, and it's really important that you understand the roles of the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committers_] and the https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] before watching this video. Thank you. +It helps to be familiar with the Agile or Lean processes, and it's really important that you understand the roles of the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committers_] and the https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] before watching this video. Thank you. diff --git a/product-owner/03-major-benefits-are-built-into-the-innersource-process-article.asciidoc b/product-owner/03-major-benefits-are-built-into-the-innersource-process-article.asciidoc index 915e59ff..c6e09272 100644 --- a/product-owner/03-major-benefits-are-built-into-the-innersource-process-article.asciidoc +++ b/product-owner/03-major-benefits-are-built-into-the-innersource-process-article.asciidoc @@ -5,7 +5,7 @@ Let me step through a few of those from a manager's perspective. I'll talk about First of that is _open code_. What do I mean by open code? Basically, the fact that the code is visible by all of the company, and there's a process for other developers to be able to submit pull requests on other code bases and get them accepted. -To understand this more, please see the articles about https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committers_] and contributing agreements for more details. +To understand this more, please see the articles about https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committers_] and contributing agreements for more details. Open code for a manager also means no more waiting or escalating to get bugs fixed or features implemented on other teams' code bases. You can start to implement and plan more effectively. diff --git a/product-owner/04-new-roles-and-responsibilities-article.asciidoc b/product-owner/04-new-roles-and-responsibilities-article.asciidoc index c04aa052..47670557 100644 --- a/product-owner/04-new-roles-and-responsibilities-article.asciidoc +++ b/product-owner/04-new-roles-and-responsibilities-article.asciidoc @@ -1,16 +1,16 @@ == New Roles and Responsibilities Being an InnerSource leader comes with new roles and responsibilities. - One of the first one of those is supporting your TCs. TCs are the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committers_]. + One of the first one of those is supporting your TCs. TCs are the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committers_]. One of the first things that you're going to be doing is probably helping to choose who those new TCs are going to be and supporting them in their job. -If you want to know more about what the TC role looks like, please review the https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committer_] section. +If you want to know more about what the TC role looks like, please review the https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committer_] section. They are the gatekeepers to your code base. Typically, they are lead developers who are good at code reviews and have a deep understanding of the code base's architecture. They will need your support. They will also be key for you in regards to collaborating with other teams. They'll be your right-hand people in regards to estimations and integrations. Remember to support them. -They have some crazy new responsibilities and may need mentoring to help with those https://innersourcecommons.org/resources/learningpath/contributor/index[_contributing teams_]. +They have some crazy new responsibilities and may need mentoring to help with those https://innersourcecommons.org/learn/learning-path/contributor/01[_contributing teams_]. Developers are not often taught how to negotiate. I recommend the book https://www.amazon.com/Getting-Yes-Negotiating-Agreement-Without/dp/0143118757/[Getting to Yes], and for you to use it with them. @@ -27,9 +27,9 @@ So nowadays, you document it so that the guests know that hey, in the shower, th Thirdly, documentation time. At the beginning, you may have to sink a fair amount of your time in regards to the open documentation, and going beyond just your open roadmaps and other open processes. I'm also talking about things like UX and UI standards, API standards, or even testing requirements. -With that, of course, you're going to want to sync up with your https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committers_] as to what they need to feel safe in regards to some of their coding requirements. It'll be worth it, promise. +With that, of course, you're going to want to sync up with your https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committers_] as to what they need to feel safe in regards to some of their coding requirements. It'll be worth it, promise. -Once you start working with those other teams, and when you onboard new developers and get so much more done than you'd gotten previously, remember those https://innersourcecommons.org/resources/learningpath/contributor/index[_new developers_] - you can also get them to help you write some of this brand-new documentation. +Once you start working with those other teams, and when you onboard new developers and get so much more done than you'd gotten previously, remember those https://innersourcecommons.org/learn/learning-path/contributor/01[_new developers_] - you can also get them to help you write some of this brand-new documentation. If your tool is one of those bottlenecks and is really important to them, they may even offer to help you do a lot of the heavy lifting in regards to the standards, because they want to integrate in with your product. Lastly, internal marketing. diff --git a/product-owner/05-recap-takeaways-article.asciidoc b/product-owner/05-recap-takeaways-article.asciidoc index 576a0cb4..3e3e32a3 100644 --- a/product-owner/05-recap-takeaways-article.asciidoc +++ b/product-owner/05-recap-takeaways-article.asciidoc @@ -12,7 +12,7 @@ Also, you get to collaborate more with your peers to accomplish more with less, The open processes also means that you get more credit for your work than you were probably getting previously. By going through and publishing those planning processes, it also means that you can deal with less politics, because everything becomes so much more clear. -And lastly, you've got those new roles and responsibilities, such as supporting your new https://innersourcecommons.org/resources/learningpath/trusted-committer/index[_Trusted Committers_]. +And lastly, you've got those new roles and responsibilities, such as supporting your new https://innersourcecommons.org/learn/learning-path/trusted-committer/01[_Trusted Committers_]. They're really going to need your help. Also, working with those other product owners so that you can both get more of your work done in a faster time frame. Going to have to sink a lot of time in regards to the new documentation, but that's OK, because you're going to get more credit for it. diff --git a/trusted-committer/01-introduction.asciidoc b/trusted-committer/01-introduction.asciidoc index 4a06af43..bc9328b2 100644 --- a/trusted-committer/01-introduction.asciidoc +++ b/trusted-committer/01-introduction.asciidoc @@ -20,7 +20,7 @@ dimensions in the following sections. Before we go into the details of what a Trusted Committer actually does, let’s spend some time contrasting the Trusted Committer role with other roles in InnerSource at a high level of abstraction and explain why we think the name is both apt -and important. Let’s start with the https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributor_] role. A +and important. Let’s start with the https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributor_] role. A _Contributor_ — as the name implies—makes contributions to an InnerSource community. These contributions could be code or non-code artifacts, such as bug reports, feature requests, or documentation. @@ -40,13 +40,13 @@ responsibility to push code closer to production and are generally allowed to perform tasks that have a higher level of risk associated with them. -The https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_ (PO)] is the third role in InnerSource. Similar to +The https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_ (PO)] is the third role in InnerSource. Similar to agile processes, the PO is responsible for defining and prioritizing requirements and stories for the community to implement. The PO interacts often with the Trusted Committer, (e.g., in making sure that a requested or contributed feature actually belongs to the product). Especially in smaller, grassroots InnerSource communities, the Trusted Committer usually also -acts as a PO. Check out our https://innersourcecommons.org/resources/learningpath/product-owner/index[Product Owner Learning Path segment] +acts as a PO. Check out our https://innersourcecommons.org/learn/learning-path/product-owner/01[Product Owner Learning Path segment] for more detailed information. === Why Role Names Matter @@ -75,10 +75,10 @@ a quick look at the responsibilities of a Trusted Committer. Trusted Committers have various responsibilities, including: -* https://innersourcecommons.org/resources/learningpath/trusted-committer/02/[Ensuring product quality] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/03/[Keeping the community healthy] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[Reducing the barriers to making contributions] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/04/[Upleveling the community] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/06/[Advocating the community's needs] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/02/[Ensuring product quality] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/03/[Keeping the community healthy] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[Reducing the barriers to making contributions] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/04/[Upleveling the community] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/06/[Advocating the community's needs] -We will look at these responsibilities in more depth in the following pages and also explore the path of https://innersourcecommons.org/resources/learningpath/trusted-committer/07/[becoming a Trusted Committer] at the end of this article. +We will look at these responsibilities in more depth in the following pages and also explore the path of https://innersourcecommons.org/learn/learning-path/trusted-committer/07/[becoming a Trusted Committer] at the end of this article. diff --git a/trusted-committer/02-ensuring-product-quality.asciidoc b/trusted-committer/02-ensuring-product-quality.asciidoc index 397da499..3ce7fcf8 100644 --- a/trusted-committer/02-ensuring-product-quality.asciidoc +++ b/trusted-committer/02-ensuring-product-quality.asciidoc @@ -12,7 +12,7 @@ tech-related decisions themselves or do all the work to implement them. It is the Trusted Committer's job to communicate and clarify quality standards in their community and to formulate them in a way that is understandable and -actionable by their https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_]. This includes written documentation, +actionable by their https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_]. This includes written documentation, of course, but the most effective way for Trusted Committers to communicate these quality standards is by example. We think it can be a worthwhile goal for an InnerSource community to try and distinguish itself from traditional software development projects not @@ -26,7 +26,7 @@ performed as part of pull requests (PRs), is most frequently used to ensure qual and participate in pull requests by pointing out necessary improvements, it is usually only the Trusted Committer who can ultimately accept and merge or reject a contribution. This is what we meant earlier when we said "Trusted Committers can push code -closer to production." Trusted Committers should also help https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] during +closer to production." Trusted Committers should also help https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] during a PR to get their contributions over the finish line. That said, it is ultimately the contributor's job to make that happen. @@ -34,14 +34,14 @@ The job of a Trusted Committer is not to accept all contributions by default, bu only accept those that meet the defined criteria in terms of quality and scope. And Trusted Committers should avoid rewriting a contributor's code to make it "fit" as much as possible, even if it means spending more time -supporting https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] in a PR. Trusted Committers +supporting https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] in a PR. Trusted Committers take a long-term perspective and understand that this kind of support is an investment in the longevity of the community, and it will increase the community's development speed in the long run. Sometimes project requirements or limitations are not known upfront and are instead discovered during development. Trusted Committers are also responsible for making sure -these findings are captured and documented for both the https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owners_] and the -https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_]. +these findings are captured and documented for both the https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owners_] and the +https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_]. But the Trusted Committer's purview with respect to quality goes beyond pull requests. Trusted Committers think about quality on a strategic level and ensure the @@ -56,10 +56,10 @@ The effectiveness of the Trusted Committer is strongly related to code health. Absent the latter, Trusted Committers will have to spend much of their valuable time validating and documenting workarounds for bugs or a fragile architecture and will not have enough time to spend on onboarding and -mentoring https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_]. +mentoring https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_]. In conclusion, ensuring product quality is a key responsibility of Trusted Committers. They set quality standards and lead by example. They participate in pull -requests and help https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] meet +requests and help https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] meet quality standards. They also take responsibility for the long-term health of the software. diff --git a/trusted-committer/03-keeping-the-community-healthy.asciidoc b/trusted-committer/03-keeping-the-community-healthy.asciidoc index 6c8e0cc0..364ba0ec 100644 --- a/trusted-committer/03-keeping-the-community-healthy.asciidoc +++ b/trusted-committer/03-keeping-the-community-healthy.asciidoc @@ -7,10 +7,10 @@ strive to keep the community building the software healthy as well. Because of that, they must strike a good balance between ensuring product quality and growing a healthy community. What does a healthy community look like? Quite simply, in a healthy community, -https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] tend to stick around, can spend most of their time developing software, and are able to level up their abilities. +https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] tend to stick around, can spend most of their time developing software, and are able to level up their abilities. As a result, a healthy community will be continually growing. -Why do https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] join and stick around in a community? Some do because they +Why do https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] join and stick around in a community? Some do because they subscribe to the purpose or the mission of the community. It is the Trusted Committer's job to clearly articulate and promote this purpose. The importance of this is often not recognized, but marketing a community and its products is truly essential. @@ -44,13 +44,13 @@ development projects. We believe that Trusted Committers should prioritize onboarding and mentoring during pull requests over reaching communicated release dates, unless there is a very good reason not to. Good mentoring during pull requests leads to a higher level -of trust and engagement by https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_], which in turn leads -to more contributions. We’ll discuss this more in https://innersourcecommons.org/resources/learningpath/trusted-committer/04/["Upleveling the Community"]. +of trust and engagement by https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_], which in turn leads +to more contributions. We’ll discuss this more in https://innersourcecommons.org/learn/learning-path/trusted-committer/04/["Upleveling the Community"]. Finally, some people stick around in InnerSource communities because they get to focus on developing software instead of activities considered overhead or waste, especially common in large companies with a strong focus on processes. The Trusted Committer's job in this context is to -ensure that https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] can actually focus on their projects by +ensure that https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] can actually focus on their projects by communicating and enacting helpful contribution guidelines. One important aspect of these guidelines is to explain what we call _signaling_ in @@ -65,10 +65,10 @@ them as a community as much as possible. For Trusted Committers to be able to fulfill all these responsibilities, it is important that they communicate regularly with community members and keep an ear to the ground. We'll -go into more detail about this in the section in https://innersourcecommons.org/resources/learningpath/trusted-committer/06/["Advocating the Community's +go into more detail about this in the section in https://innersourcecommons.org/learn/learning-path/trusted-committer/06/["Advocating the Community's Needs"]. In summary, Trusted Committers should strive to create a welcoming and appreciative -environment for their https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] that allows them to concentrate on writing +environment for their https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] that allows them to concentrate on writing software and growing personally by creating opportunities to learn from other community members. diff --git a/trusted-committer/04-uplevelling-community-members.asciidoc b/trusted-committer/04-uplevelling-community-members.asciidoc index 9c00e1fd..16190fcf 100644 --- a/trusted-committer/04-uplevelling-community-members.asciidoc +++ b/trusted-committer/04-uplevelling-community-members.asciidoc @@ -3,7 +3,7 @@ == Upleveling Community Members There is a continuum of participation in an InnerSource community. -There are people who are not aware of the community. _Newcomers_ might be interested in the community and its product, but have not yet used it. _Consumers_ use the software but may not have made a contribution. Then there are the https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] who have made at least one contribution, and finally the _Trusted Committers_, who are taking responsibility for both the software and the community. +There are people who are not aware of the community. _Newcomers_ might be interested in the community and its product, but have not yet used it. _Consumers_ use the software but may not have made a contribution. Then there are the https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] who have made at least one contribution, and finally the _Trusted Committers_, who are taking responsibility for both the software and the community. As a Trusted Committer, you are responsible for moving individuals along this continuum and upleveling their ability to make contributions. In this sense, Trusted Committers act as force multipliers in their community. @@ -12,27 +12,27 @@ It is important for Trusted Committers to market their product and communities to increase the number of newcomers and consumers. They should also communicate opportunities to make contributions to consumers and try to elicit and align the -interests of potential https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] with that of the community. What -often works well is if https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] are able to work on something that +interests of potential https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] with that of the community. What +often works well is if https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] are able to work on something that benefits their department or role in the company. Development tools and automation are good examples. -Finally, it is the Trusted Committer's responsibility to identify and support https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] with the potential to grow +Finally, it is the Trusted Committer's responsibility to identify and support https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] with the potential to grow by encouraging them to tackle challenging tasks and mentor them towards completion. This is, in our opinion, a Trusted Committer's noblest responsibility, and it is rewarding for both Trusted Committer and contributor. We've heard Trusted Committers say that mentoring and seeing people level up their abilities more than makes up for the fact that they have less time to actually spend writing software. -As mentioned in the https://innersourcecommons.org/resources/learningpath/trusted-committer/03/[previous section], learning and personal growth are +As mentioned in the https://innersourcecommons.org/learn/learning-path/trusted-committer/03/[previous section], learning and personal growth are reasons people join and stick around in an InnerSource community. -Upleveling their https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] is one of the most powerful tools Trusted Committers have +Upleveling their https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] is one of the most powerful tools Trusted Committers have at their disposal to increase the speed, output and longevity of their communities. It is also one of the key arguments with which to convince management to allow their employees to participate in an InnerSource community, as that will make their employees more valuable to the company overall and help them retain top talent. -In summary, Trusted Committers need to attract new https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] and level up their +In summary, Trusted Committers need to attract new https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] and level up their ability to make contributions. This activity ultimately levels up the community’s ability to create better software faster. They do so by communicating opportunities to make contributions and by helping and diff --git a/trusted-committer/05-lowering-the-barriers-to-entry.asciidoc b/trusted-committer/05-lowering-the-barriers-to-entry.asciidoc index 940a47b1..39a4beb2 100644 --- a/trusted-committer/05-lowering-the-barriers-to-entry.asciidoc +++ b/trusted-committer/05-lowering-the-barriers-to-entry.asciidoc @@ -2,14 +2,14 @@ Soliciting contributions in an InnerSource community is more challenging than it is in an Open Source community for a number of reasons: -* The sheer number of potential https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] is lower in InnerSource communities. +* The sheer number of potential https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] is lower in InnerSource communities. * Contributors will want to contribute during their work time, which means they are more time constrained. * Work in InnerSource might not necessarily be part of Contributors' official performance goals, so time spent working on InnerSource may seem to detract from achieving those goals. That's why it's important for Trusted Committers to make the processes for making -contributions and onboarding https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] as frictionless as +contributions and onboarding https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] as frictionless as possible. There are a number of things that can help: * Have a good README.md in each code repository. A good README.md @@ -18,7 +18,7 @@ addition, it should provide detailed instructions on how to get, build, test, and use the software in the repository, including information about the license. * Have a good CONTRIBUTING.md that outlines what is expected of the -https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributor_]. It should answer +https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributor_]. It should answer common questions, such as: ** How do I submit a bug report or feature request? ** Who and how do I contact if I have questions? @@ -37,19 +37,19 @@ obligations in layman’s terms. In addition to these documentary tasks, similar to Open Source software development it should be easy and straightforward to run and test the software -being developed locally by potential https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_], so they can start implementing and validating their contribution with as little effort as +being developed locally by potential https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_], so they can start implementing and validating their contribution with as little effort as possible. There are two common models for making contributions: _shared repository_ and _fork and join_. Both have advantages, and as a Trusted Committer, you want to support both models to accommodate different needs of your -potential and current https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_]. +potential and current https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_]. Your Contributors will often have questions about the contribution process or about the community itself, and someone has to be available to answer these questions. It is therefore important for any InnerSource community to have one or more contact persons that are available for answering such questions. Someone from the group of Trusted Committers is usually that contact person, or else they need to make sure there is a community member "on call". -It is also important to help potential https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] determine what +It is also important to help potential https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] determine what contributions are needed. These can be code contributions but also noncode contributions, such as writing documentation, creating artwork, or organizing events. One common way to do this is to tag diff --git a/trusted-committer/06-advocating-for-the-communitys-needs.asciidoc b/trusted-committer/06-advocating-for-the-communitys-needs.asciidoc index bbe296f6..55e7a1f3 100644 --- a/trusted-committer/06-advocating-for-the-communitys-needs.asciidoc +++ b/trusted-committer/06-advocating-for-the-communitys-needs.asciidoc @@ -15,7 +15,7 @@ Trusted Committers build trust with the organization and, building on that trust They are responsible for communicating technical, as well as community-related, risks to management. At the same time, Trusted Committers need to be strategic and work within the degrees of freedom afforded by their companies. -Trusted Committers also need to make sure that the community and individual https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[contributors] get public credit for their work. +Trusted Committers also need to make sure that the community and individual https://innersourcecommons.org/learn/learning-path/contributor/01[contributors] get public credit for their work. Public credit is the currency with which contributors are being paid, especially those who contribute voluntarily. It is a good practice to commend valuable contributors publicly and to make sure their managers are aware of their contributions. Neglecting to give credit can be frustrating for individual contributors and detrimental to the health of the community. @@ -23,10 +23,10 @@ This can happen in companies not yet accustomed to the InnerSource working model A good Trusted Committer will engage with management and advocate for public credit. Failure to give credit is almost never done in bad faith and is easy to fix. -Another common case calling for the Trusted Committer’s advocacy is when https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[contributors] are not given time or permission to contribute. +Another common case calling for the Trusted Committer’s advocacy is when https://innersourcecommons.org/learn/learning-path/contributor/01[contributors] are not given time or permission to contribute. This can happen when the community is working on a product outside of the contributor's department and thus not relevant for their manager’s goals. In this case, the Trusted Committer should engage in discussion with the contributor’s manager and lobby for an alternative decision. -In summary, there are many situations in which Trusted Committers need to advocate for the interests of individual https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[contributors] and for the community as a whole. +In summary, there are many situations in which Trusted Committers need to advocate for the interests of individual https://innersourcecommons.org/learn/learning-path/contributor/01[contributors] and for the community as a whole. Trusted Committers understand that the value the community can provide to the organization depends on the health and longevity of the community and ultimately on a trustworthy relationship between both. diff --git a/trusted-committer/07-becoming-a-trusted-committer.asciidoc b/trusted-committer/07-becoming-a-trusted-committer.asciidoc index 458ef0dc..b2999cbb 100644 --- a/trusted-committer/07-becoming-a-trusted-committer.asciidoc +++ b/trusted-committer/07-becoming-a-trusted-committer.asciidoc @@ -11,10 +11,10 @@ Transparency, another Open Source value, also plays a vital role in that it make The process of officially becoming a Trusted Committer differs from community to community, depends on where you are in your InnerSource journey and might evolve over time. In grassroots communities, the founders often assume the role of the Trusted Committer. -As a community grows, or in larger communities, Trusted Committers are usually nominated or voted in from the community https://innersourcecommons.org/resources/learningpath/contributor/index[contributors]. +As a community grows, or in larger communities, Trusted Committers are usually nominated or voted in from the community https://innersourcecommons.org/learn/learning-path/contributor/01[contributors]. But the Trusted Committer role should be taken on voluntarily as it requires an immense amount of time and dedication to be successful in it. -What are the criteria to apply in nominating https://innersourcecommons.org/resources/learningpath/contributor/index[contributors] for a Trusted Committer role? +What are the criteria to apply in nominating https://innersourcecommons.org/learn/learning-path/contributor/01[contributors] for a Trusted Committer role? What does it take to successfully fill the role of a Trusted Committer? First off, potential Trusted Committers need to have demonstrated a deep technical competence during their work in the community. In addition to that, they must have proven their ability to effectively communicate with peers in the community and ideally also with diff --git a/trusted-committer/de/01-introduction-de.asciidoc b/trusted-committer/de/01-introduction-de.asciidoc index e92b8df8..5fba77ce 100644 --- a/trusted-committer/de/01-introduction-de.asciidoc +++ b/trusted-committer/de/01-introduction-de.asciidoc @@ -14,7 +14,7 @@ Wir werden uns die beiden Dimensionen in den folgenden Abschnitten genauer ansch Bevor wir aber in die Details gehen, was die eigentliche Aufgabe eines _Trusted Committers_ ist, wollen wir uns zunächst auf höherer Abtraktionsebene anschauen, wie sich die Rolle des _Trusted Committers_ von den anderen Rollen in der _InnerSource_ unterscheidet und dabei erklären, warum wir glauben, dass die -Bezeichnung sowohl passend als auch wichtig ist. Lasst uns beginnen mit der Rolle des https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_]. Ein +Bezeichnung sowohl passend als auch wichtig ist. Lasst uns beginnen mit der Rolle des https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_]. Ein _Contributor_ — wie schon der Name nahelegt — liefert Beiträge zu einer _InnerSource_-Organisationseinheit. Diese Beiträge können entweder _code_ oder andere Artefakte wie z.B. Fehlerreports, Änderungsanforderungen oder Dokumentation sein. @@ -27,11 +27,11 @@ _Trusted Committer_ sowohl für den Bau eines Hauses als auch für die Hausordnu miteinander arbeiten können. Verglichen mit den _Contributors_ haben _Trusted Committers_ sich die Verantwortlichkeit verdient, näher am produktiven Code zu arbeiten und sind grundsätzlich befugt, Aufgaben auszuführen, die mit einem höheren Riskio verbunden sind. -Der https://innersourcecommons.org/resources/learningpath/product-owner/index[_Product Owner_ (PO)] ist die dritte +Der https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owner_ (PO)] ist die dritte Rolle bei _InnerSource_. Ähnlich wie bei agilen Prozessen ist der _PO_ verantwortlich für die Definition und Priorisierung von Anforderungen und User Stories, welche die jeweilige Organisationseinheit umsetzen soll. Der _PO_ arbeitet eng mit dem _Trusted Committer_ zusammen, z.B. um sicherzustellen, dass ein angefordertes oder bereitgestelltes Feature tatsächlich Bestandteil des Produkts sein soll. Speziell in kleineren _InnerSource_-Organisationen kann der _Trusted Committer_ meistens auch die Aufgaben des -PO wahrnehmen. Schau Dir für weiterführende Informationen unser https://innersourcecommons.org/resources/learningpath/product-owner/index[Product Owner Learning Path segment] +PO wahrnehmen. Schau Dir für weiterführende Informationen unser https://innersourcecommons.org/learn/learning-path/product-owner/01[Product Owner Learning Path segment] an. === Warum Rollennamen von Bedeutung sind @@ -57,11 +57,11 @@ kurzen Blick auf die Verantwortlichkeiten eines _Trusted Committers_ werfen. _Trusted Committers_ haben verschiedene Verantwortlichkeiten, unter anderem: -* https://innersourcecommons.org/resources/learningpath/trusted-committer/02/[Ensuring product quality] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/03/[Keeping the community healthy] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[Reducing the barriers to making contributions] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/04/[Upleveling the community] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/06/[Advocating the community's needs] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/02/[Ensuring product quality] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/03/[Keeping the community healthy] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[Reducing the barriers to making contributions] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/04/[Upleveling the community] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/06/[Advocating the community's needs] -Wir werden diese Verantwortlichkeiten in den folgenden Kapiteln weiter vertiefen, bitte schau Dir dazu auch das Kapitel https://innersourcecommons.org/resources/learningpath/trusted-committer/07/[07 becoming a Trusted Committer] am Ende an. +Wir werden diese Verantwortlichkeiten in den folgenden Kapiteln weiter vertiefen, bitte schau Dir dazu auch das Kapitel https://innersourcecommons.org/learn/learning-path/trusted-committer/07/[07 becoming a Trusted Committer] am Ende an. [role="pagenumrestart"] diff --git a/trusted-committer/de/02-ensuring-product-quality-de.asciidoc b/trusted-committer/de/02-ensuring-product-quality-de.asciidoc index 6e2cfddd..17e270fa 100644 --- a/trusted-committer/de/02-ensuring-product-quality-de.asciidoc +++ b/trusted-committer/de/02-ensuring-product-quality-de.asciidoc @@ -4,7 +4,7 @@ Lasst uns mit der wohl am häufigsten mit der Rolle des _Trusted Committers_ in In einer _InnerSource-Community_ sind die _Trusted Committer_ verantwortlich für alle technologisch basierten Entscheidungen, speziell diejenigen, die Einfluss auf die Produktqualität haben. Ownership bedeutet hier, sicherzustellen, dass getroffene Entscheidungen umgesetzt werden. Das schließt die Kommunikation dieser Entscheidungen und - falls notwendig - deren wirksame Vertretung innerhalb und außerhalb der _Community_ mit ein. Das bedeutet aber nicht, dass alle technischen Entscheidungen von den _Trusted Committer_ getroffen werden müssen, noch dass diese die komplette Implementierungsarbeit erledigen. -Die Aufgabe eines _Trusted Committer_ ist es, die Qualitätsstandards innerhalb ihrer _Community_ zu kommunizieren und zu erläutern, vor allem sie so zu formulieren, dass sie für ihre https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[_Contributors_] verständlich und anwendbar sind. +Die Aufgabe eines _Trusted Committer_ ist es, die Qualitätsstandards innerhalb ihrer _Community_ zu kommunizieren und zu erläutern, vor allem sie so zu formulieren, dass sie für ihre https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] verständlich und anwendbar sind. Dies beinhaltet natürlich auch die schriftliche Dokumentation, dies ist für eine _InnerSource-Community_ der effektivste Weg diese Standards vorzuleben und Beispiele zu geben. Wir glauben, dass es ein erstrebenswertes Ziel für eine _InnerSource-Community_ sein sollte, sich nicht nur in der Arbeitsorganisation von klassischen Entwicklungsprojekten zu unterscheiden, sondern auch in der Qualität der Software, die sie entwickelt. @@ -15,22 +15,22 @@ _Trusted Committer_ stellen außerdem sicher, das in der _Community_ die notwend Zur Sicherstellung der Qualität wird am häufigsten das _Peer Review_ genutzt, welches normalerweise Bestandteil der Pull Requests (PR's) ist. Während für gewöhnlich jedermann Pull Requests starten und daran teilnehmen kann indem er auf notwendige Verbesserungen hinweist, ist es normalerweise nur dem _Trusted Committer_ möglich Beiträge zu akzeptieren oder abzulehnen. Das ist es, was wir an anderer Stelle damit gemeint haben, wenn wir davon sprachen, dass "_Trusted Committer_ Code in Produktion bringen können". -_Trusted Committer_ sollten den https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[_Contributors_] auch während eines PR's helfen ihre Beiträge fertig zu stellen. +_Trusted Committer_ sollten den https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] auch während eines PR's helfen ihre Beiträge fertig zu stellen. Dennoch ist es letztendlich die Aufgabe des _Contributors_, dies zu erreichen. Es ist nicht Aufgabe eines _Trusted Committer_, alle Beiträge grundsätzlich zu akzeptieren, sondern nur diejenigen, die die definierten Kriterien bezüglich Qualität, Umfang und Projektausrichtung erfüllen. -_Trusted Committer_ sollten vermeiden, den Code eines _Contributors_ selbst umzuschreiben, um ihn passend zu machen, selbst wenn dadurch ein höherer Aufwand bei der Unterstützung des https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[_Contributors_] bei einem PR anfällt. _Trusted Committer_ nehmen eine längerfristige Perspektive ein und verstehen, dass diese Art der Unterstützung eine Investition in die Langlebigkeit der _Community_ darstellt und dies langfristig die Entwicklungsgeschwindigkeit der _Community_ erhöht. +_Trusted Committer_ sollten vermeiden, den Code eines _Contributors_ selbst umzuschreiben, um ihn passend zu machen, selbst wenn dadurch ein höherer Aufwand bei der Unterstützung des https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] bei einem PR anfällt. _Trusted Committer_ nehmen eine längerfristige Perspektive ein und verstehen, dass diese Art der Unterstützung eine Investition in die Langlebigkeit der _Community_ darstellt und dies langfristig die Entwicklungsgeschwindigkeit der _Community_ erhöht. Manchmal sind Anforderungen und Einschränkungen des Projekts nicht von vorne herein bekannt, sondern werden erst während der Entwicklung erkannt. -_Trusted Committer_ sind auch dafür verantwortlich, dass diese Ergebnisse erfasst und dokumentiert werden, so dass diese sowohl den https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/product-owner/01-opening-article.asciidoc[_Product Owners_] als auch den https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[_Contributors_] zugänglich sind. +_Trusted Committer_ sind auch dafür verantwortlich, dass diese Ergebnisse erfasst und dokumentiert werden, so dass diese sowohl den https://innersourcecommons.org/learn/learning-path/product-owner/01[_Product Owners_] als auch den https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] zugänglich sind. Der Aufgabenbereich des _Trusted Committer_ in Bezug auf Qualität geht über Pull Requests hinaus. _Trusted Committer_ betrachten Qualität als strategische Komponente und stellen die Langlebigkeit der zu erstellenden Software sicher. Dies beinhaltet codeorientierte Verantwortlichkeiten im Sinne von Verständlichkeit des Quellcodes bis hin zur Wahrung der konzeptionellen Integrität der gesamten Software. Dazu gehören auch managementorientierte Aufgaben wie zum Beispiel sicherzustellen, dass die _Community_ genügend Zeit für Refaktorierung der Software hat, oder wenn nötig, die Verschiebung von Releaseterminen zugunsten der Verbesserung der Softwarequalität zu veranlassen. Die Effektivität des _Trusted Committers_ hängt stark von der Wartbarkeit des Codes ab. -Fehlt letzteres, müssen die _Trusted Committer_ viel ihrer wertvollen Zeit investieren um Workarounds für Fehler oder anfällige Architektur zu validieren und zu dokumentieren. Dadurch haben sie nicht ausreichend Zeit, um https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[_Contributors_] mit Onboarding und Mentoring zu unterstützen. +Fehlt letzteres, müssen die _Trusted Committer_ viel ihrer wertvollen Zeit investieren um Workarounds für Fehler oder anfällige Architektur zu validieren und zu dokumentieren. Dadurch haben sie nicht ausreichend Zeit, um https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] mit Onboarding und Mentoring zu unterstützen. Zusammengefasst ist das Sicherstellen der Produktqualität eine Schlüsselverantwortung der _Trusted Committer_. -Sie bestimmen die Qualitätsstandards und gehen mit gutem Vorbild voran. Sie unterstützen bei Pull Requests und helfen den https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[_Contributors_] die Qualitätsstandards zu erfüllen. +Sie bestimmen die Qualitätsstandards und gehen mit gutem Vorbild voran. Sie unterstützen bei Pull Requests und helfen den https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] die Qualitätsstandards zu erfüllen. Weiterhin übernehmen sie auch die Verantwortung für die langfristige Wartbarkeit und Qualität der Software. diff --git a/trusted-committer/de/03-keeping-the-community-healthy-de.asciidoc b/trusted-committer/de/03-keeping-the-community-healthy-de.asciidoc index 22763f99..15e173af 100644 --- a/trusted-committer/de/03-keeping-the-community-healthy-de.asciidoc +++ b/trusted-committer/de/03-keeping-the-community-healthy-de.asciidoc @@ -3,10 +3,10 @@ In der Einführung wurde darauf hingewiesen, dass _Trusted Committer_ sowohl technikorientierte als auch organisationsorientierte Verantwortlichkeiten haben. Es ist nicht ausreichend, sich nur auf den _Code_ und den Zustand des _Codes_ zu konzentrieren. Um auf lange Sicht erfolgreich zu sein, sollten _Trusted Committer_ auch danach streben, die Community, die die Software erstellt, gesund zu erhalten. Deshalb müssen sie sich um eine gute Balance zwischen dem Sicherstellen der Produktqualität und dem Wachstum der eigenen Community bemühen. -Was macht eine gute Community aus? Sehr einfach, eine gute Community motiviert die https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] dazu dabeizubleiben, sie können den Großteil ihrer Zeit für die Entwicklung der Software einsetzen, und sind in der Lage, ihre Fähigkeiten zu verbessern. +Was macht eine gute Community aus? Sehr einfach, eine gute Community motiviert die https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] dazu dabeizubleiben, sie können den Großteil ihrer Zeit für die Entwicklung der Software einsetzen, und sind in der Lage, ihre Fähigkeiten zu verbessern. Infolgedessen wird eine gute Community kontinuierlich wachsen. -Warum schließen sich https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] einer Community an und bleiben dabei? Einige tun dies, weil sie sich mit dem Zweck der Community identifizieren können. +Warum schließen sich https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] einer Community an und bleiben dabei? Einige tun dies, weil sie sich mit dem Zweck der Community identifizieren können. Es ist die Aufgabe der _Trusted Committer_, diesen Zweck klar zu formulieren und fördern. Dessen Bedeutung wird oft nicht erkannt, aber Marketing für die Community und ihrer Produkte ist tatsächlich entscheidend. Ein weiterer, offensichtlicher Grund für eine Person dabeizubleiben ist die Zusammenarbeit mit anderen Community Mitgliedern. @@ -23,12 +23,12 @@ _Trusted Committer_ sind oft Mentoren für jüngere Entwickler, und verwenden Ze Sie liefern die Theorie oder die Erfahrung bei Quellcodeänderungen und schlagen Möglichkeiten, wie Änderungen am besten implementiert werden können, vor. Dadurch können _Trusted Committer_ die Lerngeschwindigkeit ihrer Community weit über die traditioneller Software-Entwicklung erhöhen. Wir glauben, dass _Trusted Committer_ das Onboarding und Mentoring während der Pull Requests über das Erreichen von Releaseterminen stellen sollten, außer es sprechen triftige Gründe dagegen. -Gute Betreuung während eines Pull Requests führt zu höherem Vertrauen und Bindung von https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_], was im Gegenzug zu mehr Mitarbeit führt. -Wir werden diesen Aspekt in https://innersourcecommons.org/resources/learningpath/trusted-committer/04/["Upleveling the Community"] näher betrachten. +Gute Betreuung während eines Pull Requests führt zu höherem Vertrauen und Bindung von https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_], was im Gegenzug zu mehr Mitarbeit führt. +Wir werden diesen Aspekt in https://innersourcecommons.org/learn/learning-path/trusted-committer/04/["Upleveling the Community"] näher betrachten. Schliesslich gibt es Menschen, die sich in _InnerSource Communities_ engagieren, weil sie sich dort auf das Entwickeln von Software konzentrieren können anstatt anderen Aufgaben nachzugehen, die häufig als überflüssig oder unnötig angesehen werden. Dies trifft häufig auf große Unternehmen mit einem starken Fokus auf Prozesse zu. -Die Aufgabe der _Trusted Committer_ in diesem Zusammenhang ist es, sicherzustellen dass die https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] sich auf ihre Projekte konzentrieren können, indem sie sinnvolle Contribution Guidelines kommunizieren und einsetzen. +Die Aufgabe der _Trusted Committer_ in diesem Zusammenhang ist es, sicherzustellen dass die https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] sich auf ihre Projekte konzentrieren können, indem sie sinnvolle Contribution Guidelines kommunizieren und einsetzen. Ein wichtiger Aspekt dieser Guidelines ist, was wir in Pull Requests _signaling_ nennen: Wie soll ein Kommentar aussehen? Was bedeutet es, wenn ich einen Kommentar "_like_" oder "_+1_" vergebe? Wie unterscheidet sich beim _@mentioning_ die Verwendung eines _/CC_-Vorzeichens von einem _/FYI_-Vorzeichen? @@ -36,6 +36,6 @@ Allgemein gesprochen müssen _Trusted Committer_ sicherstellen, dass der Prozess Schließlich sollten _Trusted Committer_ ihre Community dazu befähigen, prozessbezogene Probleme zu finden und diese so gut wie möglich selbst anzupassen und zu verbessern. Damit _Trusted Committer_ alle diese Verantwortlichkeiten erfüllen können, ist es wichtig, dass sie regelmäßig mit den Mitgliedern der Community kommunizieren und ein Gespür für die allgemeine Stimmung entwickeln. -Wir werden dies näher im Kapitel https://innersourcecommons.org/resources/learningpath/trusted-committer/06/["Advocating the Community's Needs"] betrachten. +Wir werden dies näher im Kapitel https://innersourcecommons.org/learn/learning-path/trusted-committer/06/["Advocating the Community's Needs"] betrachten. -Zusammengefasst sollten _Trusted Committer_ sich bemühen ein einladendes und annerkennendes Umfeld für ihre https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] zu erzeugen, welches diesen erlaubt, sich auf das Schreiben von Software zu konzentrieren und ihre Persönlichkeit weiterzuentwickeln indem sie von anderen Mitgliedern der Organisation lernen. +Zusammengefasst sollten _Trusted Committer_ sich bemühen ein einladendes und annerkennendes Umfeld für ihre https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] zu erzeugen, welches diesen erlaubt, sich auf das Schreiben von Software zu konzentrieren und ihre Persönlichkeit weiterzuentwickeln indem sie von anderen Mitgliedern der Organisation lernen. diff --git a/trusted-committer/de/04-uplevelling-community-members.asciidoc b/trusted-committer/de/04-uplevelling-community-members.asciidoc index a2441e06..e977939b 100644 --- a/trusted-committer/de/04-uplevelling-community-members.asciidoc +++ b/trusted-committer/de/04-uplevelling-community-members.asciidoc @@ -3,21 +3,21 @@ == Weiterbildung von Community Mitgliedern Es gibt ein Kontinuum bei der Teilnahme an einer InnerSource Community. Es gibt Menschen, denen die Community nicht bekannt ist. Neulinge könnten sich für die Community und deren Produkt interessieren, haben aber bisher noch nicht damit gearbeitet. _Consumer_ nutzen die Software, haben aber bisher noch nicht selbst dazu beigetragen. -Dann gibt es die https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_], die schon mindestens einen Beitrag geleistet haben, und schließlich die _Trusted Committer_, welche Verantwortung sowohl für die Software als auch die Community übernehmen. +Dann gibt es die https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_], die schon mindestens einen Beitrag geleistet haben, und schließlich die _Trusted Committer_, welche Verantwortung sowohl für die Software als auch die Community übernehmen. Als _Trusted Committer_ bist du verantwortlich, Individuen zu helfen sich innerhalb dieses Kontinuums weiterzuentwickeln und ihre Fähigkeiten zu verbessern, Beiträge zu liefern. In diesem Sinne agieren _Trusted Committer_ als Multiplikatoren in ihrer Community. Es ist wichtig für _Trusted Committer_ ihr Produkt und ihre Community zu vermarkten, um weitere Neueinsteiger und _Consumer_ der Community zu werben. -Sie sollten also Gelegentheiten kommunizieren, eigene Beiträge für _Consumer_ zu erstellen und versuchen, die Interessen von möglichen https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] zu ermitteln und mit denen der Community in Einklang zu bringen. -Als gute Praxis hat sich dabei bewährt, wenn https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] an etwas arbeiten können, was ihnen bei ihrer täglichen Arbeit oder ihrer Rolle im Unternehmen hilft. Gute Beispiele dafür sind Entwicklungswerkzeuge oder die Automatisierung von Abläufen. +Sie sollten also Gelegentheiten kommunizieren, eigene Beiträge für _Consumer_ zu erstellen und versuchen, die Interessen von möglichen https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] zu ermitteln und mit denen der Community in Einklang zu bringen. +Als gute Praxis hat sich dabei bewährt, wenn https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] an etwas arbeiten können, was ihnen bei ihrer täglichen Arbeit oder ihrer Rolle im Unternehmen hilft. Gute Beispiele dafür sind Entwicklungswerkzeuge oder die Automatisierung von Abläufen. -Letztendlich sind die _Trusted Committers_ dafür verantwortlich, https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] mit dem Potential zu wachsen zu indentifizieren und zu unterstützen, indem sie sie ermutigen, herausfordernde Aufgaben zu übernehmen und sie dabei bis ins Ziel unterstützen. +Letztendlich sind die _Trusted Committers_ dafür verantwortlich, https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] mit dem Potential zu wachsen zu indentifizieren und zu unterstützen, indem sie sie ermutigen, herausfordernde Aufgaben zu übernehmen und sie dabei bis ins Ziel unterstützen. Dies ist unserer Meinung nach die edelste Aufgabe eines _Trusted Committers_, und diese Aufgabe lohnt sich sowohl für den _Trusted Committer_ als auch für den _Contributor_. _Trusted Committer_ berichten, dass Mentoring und zu sehen, wie Menschen lernen und zur Community beitragen, mehr als genug Ersatz dafür ist, dass die _Trusted Committer_ weniger Zeit haben, selbst Software zu schreiben. -Wie in https://innersourcecommons.org/resources/learningpath/trusted-committer/03/[previous section] erwähnt, sind Lernen und persönliches Wachstum wesentliche Gründe für Menschen, einer InnerSoure Community beizutreten und dabei zu bleiben. -Die Weiterbildung ihrer https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] ist eines der stärksten Werkzeuge, welches _Trusted Committer_ zur Verfügung haben, um die Geschwindigkeit, den Output und die Langlebigkeit ihrer Communitiy zu erhöhen. +Wie in https://innersourcecommons.org/learn/learning-path/trusted-committer/03/[previous section] erwähnt, sind Lernen und persönliches Wachstum wesentliche Gründe für Menschen, einer InnerSoure Community beizutreten und dabei zu bleiben. +Die Weiterbildung ihrer https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] ist eines der stärksten Werkzeuge, welches _Trusted Committer_ zur Verfügung haben, um die Geschwindigkeit, den Output und die Langlebigkeit ihrer Communitiy zu erhöhen. Es ist auch eines der Hauptargumente, um das Management eines Unternehmens davon zu überzeugen, ihren Mitarbeitern zu erlauben an einer _InnerSource Community_ teilzunehmen, da dies ihre Mitarbeiter für das Unternehmen wertvoller macht und dem Unternehmen hilft, seine Top-Talente zu halten. -Zusammengefasst ist es eine Aufgabe der _Trusted Committer_, ständig neue https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] zu werben und deren Fähigkeiten, Beiträge zu liefern, weiterzubilden. +Zusammengefasst ist es eine Aufgabe der _Trusted Committer_, ständig neue https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] zu werben und deren Fähigkeiten, Beiträge zu liefern, weiterzubilden. Diese Aktivität erhöht letztendlich die Fähigkeit der Community, schneller bessere Software zu erstellen. Dies geschicht durch Kommunikation von Möglichkeiten, Beiträge zu leisten, und durch Hilfestellungen und Mentoring von _Contributors_, um deren Wachstum zu fördern. diff --git a/trusted-committer/de/05-lowering-the-barriers-to-entry.asciidoc b/trusted-committer/de/05-lowering-the-barriers-to-entry.asciidoc index 60b5f170..5ae94f22 100644 --- a/trusted-committer/de/05-lowering-the-barriers-to-entry.asciidoc +++ b/trusted-committer/de/05-lowering-the-barriers-to-entry.asciidoc @@ -2,14 +2,14 @@ Aufgrund einer Reihe von Gründen ist das Werben um Beiträge für eine _InnerSource Community_ herausfordernder als in einer _Open Source Community_: -* In _InnerSource Communities_ ist die schiere Anzahl an möglichen https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] geringer. +* In _InnerSource Communities_ ist die schiere Anzahl an möglichen https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] geringer. * _Contributors_ werden Ihre Beiträge während ihrer Arbeitszeit erstellen wollen, was bedeutet, dass sie höheren zeitlichen Beschränkungen unterliegen. * Das Arbeiten an einem _InnerSource Projekt_ muss nicht zwangsläufig Teil der Leistungsziele eines _Contibutors_ sein, d.h. die Zeit, die sie während dem Arbeiten in der _InnerSoure_ verbringen, kann sie davon ablenken, ihre Leistungsziele zu erreichen. -Das sind die Gründe, warum es für _Trusted Committer_ wichtig ist, den Prozess für Beiträge und das Anwerben von https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] so reibungslos wie möglich zu machen. Es gibt eine Reihe von Punkten, die dabei hilfreich sein können: +Das sind die Gründe, warum es für _Trusted Committer_ wichtig ist, den Prozess für Beiträge und das Anwerben von https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] so reibungslos wie möglich zu machen. Es gibt eine Reihe von Punkten, die dabei hilfreich sein können: * jedes Repository sollte ein gepflegtes README.md enthalten. Ein gutes README.md erklärt, was das Repository beinhaltet und für was es benutzt werden kann. Zusätzlich sollte es Informationen enthalten, wie man die Software aus dem Repository herunterlädt, compiliert, testet und benutzt, einschließlich der Information zur Lizenzierung. -* jedes Repository sollte ein gepflegtes CONTRIBUTING.md enthalten, welches die Erwartungen an den https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributor_] beschreibt. Es sollte mindestens folgende Fragen beantworten: +* jedes Repository sollte ein gepflegtes CONTRIBUTING.md enthalten, welches die Erwartungen an den https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributor_] beschreibt. Es sollte mindestens folgende Fragen beantworten: ** Wie erstelle ich einen Bug Report oder einen Feature Request? ** Wen (und wie) kann bei Fragen kontaktieren? ** Welche Konventionen gelten für Codierung, Branching oder Commit Messages? @@ -20,13 +20,13 @@ Das sind die Gründe, warum es für _Trusted Committer_ wichtig ist, den Prozess Falls die Software mit einer internen Lizenz versehen ist, was in machen Unternehmen eine Voraussetzung für die gemeinsame Nutzung von Software zwischen juristischen Einheiten ist, sollte eine Kopie dieser Lizenz und eine für Laien verständliche Erklärung der daraus resultierenden Rechte und Pflichten zur Verfügung stehen. -Neben ausreichender Dokumentation sollte es für die potentiellen https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] ähnlich wie bei einer Open Source +Neben ausreichender Dokumentation sollte es für die potentiellen https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] ähnlich wie bei einer Open Source Software Entwicklung sehr einfach und selbsterklärend sein, die Software lokal ausführen und testen zu können. Dies erlaubt es, so einfach wie möglich mit eigenen Beiträgen beginnen und selbst verifizieren zu können. Es gibt grundsätzlich zwei Modelle um Beiträge zu erstellen: -_shared repository_ und _fork and join_. Beide haben jeweils Vorteile, und als ein _Trusted Committer_ solltest du beide Modelle unterstützen, um die verschiedenen Bedürfnisse der zukünftigen und aktuellen https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] zu unterstützen. +_shared repository_ und _fork and join_. Beide haben jeweils Vorteile, und als ein _Trusted Committer_ solltest du beide Modelle unterstützen, um die verschiedenen Bedürfnisse der zukünftigen und aktuellen https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] zu unterstützen. Deine _Contributors_ werden zahlreiche Fragen über den Prozess oder die Community selbst haben, und es muss jemand verfügbar sein, der diese Fragen beantwortet. Deshalb ist es für eine _InnerSource Community_ wichtig, einen oder mehrere Kontaktpersonen zu haben, die zur Beantwortung der Fragen zur Verfügung stehen. Normalerweise ist diese Kontaktperson jemand aus der Gruppe der _Trusted Committer_, oder aber sie muss sicherstellen, dass ein anderes Mitglied der _Community_ diese Aufgabe übernimmt. -Es ist wichtig, zukünftigen https://innersourcecommons.org/resources/learningpath/contributor/index[_Contributors_] bei der Auswahl zu helfen, welche Beiträge benötigt werden. Dabei kann es sich sowohl um Code als auch andere Artefakte handeln, wie zum Beispiel das Schreiben von Dokumentationen, das Erstellen von Grafiken oder Veranstaltungen zu organisieren. Üblicherweise werden dazu im jeweiligen Workflowmanagementsystem der Community spezielle "newcomer tasks" ausgewiesen, oder man etabliert einen Marktplatz für offene Aufgaben, den _Contributors_ nutzen können. +Es ist wichtig, zukünftigen https://innersourcecommons.org/learn/learning-path/contributor/01[_Contributors_] bei der Auswahl zu helfen, welche Beiträge benötigt werden. Dabei kann es sich sowohl um Code als auch andere Artefakte handeln, wie zum Beispiel das Schreiben von Dokumentationen, das Erstellen von Grafiken oder Veranstaltungen zu organisieren. Üblicherweise werden dazu im jeweiligen Workflowmanagementsystem der Community spezielle "newcomer tasks" ausgewiesen, oder man etabliert einen Marktplatz für offene Aufgaben, den _Contributors_ nutzen können. Zusammengefasst ist es sehr wichtig für _InnerSource Communities_ in einem Unternehmen Hürden für Beiträge so gering wie möglich zu halten, um möglichst vielen Kollegen das Mitwirken zu ermöglichen. Das bedeutet, dass sowohl der Zugriff auf hilfreiche Dokumentation bereit stehen sollte, als auch dass Ansprechpartner für die Beantwortung von Fragen und zur Förderung der Zusammenarbeit zur Verfügung stehen sollten. Kurz gesagt, _Trusted Committer_ sollten sicherstellen, dass der Einstieg und das Beitragen als positive Erfahrungen wahrgenommen wird. diff --git a/trusted-committer/de/06-advocating-for-the-communitys-needs.asciidoc b/trusted-committer/de/06-advocating-for-the-communitys-needs.asciidoc index daaddf01..8aadf029 100644 --- a/trusted-committer/de/06-advocating-for-the-communitys-needs.asciidoc +++ b/trusted-committer/de/06-advocating-for-the-communitys-needs.asciidoc @@ -10,14 +10,14 @@ _Trusted Committer_ generieren Vertrauen im Unternehmen und agieren, aufbauend a Sie sind dafür verantwortlich, dass sowohl technische als auch organisatorische Risiken an das Management berichtet werden. Gleichzeitig müssen _Trusted Committer_ strategisch handeln und sich innerhalb der vom Unternehmen gebotenen Freiheiten bewegen. -_Trusted Committer_ müssen sich auch darum kümmern, dass die Community und einzelne https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[Contributors] öffentliche Anerkennung für Ihre Arbeit erhalten. Öffentliche Anerkennung ist die Währung, mit der Contributors belohnt werden, speziell diejenigen, die freiwillig beitragen. Es hat sich bewährt, wertvolle Contributors öffentlich zu loben und sicherzustellen, dass ihre Führungskraft über ihre Beiträge informiert werden. Beiträge nicht zu loben kann für die jeweiligen Contributors frustrierend sein und wirkt sich negativ auf die Community aus. So etwas kann in Unternehmen passieren, die noch nicht an das InnerSource-Arbeitsmodell gewöhnt sind, oder wenn die von der InnerSource-Community entwickelte Software hinter den Kulissen ausgeführt wird und das Management die Beitrage der Community einfach nicht kennt. +_Trusted Committer_ müssen sich auch darum kümmern, dass die Community und einzelne https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] öffentliche Anerkennung für Ihre Arbeit erhalten. Öffentliche Anerkennung ist die Währung, mit der Contributors belohnt werden, speziell diejenigen, die freiwillig beitragen. Es hat sich bewährt, wertvolle Contributors öffentlich zu loben und sicherzustellen, dass ihre Führungskraft über ihre Beiträge informiert werden. Beiträge nicht zu loben kann für die jeweiligen Contributors frustrierend sein und wirkt sich negativ auf die Community aus. So etwas kann in Unternehmen passieren, die noch nicht an das InnerSource-Arbeitsmodell gewöhnt sind, oder wenn die von der InnerSource-Community entwickelte Software hinter den Kulissen ausgeführt wird und das Management die Beitrage der Community einfach nicht kennt. Ein guter _Trusted Committer_ arbeitet mit dem Management zusammen und setzt sich dafür ein, Erfolge zu feiern. Erfolge nicht zu feiern geschieht in den meisten Fällen nicht aus böser Absicht und ist einfach zu beheben. -Ein anderer Fall, der die Vermittlung des _Trusted Committers_ erfordert, ist wenn https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[Contributors] keine Zeit oder Erlaubnis bekommen, an der Community mitzuarbeiten. +Ein anderer Fall, der die Vermittlung des _Trusted Committers_ erfordert, ist wenn https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] keine Zeit oder Erlaubnis bekommen, an der Community mitzuarbeiten. Dies kann passieren, wenn die Community an Produkten ausserhalb des Verantwortungsbereichs des _Contributors_ arbeitet und diese nicht relevant für die Ziele der jeweiligen Untereinheit im Unternehmen sind. In diesem Fall sollte der _Trusted Committer_ das Gespräch mit der Führungskraft des _Contributors_ suchen und sich für eine andere Entscheidung einsetzen. -Zusammengefasst gibt es viele Situationen, in denen sich der _Trusted Committer_ für die Interessen der einzelnen https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/contributor/01-introduction-article.asciidoc[Contributors] und für das Unternehmen als ganzes einsetzen sollte. +Zusammengefasst gibt es viele Situationen, in denen sich der _Trusted Committer_ für die Interessen der einzelnen https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] und für das Unternehmen als ganzes einsetzen sollte. _Trusted Committer_ verstehen, dass der Wert, den die Community für das Unternehmen bieten kann, von einer funktionierenden und langlebigen Community und letztendlich von einer vertrauenswürdigen Beziehung zwischen Unternehmen und Community abhängt. diff --git a/trusted-committer/de/07-becoming-a-trusted-committer.asciidoc b/trusted-committer/de/07-becoming-a-trusted-committer.asciidoc index fc159128..8032b324 100644 --- a/trusted-committer/de/07-becoming-a-trusted-committer.asciidoc +++ b/trusted-committer/de/07-becoming-a-trusted-committer.asciidoc @@ -5,10 +5,10 @@ Die Rolle des _Trusted Committer_ ist zwar anspruchsvoll, aber auch erfüllend. InnerSource Communities funktionieren nach denselben Prinzipien wie Open Source Communities, eines davon ist Meritokratie. In einer Meritokratie wird Ansehen basierend auf Talent, Anstrengung und Erreichtem erworben. Das bedeutet, dass das Ansehen und Privilegien, die mit der Rolle des _Trusted Committers_ einhergehen, verdient werden müssen. Transparenz, ein weiterer Wert von Open Source, spielt ebenfalls eine wesentliche Rolle dabei, Talent, Anstrengung und Erreichtes in der gesamten Gemeinschaft sichtbar zu machen. -Der Prozess, offiziell ein _Trusted Committer_ zu werden, unterscheidet sich von Community zu Community und hängt davon ab, wo du persönlich in deiner Inner Source Reise stehst und wird sich im Lauf der Zeit entwickeln. In neu gegründeten Communities übernehmen die Gründer oft selbst die Rolle des _Trusted Committers_. Wenn die Community dann wächst, oder in größeren Communities, werden _Trusted Committer_ normalerweise nominiert oder von den https://innersourcecommons.org/resources/learningpath/contributor/index[Contributors] der Community gewählt. +Der Prozess, offiziell ein _Trusted Committer_ zu werden, unterscheidet sich von Community zu Community und hängt davon ab, wo du persönlich in deiner Inner Source Reise stehst und wird sich im Lauf der Zeit entwickeln. In neu gegründeten Communities übernehmen die Gründer oft selbst die Rolle des _Trusted Committers_. Wenn die Community dann wächst, oder in größeren Communities, werden _Trusted Committer_ normalerweise nominiert oder von den https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] der Community gewählt. Trotzdem sollte die Rolle des _Trusted Committers_ freiwillig übernommen werden, denn sie erfordert großen Zeitaufwand und Engagement um erfolgreich zu sein. -Welche Kriterien gelten bei der Nominierungen von https://innersourcecommons.org/resources/learningpath/contributor/index[Contributors] für die Rolle des _Trusted Committers_? Was benötigt man, um die Rolle des _Trusted Committers_ erfolgreich auszufüllen? Zuallererst müssen potentielle _Trusted Committer_ ihre tiefe technische Kompetenz während ihrer Arbeit in der Community unter Beweis stellen. Zusätzlich dazu müssen sie zeigen, dass sie wirkungsvoll mit den Kollegen der Community, und idealerweise genauso mit den Product Ownern und dem Management, zusammen arbeiten können. +Welche Kriterien gelten bei der Nominierungen von https://innersourcecommons.org/learn/learning-path/contributor/01[Contributors] für die Rolle des _Trusted Committers_? Was benötigt man, um die Rolle des _Trusted Committers_ erfolgreich auszufüllen? Zuallererst müssen potentielle _Trusted Committer_ ihre tiefe technische Kompetenz während ihrer Arbeit in der Community unter Beweis stellen. Zusätzlich dazu müssen sie zeigen, dass sie wirkungsvoll mit den Kollegen der Community, und idealerweise genauso mit den Product Ownern und dem Management, zusammen arbeiten können. Auf dieselbe Art müssen sie den Willen und die Geduld aufweisen, ihre Fähigkeiten zu nutzen und bewusst sich Zeit nehmen, um _Contributors_ weiter zu qualifizieren. Schließlich erfordert die Erfüllung der Rolle des _Trusted Committers_ eine gewisse emotionale Reife, um mit stressvollen sozialen Situationen umzugehen die mit Sicherheit ab und zu aufkommen. Contributors, welche diese Kriterien erfüllen, sind nach unserer Meinung gute Kandidaten für potentielle _Trusted Committers_. diff --git a/trusted-committer/ja/01-introduction-ja.asciidoc b/trusted-committer/ja/01-introduction-ja.asciidoc index 5aafc784..8a6cbc34 100644 --- a/trusted-committer/ja/01-introduction-ja.asciidoc +++ b/trusted-committer/ja/01-introduction-ja.asciidoc @@ -13,7 +13,7 @@ Trusted Committerの役割は、要求が厳しくやりがいがあるもので 次のセクションでは、これらの両方の側面について説明します。 Trusted Committerの実際の役割について詳しく説明する前に、抽象化が高いレベルでTrusted Committerの役割とInnerSourceの他の役割を比較して、なぜその名前が適切であると同時に重要であると考えるかの理由を説明します。 -https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] の役割から始めましょう。 +https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] の役割から始めましょう。 _コントリビューター_ は、名前の通り、InnerSourceコミュニティにコントリビューションします。 これらのコントリビューションは、バグレポート、機能リクエスト、ドキュメントなど、コードやコード以外の成果の可能性があります。 @@ -26,11 +26,11 @@ _Trusted Committer_ は常にInnerSourceコミュニティのメンバーであ この例では、Trusted Committerは、ゲストが快適で効率的に共同作業できるように、ハウスの構築とハウスルール設定の両方に責任があります。 コントリビューターと比較すると、Trusted Committersはコードを本番環境に近づける責任を負っており、一般的にリスクの高いタスクを実行することが許可されています。 -https://innersourcecommons.org/resources/learningpath/product-owner/index[_プロダクトオーナー_ (PO)]は、InnerSourceにおける3番目の役割です。 +https://innersourcecommons.org/learn/learning-path/product-owner/01[_プロダクトオーナー_ (PO)]は、InnerSourceにおける3番目の役割です。 アジャイルプロセスと同様に、POはコミュニティが実装する要件やストーリの定義と優先順位付けに責任をもちます。 POは、Trusted Committerと頻繁に対話します(例えば、要求された機能や提供された機能が実際に製品に属することを確認します)。 特に、小規模で草の根のInnerSourceコミュニティでは、Trusted Committerは通常POとしても活動します。 -より詳細については、 https://innersourcecommons.org/resources/learningpath/product-owner/index[ラーニングパスのプロダクトオーナーセグメント] を確認してください。 +より詳細については、 https://innersourcecommons.org/learn/learning-path/product-owner/01[ラーニングパスのプロダクトオーナーセグメント] を確認してください。 === 役割の名前が重要な理由 @@ -48,10 +48,10 @@ Trusted Committerの「信頼された（Trusted）」とは、その人が信 Trusted Committer には、次のようなさまざまな責任があります。 -* https://innersourcecommons.org/resources/learningpath/trusted-committer/02/[製品品質の確保] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/03/[コミュニティの健全性維持] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/05/[コントリビューションの壁の削減] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/04/[コミュニティのレベル向上] -* https://innersourcecommons.org/resources/learningpath/trusted-committer/06/[コミュニティのニーズ提唱] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/02/[製品品質の確保] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/03/[コミュニティの健全性維持] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/05/[コントリビューションの壁の削減] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/04/[コミュニティのレベル向上] +* https://innersourcecommons.org/learn/learning-path/trusted-committer/06/[コミュニティのニーズ提唱] -これらの責任については、次のページで詳しく説明し、この記事の最後で https://innersourcecommons.org/resources/learningpath/trusted-committer/07/[Trusted Committe になる] ための道筋についても説明します。 +これらの責任については、次のページで詳しく説明し、この記事の最後で https://innersourcecommons.org/learn/learning-path/trusted-committer/07/[Trusted Committe になる] ための道筋についても説明します。 diff --git a/trusted-committer/ja/02-ensuring-product-quality-ja.asciidoc b/trusted-committer/ja/02-ensuring-product-quality-ja.asciidoc index c735e371..726db893 100644 --- a/trusted-committer/ja/02-ensuring-product-quality-ja.asciidoc +++ b/trusted-committer/ja/02-ensuring-product-quality-ja.asciidoc @@ -7,7 +7,7 @@ InnerSourceのコミュニティでTrusted Committerたちは、すべての技 これには、コミュニティ内外で意思疎通を図り、必要に応じてこれらの決定を支持することが含まれます。 しかし、Trusted Committerは、必ずしも技術関連の決定をすべて自分で行ったり、それを実装するためのすべての作業を行うわけではありません。 -Trusted Committer の仕事は、彼らのコミュニティの品質基準を伝え、明確にし、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] が理解でき、実行可能な形にそれらを策定することです。 +Trusted Committer の仕事は、彼らのコミュニティの品質基準を伝え、明確にし、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] が理解でき、実行可能な形にそれらを策定することです。 これにはもちろん書面による文書も含まれますが、Trusted Committer がこれらの品質基準を伝える最も効果的な方法は、例示によるものです。 私たちは、InnerSourceコミュニティが開発をまとめる方法だけでなく、彼らが作成するソフトウェアの品質においても、従来のソフトウェア開発プロジェクトと差別化を図ることは価値ある目標であると考えています。 ソフトウェア品質の高さは、InnerSourceコミュニティのユーザとその管理者の信頼を確立し維持するために不可欠なものです。 @@ -17,15 +17,15 @@ Trusted Committers は、コミュニティが質の高いソフトウェアを ピアレビューは、通常、プルリクエスト(PR)の一部として行われ、品質を確保するために最も頻繁に使用されます。 通常、誰もが必要な改善点を指摘することでプルリクエストを開始して参加できますが、最終的にコントリビューションを受け入れてマージしたり拒否したりできるのは、通常はTrusted Committerだけです。 これが先程「Trusted Committersはコードを本番環境に近づけることができる」と言った意味になります。 -Trusted Committersは、PR中にコントリビューションがゴールラインを越えられるように、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] を支援する必要もあります。 +Trusted Committersは、PR中にコントリビューションがゴールラインを越えられるように、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] を支援する必要もあります。 そうは言っても、最終的にそれを実現するのはコントリビューターの仕事です。 Trusted Committerの仕事は、デフォルトですべてのコントリビューションを受け入れるのではなく、品質と範囲に関して定義された基準を満たすものだけを受け入れることです。 -また、Trusted Committerは、PRで https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] のサポートに多くの時間を費やすことになっても、コントリビューターのコードをできるだけ「適合する」ように書き直すことは避けるべきです。 +また、Trusted Committerは、PRで https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] のサポートに多くの時間を費やすことになっても、コントリビューターのコードをできるだけ「適合する」ように書き直すことは避けるべきです。 Trusted Committerは、長期的な視点を持ち、このような支援がコミュニティの寿命への投資で、長期的にはコミュニティの開発速度を向上させることを理解しています。 時々、プロジェクトの要件や制限が事前にわからず、開発中に発見されることがあります。 -Trusted Committerは、これらの発見を https://innersourcecommons.org/resources/learningpath/product-owner/index[_プロダクトオーナー_] と https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] のために捕捉し、ドキュメントにすることを確認する責任もあります。 +Trusted Committerは、これらの発見を https://innersourcecommons.org/learn/learning-path/product-owner/01[_プロダクトオーナー_] と https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] のために捕捉し、ドキュメントにすることを確認する責任もあります。 しかし、Trusted Committerの品質に関する権限は、プルリクエストの範囲を越えています。 Trusted Committersは品質を戦略レベルで考え、構築中のソフトウェアの寿命を確保します。 @@ -33,9 +33,9 @@ Trusted Committersは品質を戦略レベルで考え、構築中のソフト また、必要に応じて、コミュニティがソフトウェアをリファクタリングするための十分な時間を確保したり、品質改善するためにリリース日を移動したりするなど、管理面のタスクも含まれます。 Trusted Committerの有効性は、コードの健全性と強く関係しています。 -後者がなければ、Trusted Committerはバグや脆弱なアーキテクチャのための回避策の検証や文書化に貴重な時間の多くを費やすことになり、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] の指導に十分な時間を割くことができなくなってしまいます。 +後者がなければ、Trusted Committerはバグや脆弱なアーキテクチャのための回避策の検証や文書化に貴重な時間の多くを費やすことになり、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] の指導に十分な時間を割くことができなくなってしまいます。 まとめると、製品の品質を確保することは、Trusted Committer達の重要な責任です。 彼らは品質基準を設定し、例示することでリードします。 -彼らはプルリクエストに参加し、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] が品質基準を満たすのを支援します。 +彼らはプルリクエストに参加し、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] が品質基準を満たすのを支援します。 また、彼らはソフトウェアの長期的な健全性についても責任を持ちます。 diff --git a/trusted-committer/ja/03-keeping-the-community-healthy-ja.asciidoc b/trusted-committer/ja/03-keeping-the-community-healthy-ja.asciidoc index 6fe21e10..8dd1e732 100644 --- a/trusted-committer/ja/03-keeping-the-community-healthy-ja.asciidoc +++ b/trusted-committer/ja/03-keeping-the-community-healthy-ja.asciidoc @@ -6,10 +6,10 @@ そのためには、製品の品質を確保することと健全なコミュニティを育てることの間で、バランスを取る必要があります。 健全なコミュニティとはどのようなものでしょうか？ -簡単に言うと、健全なコミュニティでは、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] はソフトウェア開発にほとんどの時間を費やすことができ、能力を高めることができます。 +簡単に言うと、健全なコミュニティでは、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] はソフトウェア開発にほとんどの時間を費やすことができ、能力を高めることができます。 その結果、健全なコミュニティは、継続して成長することになります。 -なぜ、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] はコミュニティに参加して留まるのでしょうか？ +なぜ、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] はコミュニティに参加して留まるのでしょうか？ コミュニティの目的や使命に賛同しているため、そうする人達がいます。 この目的を明確にして推進することが、Trusted Committer の仕事です。 この重要性は、認識されていないことが多いが、コミュニティとそのプロダクトをマーケティングすることは本当に重要です。 @@ -29,11 +29,11 @@ Trusted Committers は多くの場合、ジュニア開発者のメンターと そうすることで Trusted Committer は、コミュニティの学習スピードを、従来のソフトウェア開発プロジェクトをはるかに上回るものに高めることができます。 私たちは、Trusted Committer は、よほど正当な理由がない限り、周知されたリリース日に到達するよりも、プルリクエスト中のオンボーディングと指導を優先すべきだと考えています。 -プルリクエスト中に優れた指導を行うことは、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] の信頼と関与のレベルを高め、より多くのコントリビューションにつながります。 -これについては、 https://innersourcecommons.org/resources/learningpath/trusted-committer/04/["コミュニティのレベル向上"] で詳しく説明します。 +プルリクエスト中に優れた指導を行うことは、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] の信頼と関与のレベルを高め、より多くのコントリビューションにつながります。 +これについては、 https://innersourcecommons.org/learn/learning-path/trusted-committer/04/["コミュニティのレベル向上"] で詳しく説明します。 最後に、特にプロセスに重点を置いている大企業で、彼らがオーバーヘッドや無駄と考える活動の代わりに、ソフトウェアの開発に集中できるのでInnerSource のコミュニティに留まる人たちもいます。 -このコンテキストでの Trusted Committer の仕事は、有用なコントリビューションガイドラインを伝えて制定することにより、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] が実際にプロジェクトに集中できるようにすることです。 +このコンテキストでの Trusted Committer の仕事は、有用なコントリビューションガイドラインを伝えて制定することにより、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] が実際にプロジェクトに集中できるようにすることです。 これらのガイドラインの重要な側面の1つは、私たちがプルリクエストで _シグナリング_ と呼ぶものを説明することです。コメントはどのように見えるべきか? 「いいね」や「+1」のコメントの意味は何ですか？ @@ -42,6 +42,6 @@ Trusted Committers は多くの場合、ジュニア開発者のメンターと 最終的に、Trusted Committer は、コミュニティがプロセス関連の問題を発見し、それらをコミュニティとして可能な限り適合および改善できるようにしなければなりません。 Trusted Committer がこれらすべての責任を果たすためには、コミュニティメンバーと定期的にコミュニケーションをとり、常に耳を傾けることが重要です。 -これについての詳細は、 https://innersourcecommons.org/resources/learningpath/trusted-committer/06/["コミュニティのニーズ提唱"] のセクションで説明します。 +これについての詳細は、 https://innersourcecommons.org/learn/learning-path/trusted-committer/06/["コミュニティのニーズ提唱"] のセクションで説明します。 -要約すると、Trusted Committersは、他のコミュニティメンバーから学ぶ機会を作ることでソフトウェアの作成と個人的成長に集中できるように、 https://innersourcecommons.org/resources/learningpath/contributor/index[_コントリビューター_] が歓迎され感謝される環境を作るように努力すべきです。 +要約すると、Trusted Committersは、他のコミュニティメンバーから学ぶ機会を作ることでソフトウェアの作成と個人的成長に集中できるように、 https://innersourcecommons.org/learn/learning-path/contributor/01[_コントリビューター_] が歓迎され感謝される環境を作るように努力すべきです。 diff --git a/trusted-committer/zh/01-introduction-zh.asciidoc b/trusted-committer/zh/01-introduction-zh.asciidoc index 8b4475ba..b3c12999 100644 --- a/trusted-committer/zh/01-introduction-zh.asciidoc +++ b/trusted-committer/zh/01-introduction-zh.asciidoc @@ -12,7 +12,7 @@ https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡 Trusted Committer始终是InnerSource社区的成员，该社区有时也称为维护团队。我们用比喻来形容一下，Trusted Committer既负责建造房屋，也负责制定房屋规则，以确保其客人感到舒适，并可以进行有效的合作。与 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]相比，Trusted Committer已经承担了将代码推向生产的责任，并且通常被允许执行更高风险的任务。 -https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品所有者（Product Owner）_]是InnerSource中的第三个角色。与敏捷过程类似，产品负责人负责定义和优先考虑社区要实施的需求和故事。 产品负责人经常与Trusted Committer进行交互（例如，确保所请求或提供的功能实际上属于该产品）。特别是在较小的草根InnerSource社区中，Trusted Committer通常还充当产品负责人。查看我们的 https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品负责人学习方法（Product Owner Learning Path segment）_]，以获取更多详细信息。 +https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品所有者（Product Owner）_]是InnerSource中的第三个角色。与敏捷过程类似，产品负责人负责定义和优先考虑社区要实施的需求和故事。 产品负责人经常与Trusted Committer进行交互（例如，确保所请求或提供的功能实际上属于该产品）。特别是在较小的草根InnerSource社区中，Trusted Committer通常还充当产品负责人。查看我们的 https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品负责人学习方法（Product Owner Learning Path segment）_]，以获取更多详细信息。 为什么角色名称很重要？ diff --git a/trusted-committer/zh/02-ensuring-product-quality-zh.asciidoc b/trusted-committer/zh/02-ensuring-product-quality-zh.asciidoc index 984ac29a..7243eeb9 100644 --- a/trusted-committer/zh/02-ensuring-product-quality-zh.asciidoc +++ b/trusted-committer/zh/02-ensuring-product-quality-zh.asciidoc @@ -10,7 +10,7 @@ Trusted Committer还需要确保社区拥有生产高质量软件所需的基础 也就是说，实现这一目标最终是 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]的工作。Trusted Committer的工作不是默认接受所有贡献，而仅接受在质量和范围方面符合定义标准的贡献。Trusted Committer应避免重写贡献者的代码去让它们尽可能符合规定，即使这意味着要花费更多时间在PR中为 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]提供支持。Trusted Committer应具有长远的眼光，并了解这种支持是对社区的一种长期投资，从长远来看，它将提高社区的发展速度。 -有时项目需求或限制不是都能预先设计的，而是在开发过程中被发现的。Trusted Committer还会负责为 https://innersourcecommons.org/resources/learningpath/product-owner/index[_产品所有者（Product Owner）_]和贡献者（Contributor）捕获并记录这些发现。 +有时项目需求或限制不是都能预先设计的，而是在开发过程中被发现的。Trusted Committer还会负责为 https://innersourcecommons.org/learn/learning-path/product-owner/01[_产品所有者（Product Owner）_]和贡献者（Contributor）捕获并记录这些发现。 但是，Trusted Committer在控制质量方面的权限超出了普通PR的范围。Trusted Committer从战略角度考虑质量，并确保所构建软件的长期生命力。从确保代码的整洁到维护整个软件的概念完整性，这涉及到面向整体代码的责任。还需要完成面向管理的任务，例如确保给社区足够的时间来重构其软件，或者在需要时为支持质量改进而推迟发布日期。Trusted Committer的工作效率与代码健康状况密切相关。 diff --git a/trusted-committer/zh/04-uplevelling-community-members-zh.asciidoc b/trusted-committer/zh/04-uplevelling-community-members-zh.asciidoc index 14d93506..f9b32ea9 100644 --- a/trusted-committer/zh/04-uplevelling-community-members-zh.asciidoc +++ b/trusted-committer/zh/04-uplevelling-community-members-zh.asciidoc @@ -6,6 +6,6 @@ 最后，Trusted Committer有责任在鼓励大家完成挑战性任务、指导他们完成工作的过程中，来识别和支持有成长潜力的贡献者。我们认为，这是Trusted Committer的最高责任，对于Trusted Committer和 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]来说都是非常有价值的。我们听过一些Trusted Committer说，指导和推动人们去提升自己的能力，比花时间在编写软件上更重要。 -如 https://innersourcecommons.org/resources/learningpath/trusted-committer/03/[_上一章节_]所述，学习和个人成长是人们加入并坚持留在InnerSource社区的原因。而提升 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]的质量和数量是让他们留下的最有效方式之一，Trusted Committer可以使用它们来提高其社区的发展速度、产出和寿命。这也是说服管理层让其员工参与InnerSource社区的主要论据之一，因为这将使他们的员工对公司整体更有价值，并帮助他们保留顶尖人才。 +如 https://innersourcecommons.org/learn/learning-path/trusted-committer/03/[_上一章节_]所述，学习和个人成长是人们加入并坚持留在InnerSource社区的原因。而提升 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]的质量和数量是让他们留下的最有效方式之一，Trusted Committer可以使用它们来提高其社区的发展速度、产出和寿命。这也是说服管理层让其员工参与InnerSource社区的主要论据之一，因为这将使他们的员工对公司整体更有价值，并帮助他们保留顶尖人才。 总而言之，Trusted Committer需要吸引新的 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]，并提高其贡献能力。这可以让社区更快更好地产出。Trusted Committer通过交流做出贡献，以及帮助 https://innersourcecommons.org/resources/learningpath/contributor/zh/index[_贡献者（Contributor）_]成长来实现这一点。