From 4d9dc0ee31117fe755b09ee2969e55c062ea862d Mon Sep 17 00:00:00 2001 From: Doron Katz Date: Thu, 18 Feb 2021 20:18:53 -0800 Subject: [PATCH] Minor suggestions to two sections --- patterns/2-structured/trusted-committer.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/patterns/2-structured/trusted-committer.md b/patterns/2-structured/trusted-committer.md index 8ca8ea4ef..6b53af605 100644 --- a/patterns/2-structured/trusted-committer.md +++ b/patterns/2-structured/trusted-committer.md @@ -6,7 +6,7 @@ Trusted Committer Many InnerSource projects will find themselves in a situation where they consistently receive feedback, features, and bug-fixes from contributors. -In these situations project maintainers seek ways to recognize and reward the +In these situations, project maintainers seek ways to recognize and reward the work of the contributor above and beyond single contributions. ## Problem @@ -14,19 +14,22 @@ work of the contributor above and beyond single contributions. - Project maintainers want to find ways to scale their ability to support a project - Project maintainers want to find ways to lengthen the value delivered by a project - Project maintainers want to visibly reward frequent contributors and empower them to amplify their value contribution. -- Lack of language for recognizing contributions across teams within an organization +- Lack of mechanism for recognizing contributions across teams within an organization ## Context - You are the maintainer of a cross-team library, service, or shared resource - You receive regular contributions +- You receive regular feature requests +- You receive regular bug-fix requests - There are motivated contributors looking to build expertise through InnerSource projects ## Forces - Over the lifecycle of a project the focus of the maintainers may shift away to accommodate changing business priorities -- Contributors seek visible artifacts of their contributions demonstrating value +- Contributors seek visible recognition of their contributions demonstrating value - Maintaining a project of reasonable complexity is taxing for a small team +- Developing project features at scale is taxing for a small team ## Solution