Skip to content

Minor suggestions to two sections #296

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
+6 −3
Closed

Minor suggestions to two sections #296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions patterns/2-structured/trusted-committer.md
View file
Original file line number Diff line number Diff line change
@@ -6,27 +6,30 @@ 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

- 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