From 3e3b5dc634ef4d8ff6ebd2c39223457d088313f3 Mon Sep 17 00:00:00 2001 From: "Tyler, Tim" Date: Wed, 26 Sep 2018 12:16:08 -0400 Subject: [PATCH 01/11] Inner Source Pattern describing enterprise InnerSource initiative oversight group --- innersource-guidance-group.md | 43 +++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 innersource-guidance-group.md diff --git a/innersource-guidance-group.md b/innersource-guidance-group.md new file mode 100644 index 000000000..5e51b98b3 --- /dev/null +++ b/innersource-guidance-group.md @@ -0,0 +1,43 @@ +## Title +InnerSource Guidance Group + +## Patlet +A company may require a mechanism to set broad governance and behavioral guidelines as part of the rollout and sustaining needs of an InnerSource initiative. + +## Problem +Without a set of organizational standards Trusted Committers, and individual teams, are free to set their own standards, which is a step in the right direction. However, team standards could be highly variant and further diverge over time as they evolve and adapt to new needs and forces. This can lead to confusion and frustration as contributors submit code across team and functional boundaries. The business is interested establishing a set of agreed-upon standard operating procedures that guide teams while still providing sufficient autonomy to meet the parochial needs of individual teams. + +## Context +A company is planning to introduce InnerSource as a strategic initiative. They are faced with reforming and steering the behavior of developers and engineers toward a common goal. In general functional groups and teams within the company adhere to a broad spectrum of standards regarding tools, development languages, collaboration models, engagement models, documentation models, etc. The company recognizes the value of the Trusted Committer role as a situational leader for a team that sets and enforces team standards, code contribution standards, contribution agreements, PR management, etc. however the company is interested in establishing organizational guidelines as well that steer and focus Trusted Committers and the teams they represent. + +As an example, the breadth of languages used within an engineering and operations organization could include, powershell, bash shell, perl, tcl, python, golang, java, shell augmented with sed and awk and jq, etc. and the organization wants to standardize as much as possible on a subset of these languages so that the ability to collaborate between teams is maximized. + +## Forces +- Separate engineering and development teams establish development standards that may be highly divergent from other teams which limits the ability to collaborate. +- As people move between teams, or responsibility for specific initiatives change over time, the ability of the organization to adapt to variant team norms results in decreased development velocity. + +## Solutions +Recognize that Trusted Committers are both situational leaders and subject matter experts representing their team and establish a governance model with a “committee” attended and chaired by Trusted Committers chartered with establishing company and/or organizational guidelines. + +- The “committee” is scheduled periodically as necessary by the TC’s – twice a week, once a month, quarterly, etc. +- The goal is to establish general direction, or a highway, while leaving freedom for individual teams to adapt to local needs, or side streets +- Trusted Committers establish organization guidelines that become templates for Contribution Agreements +- Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishmentment of organizational patterns +- The TC “committee” is responsible for communicating general guidelines to upper management +- This also ensures that teams and functional groups have a recurring touchpoint with other team and functional groups – establishing trust and insight into the overall organizational needs and requirements + +## Resulting Context + +## Rationale (optional) +Empowering TC's as representatives on behalf of their teams propagates ownership of the overall InnerSource strategy as it deploys and evolves in an organization and ensures that a baseline level of governance and standardization occurs. + +May mention: +- A large, highly regulated, financial organization is planning to implment a TC Steering Group to provide broad guidlelines and guard rails as part of their InnerSource initiative. + +## Author(s) +- Tim Tyler + +## Acknowledgements +- Tim Yao + +## Changelog From 290f3fd4990f25cf627678e743e2a88afa32e8ff Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 15:50:14 +0100 Subject: [PATCH 02/11] moving pattern to Initial --- .../1-initial/innersource-guidance-group.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename innersource-guidance-group.md => patterns/1-initial/innersource-guidance-group.md (100%) diff --git a/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md similarity index 100% rename from innersource-guidance-group.md rename to patterns/1-initial/innersource-guidance-group.md From 51a1ae9770ca85fb6bc0e85345161c037c6c59b1 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 15:53:34 +0100 Subject: [PATCH 03/11] Satifysing md-linter rules. Add placeholders for essential sections --- patterns/1-initial/innersource-guidance-group.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index 5e51b98b3..ca350973f 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -1,22 +1,28 @@ ## Title + InnerSource Guidance Group ## Patlet + A company may require a mechanism to set broad governance and behavioral guidelines as part of the rollout and sustaining needs of an InnerSource initiative. ## Problem + Without a set of organizational standards Trusted Committers, and individual teams, are free to set their own standards, which is a step in the right direction. However, team standards could be highly variant and further diverge over time as they evolve and adapt to new needs and forces. This can lead to confusion and frustration as contributors submit code across team and functional boundaries. The business is interested establishing a set of agreed-upon standard operating procedures that guide teams while still providing sufficient autonomy to meet the parochial needs of individual teams. ## Context + A company is planning to introduce InnerSource as a strategic initiative. They are faced with reforming and steering the behavior of developers and engineers toward a common goal. In general functional groups and teams within the company adhere to a broad spectrum of standards regarding tools, development languages, collaboration models, engagement models, documentation models, etc. The company recognizes the value of the Trusted Committer role as a situational leader for a team that sets and enforces team standards, code contribution standards, contribution agreements, PR management, etc. however the company is interested in establishing organizational guidelines as well that steer and focus Trusted Committers and the teams they represent. As an example, the breadth of languages used within an engineering and operations organization could include, powershell, bash shell, perl, tcl, python, golang, java, shell augmented with sed and awk and jq, etc. and the organization wants to standardize as much as possible on a subset of these languages so that the ability to collaborate between teams is maximized. ## Forces + - Separate engineering and development teams establish development standards that may be highly divergent from other teams which limits the ability to collaborate. - As people move between teams, or responsibility for specific initiatives change over time, the ability of the organization to adapt to variant team norms results in decreased development velocity. ## Solutions + Recognize that Trusted Committers are both situational leaders and subject matter experts representing their team and establish a governance model with a “committee” attended and chaired by Trusted Committers chartered with establishing company and/or organizational guidelines. - The “committee” is scheduled periodically as necessary by the TC’s – twice a week, once a month, quarterly, etc. @@ -28,16 +34,24 @@ Recognize that Trusted Committers are both situational leaders and subject matte ## Resulting Context +TBD + +## Known Instances + +TBD + ## Rationale (optional) + Empowering TC's as representatives on behalf of their teams propagates ownership of the overall InnerSource strategy as it deploys and evolves in an organization and ensures that a baseline level of governance and standardization occurs. May mention: - A large, highly regulated, financial organization is planning to implment a TC Steering Group to provide broad guidlelines and guard rails as part of their InnerSource initiative. ## Author(s) + - Tim Tyler ## Acknowledgements + - Tim Yao -## Changelog From 231132ed1602f5d5beda1eb45c21fdacc86c0a30 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 15:57:09 +0100 Subject: [PATCH 04/11] some typoe fixes and formatting --- patterns/1-initial/innersource-guidance-group.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index ca350973f..dec2ca088 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -8,11 +8,17 @@ A company may require a mechanism to set broad governance and behavioral guideli ## Problem -Without a set of organizational standards Trusted Committers, and individual teams, are free to set their own standards, which is a step in the right direction. However, team standards could be highly variant and further diverge over time as they evolve and adapt to new needs and forces. This can lead to confusion and frustration as contributors submit code across team and functional boundaries. The business is interested establishing a set of agreed-upon standard operating procedures that guide teams while still providing sufficient autonomy to meet the parochial needs of individual teams. +Without a set of organizational standards, Trusted Committers, and individual teams, are free to set their own standards, which is a step in the right direction. + +However, team standards could be highly variant and further diverge over time as they evolve and adapt to new needs and forces. This can lead to confusion and frustration as contributors submit code across team and functional boundaries. + +The business is interested in establishing a set of agreed-upon standard operating procedures that guide teams, while still providing sufficient autonomy to meet the parochial needs of individual teams. ## Context -A company is planning to introduce InnerSource as a strategic initiative. They are faced with reforming and steering the behavior of developers and engineers toward a common goal. In general functional groups and teams within the company adhere to a broad spectrum of standards regarding tools, development languages, collaboration models, engagement models, documentation models, etc. The company recognizes the value of the Trusted Committer role as a situational leader for a team that sets and enforces team standards, code contribution standards, contribution agreements, PR management, etc. however the company is interested in establishing organizational guidelines as well that steer and focus Trusted Committers and the teams they represent. +A company is planning to introduce InnerSource as a strategic initiative. They are faced with reforming and steering the behavior of developers and engineers toward a common goal. In general functional groups and teams within the company adhere to a broad spectrum of standards regarding tools, development languages, collaboration models, engagement models, documentation models, etc. + +The company recognizes the value of the Trusted Committer role as a situational leader for a team that sets and enforces team standards, code contribution standards, contribution agreements, PR management, etc. however the company is interested in establishing organizational guidelines as well that steer and focus Trusted Committers and the teams they represent. As an example, the breadth of languages used within an engineering and operations organization could include, powershell, bash shell, perl, tcl, python, golang, java, shell augmented with sed and awk and jq, etc. and the organization wants to standardize as much as possible on a subset of these languages so that the ability to collaborate between teams is maximized. @@ -28,7 +34,7 @@ Recognize that Trusted Committers are both situational leaders and subject matte - The “committee” is scheduled periodically as necessary by the TC’s – twice a week, once a month, quarterly, etc. - The goal is to establish general direction, or a highway, while leaving freedom for individual teams to adapt to local needs, or side streets - Trusted Committers establish organization guidelines that become templates for Contribution Agreements -- Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishmentment of organizational patterns +- Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishment of organizational patterns - The TC “committee” is responsible for communicating general guidelines to upper management - This also ensures that teams and functional groups have a recurring touchpoint with other team and functional groups – establishing trust and insight into the overall organizational needs and requirements @@ -45,7 +51,7 @@ TBD Empowering TC's as representatives on behalf of their teams propagates ownership of the overall InnerSource strategy as it deploys and evolves in an organization and ensures that a baseline level of governance and standardization occurs. May mention: -- A large, highly regulated, financial organization is planning to implment a TC Steering Group to provide broad guidlelines and guard rails as part of their InnerSource initiative. +- A large, highly regulated, financial organization is planning to implement a TC Steering Group to provide broad guidlines and guard rails as part of their InnerSource initiative. ## Author(s) From 28bba23f4b6debf0e5649d46bcc3eb2ace169aa9 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 16:01:09 +0100 Subject: [PATCH 05/11] Link to existing aptterns. cleanup --- patterns/1-initial/innersource-guidance-group.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index dec2ca088..7f5e7453f 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -8,7 +8,7 @@ A company may require a mechanism to set broad governance and behavioral guideli ## Problem -Without a set of organizational standards, Trusted Committers, and individual teams, are free to set their own standards, which is a step in the right direction. +Without a set of organizational standards, [Trusted Committers](../2-structured/trusted-committer.md), and individual teams, are free to set their own standards, which is a step in the right direction. However, team standards could be highly variant and further diverge over time as they evolve and adapt to new needs and forces. This can lead to confusion and frustration as contributors submit code across team and functional boundaries. @@ -29,11 +29,11 @@ As an example, the breadth of languages used within an engineering and operation ## Solutions -Recognize that Trusted Committers are both situational leaders and subject matter experts representing their team and establish a governance model with a “committee” attended and chaired by Trusted Committers chartered with establishing company and/or organizational guidelines. +Recognize that Trusted Committers are both **situational leaders** and **subject matter experts** representing their team and establish a governance model with a “committee” attended and chaired by Trusted Committers chartered with establishing company and/or organizational guidelines. - The “committee” is scheduled periodically as necessary by the TC’s – twice a week, once a month, quarterly, etc. - The goal is to establish general direction, or a highway, while leaving freedom for individual teams to adapt to local needs, or side streets -- Trusted Committers establish organization guidelines that become templates for Contribution Agreements +- Trusted Committers establish organization guidelines that become templates for [Contribution Agreements](../2-structured/project-setup/base-documentation.md) - Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishment of organizational patterns - The TC “committee” is responsible for communicating general guidelines to upper management - This also ensures that teams and functional groups have a recurring touchpoint with other team and functional groups – establishing trust and insight into the overall organizational needs and requirements @@ -46,12 +46,12 @@ TBD TBD -## Rationale (optional) +## Rationale Empowering TC's as representatives on behalf of their teams propagates ownership of the overall InnerSource strategy as it deploys and evolves in an organization and ensures that a baseline level of governance and standardization occurs. May mention: -- A large, highly regulated, financial organization is planning to implement a TC Steering Group to provide broad guidlines and guard rails as part of their InnerSource initiative. +- A large, highly regulated, financial organization is planning to implement a TC Steering Group to provide broad guidelines and guard rails as part of their InnerSource initiative. ## Author(s) From 845853c20c1007b254341c0752fd14ffadb28dab Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 16:17:37 +0100 Subject: [PATCH 06/11] work in feedback from #106 --- patterns/1-initial/innersource-guidance-group.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index 7f5e7453f..2d8e71fc4 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -24,18 +24,20 @@ As an example, the breadth of languages used within an engineering and operation ## Forces -- Separate engineering and development teams establish development standards that may be highly divergent from other teams which limits the ability to collaborate. -- As people move between teams, or responsibility for specific initiatives change over time, the ability of the organization to adapt to variant team norms results in decreased development velocity. +- Separate engineering and development teams establish development standards that may be highly divergent from other teams. (Effect: This limits the ability to collaborate.) +- People move between teams, and responsibility for specific initiatives change over time. (Effect: The ability of the organization to adapt to variant team norms results in decreased development velocity.) ## Solutions -Recognize that Trusted Committers are both **situational leaders** and **subject matter experts** representing their team and establish a governance model with a “committee” attended and chaired by Trusted Committers chartered with establishing company and/or organizational guidelines. +Recognize that Trusted Committers are both **situational leaders** and **subject matter experts** representing their team. Establish an InnerSource Guidance Group as a “committee” attended and chaired by Trusted Committers. Charter this InnerSource Guidance Group with establishing company and/or organizational guidelines. -- The “committee” is scheduled periodically as necessary by the TC’s – twice a week, once a month, quarterly, etc. +- The “committee” is scheduled periodically as necessary by the Trusted Committers – twice a week, once a month, quarterly, etc. - The goal is to establish general direction, or a highway, while leaving freedom for individual teams to adapt to local needs, or side streets - Trusted Committers establish organization guidelines that become templates for [Contribution Agreements](../2-structured/project-setup/base-documentation.md) -- Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishment of organizational patterns -- The TC “committee” is responsible for communicating general guidelines to upper management +- Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishment of organizational patterns. + - This guideline definition project itself can be run as an InnerSource project, accepting contributions from anywhere in the organization. + - By running this as a collaborative documentation project, it can role-model and verify the behaviors that they want to promote for other InnerSource projects as well. +- The InnerSource Guidance Group is responsible for communicating general guidelines to upper management - This also ensures that teams and functional groups have a recurring touchpoint with other team and functional groups – establishing trust and insight into the overall organizational needs and requirements ## Resulting Context From ef86c10eb2a3c035d63058a618667896bbba44d5 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 16:34:43 +0100 Subject: [PATCH 07/11] Modifying Patlet to include both Problem + Solution --- patterns/1-initial/innersource-guidance-group.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index 2d8e71fc4..4c758a790 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -4,7 +4,7 @@ InnerSource Guidance Group ## Patlet -A company may require a mechanism to set broad governance and behavioral guidelines as part of the rollout and sustaining needs of an InnerSource initiative. +A highly divergent set of development standards in different teams can slow down collaboration betweens these teams. A InnerSource Guidance Group that establishes broad governance and behavioral guidelines can help to reduce these frictions. ## Problem From d5d8d6cdc9a2f8a95fbb853e63302beae53d1aa8 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 16:42:11 +0100 Subject: [PATCH 08/11] remove extra whitespace --- patterns/1-initial/innersource-guidance-group.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index 4c758a790..e96de7e2c 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -10,13 +10,13 @@ A highly divergent set of development standards in different teams can slow down Without a set of organizational standards, [Trusted Committers](../2-structured/trusted-committer.md), and individual teams, are free to set their own standards, which is a step in the right direction. -However, team standards could be highly variant and further diverge over time as they evolve and adapt to new needs and forces. This can lead to confusion and frustration as contributors submit code across team and functional boundaries. +However, team standards could be highly variant and further diverge over time as they evolve and adapt to new needs and forces. This can lead to confusion and frustration as contributors submit code across team and functional boundaries. The business is interested in establishing a set of agreed-upon standard operating procedures that guide teams, while still providing sufficient autonomy to meet the parochial needs of individual teams. ## Context -A company is planning to introduce InnerSource as a strategic initiative. They are faced with reforming and steering the behavior of developers and engineers toward a common goal. In general functional groups and teams within the company adhere to a broad spectrum of standards regarding tools, development languages, collaboration models, engagement models, documentation models, etc. +A company is planning to introduce InnerSource as a strategic initiative. They are faced with reforming and steering the behavior of developers and engineers toward a common goal. In general functional groups and teams within the company adhere to a broad spectrum of standards regarding tools, development languages, collaboration models, engagement models, documentation models, etc. The company recognizes the value of the Trusted Committer role as a situational leader for a team that sets and enforces team standards, code contribution standards, contribution agreements, PR management, etc. however the company is interested in establishing organizational guidelines as well that steer and focus Trusted Committers and the teams they represent. @@ -34,8 +34,8 @@ Recognize that Trusted Committers are both **situational leaders** and **subject - The “committee” is scheduled periodically as necessary by the Trusted Committers – twice a week, once a month, quarterly, etc. - The goal is to establish general direction, or a highway, while leaving freedom for individual teams to adapt to local needs, or side streets - Trusted Committers establish organization guidelines that become templates for [Contribution Agreements](../2-structured/project-setup/base-documentation.md) -- Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishment of organizational patterns. - - This guideline definition project itself can be run as an InnerSource project, accepting contributions from anywhere in the organization. +- Trusted Committers collaborate on and refine guidelines asynchronously via passive documentation and the establishment of organizational patterns. + - This guideline definition project itself can be run as an InnerSource project, accepting contributions from anywhere in the organization. - By running this as a collaborative documentation project, it can role-model and verify the behaviors that they want to promote for other InnerSource projects as well. - The InnerSource Guidance Group is responsible for communicating general guidelines to upper management - This also ensures that teams and functional groups have a recurring touchpoint with other team and functional groups – establishing trust and insight into the overall organizational needs and requirements @@ -44,7 +44,7 @@ Recognize that Trusted Committers are both **situational leaders** and **subject TBD -## Known Instances +## Known Instances TBD @@ -62,4 +62,3 @@ May mention: ## Acknowledgements - Tim Yao - From 358ec02e6fe0c7ea7c84152f81147dce2b71796b Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 16:44:13 +0100 Subject: [PATCH 09/11] Fix linter issue --- patterns/1-initial/innersource-guidance-group.md | 1 + 1 file changed, 1 insertion(+) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index e96de7e2c..a299eff0d 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -53,6 +53,7 @@ TBD Empowering TC's as representatives on behalf of their teams propagates ownership of the overall InnerSource strategy as it deploys and evolves in an organization and ensures that a baseline level of governance and standardization occurs. May mention: + - A large, highly regulated, financial organization is planning to implement a TC Steering Group to provide broad guidelines and guard rails as part of their InnerSource initiative. ## Author(s) From 4f7d5a03686ee445067d1c302353035bc0a8f7a9 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 13 Feb 2021 13:45:00 +0100 Subject: [PATCH 10/11] add link to new pattern to README --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 50d32793b..aaacba9e8 100644 --- a/README.md +++ b/README.md @@ -72,6 +72,7 @@ The below lists all known patterns. They are grouped into three [maturity levels * [Assisted Compliance](patterns/1-initial/assisted_compliance.md) - *Helping repo owners be compliant by writing their CONTRIBUTING.md for them as a pull request.* * [Open Source Trumps InnerSource](patterns/1-initial/open-source-trumps-innersource.md) - *Developers disregard InnerSource projects because they consider open source projects to be superior. Introducing a required evaluation of InnerSource projects before choosing an open source project increases the likelihood of the InnerSource projects to be adopted.* * [Transparent Governance Levels](patterns/1-initial/governance-levels.md) - *There are projects in multiple stages of InnerSource adoption. Contributors get confused when working with projects that are at different stages.* +* [InnerSource Guidance Group](patterns/1-initial/innersource-guidance-group.md) - *A highly divergent set of development standards in different teams can slow down collaboration betweens these teams. A InnerSource Guidance Group that establishes broad governance and behavioral guidelines can help to reduce these frictions.* #### Donuts (needing a solution) From 6e13e313e31296aad94a5f7299493db47a68da2a Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 13 Feb 2021 13:50:06 +0100 Subject: [PATCH 11/11] Moving block to Known Instances --- patterns/1-initial/innersource-guidance-group.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/patterns/1-initial/innersource-guidance-group.md b/patterns/1-initial/innersource-guidance-group.md index a299eff0d..624636aba 100644 --- a/patterns/1-initial/innersource-guidance-group.md +++ b/patterns/1-initial/innersource-guidance-group.md @@ -46,15 +46,11 @@ TBD ## Known Instances -TBD +- A large, highly regulated, financial organization is planning to implement a TC Steering Group to provide broad guidelines and guard rails as part of their InnerSource initiative. ## Rationale -Empowering TC's as representatives on behalf of their teams propagates ownership of the overall InnerSource strategy as it deploys and evolves in an organization and ensures that a baseline level of governance and standardization occurs. - -May mention: - -- A large, highly regulated, financial organization is planning to implement a TC Steering Group to provide broad guidelines and guard rails as part of their InnerSource initiative. +Empowering Trusted Committers as representatives on behalf of their teams propagates ownership of the overall InnerSource strategy as it deploys and evolves in an organization and ensures that a baseline level of governance and standardization occurs. ## Author(s)