You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: patterns/2-structured/core-team.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,8 +68,8 @@ The core team may be composed of a small number of people on a full-time or a pa
68
68
The choice depends on the amount of work needed, the availability of resources, and the culture of the organization.
69
69
The most important consideration is to form the team in a way that allows the organization to empower and hold them accountable in the same way as any other team.
70
70
71
-
Due to their central role, core team members should nearly always fill the role of [Trusted Committers][tc] as well.
72
-
While the [Trusted Committer][tc] role focuses mostly on facilitating others' contribution and use of the project, a core team member regularly contributes to the project as well.
71
+
Due to their central role, core team members should nearly always fill the role of **Trusted Committers** as well (for more on that concept see [Learning Path][tc-learning-path] and [Pattern][tc-pattern]).
72
+
While the Trusted Committer role focuses mostly on facilitating others' contribution and use of the project, a core team member regularly contributes to the project as well.
73
73
The core team doesn't have its own business agenda that determines its contributions.
74
74
They decide what to work on based on what will help others most to use and contribute to the project.
75
75
@@ -103,4 +103,5 @@ Structured
103
103
104
104
[Russell R. Rutledge](https://github.com/rrrutledge)
0 commit comments