Skip to content

Commit 3e9054f

Browse files
Update Trusted Committer patlet based on PR feedback
1 parent d21a66b commit 3e9054f

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

project-roles/trusted-committer.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,15 @@ work of the contributor above and beyond single contributions.
1313

1414
- You are the maintainer of a cross-team library, service, or shared resource
1515
- You receive regular contributions
16+
- There are motivated contributors looking to build expertise through
17+
inner-sourced projects
1618

1719
# Problem
1820

1921
- Project maintainers want to find ways to scale their ability to support a
2022
project
21-
- Project maintainers want to find ways to scale the longevity of the value
22-
delivered by a project
23+
- Project maintainers want to find ways to lengthen the value delivered by a
24+
project
2325
- Project maintainers want to visibly reward frequent contributors and
2426
empower them to amplify their value contribution.
2527
- Lack of language for recognizing contributions across teams within an
@@ -31,7 +33,6 @@ work of the contributor above and beyond single contributions.
3133
to accomodate changing business priorities
3234
- Contributors seek visible artifacts of their contributions demonstrating
3335
value
34-
- Motivated contributors looking to push further inner-sourced projects
3536
- Maintaining a project of reasonable complexity is taxing for a small team
3637

3738
# Solution
@@ -105,15 +106,16 @@ effort][praise] in making the project successful and set a new date to check-in.
105106

106107
## Sunsetting a Trusted Committer
107108

108-
There comes a time when removal of a Trusted Committer is necessary, such as:
109+
There comes a time when removal of a Trusted Committer is necessary, for
110+
example:
109111

110112
* No longer willing to take part
111113
* No longer able to perform their duties
112114
* No longer employed by the company
113115

114116
In each of the above cases a plan for removing access to project resources
115-
should agreed upon by both parties. This includes their entry in a project’s
116-
**Trusted Committer** section.
117+
should agreed upon by both parties. This includes transitioning their entry in
118+
a project's **Trusted Committer** section to a list of past contributors.
117119

118120
After access is removed it is courteous to [thank the Trusted Committer for
119121
their participation in a public way][praise]. This ensures clear communication
@@ -142,7 +144,7 @@ This has been tried and proven successful at Nike and PayPal.
142144

143145
# Authors
144146

145-
- Fernando Freire
147+
- [Fernando Freire]
146148

147149
# Acknowledgements
148150

@@ -162,3 +164,4 @@ Published internally at Nike; drafted via pull-request in June of 2018.
162164
[Jeremy Hicks]: https://github.com/greatestusername
163165
[Noah Cawley]: https://github.com/utanapishtim
164166
[praise]: https://github.com/paypal/InnerSourcePatterns/blob/master/praise-participants.md
167+
[Fernando Freire]: https://github.com/dogonthehorizon

0 commit comments

Comments
 (0)