InnerSourceCommons · spier · Mar 25, 2025 · Mar 25, 2025
@@ -63,9 +63,9 @@ The rewards for the ambassadors will vary by individual motivations. Rewards tha
 
 ## Known Instances
 
-- *SAP* has a concept called [Open Source Champions](https://community.sap.com/t5/open-source-blogs/sap-open-source-champions/ba-p/13539587) that seems related
-- [WellSky](https://wellsky.com/) has the analogous concept of InnerSource Champions representing each business area of the company.
-- *Siemens* has 70 Social Coding Ambassadors from across subsidiaries and countries that promote the Open and InnerSource mindset across the company.
+- **SAP** has a concept called [Open Source Champions](https://community.sap.com/t5/open-source-blogs/sap-open-source-champions/ba-p/13539587) that seems related
+- **[WellSky](https://wellsky.com/)** has the analogous concept of InnerSource Champions representing each business area of the company.
+- **Siemens** has 70 Social Coding Ambassadors from across subsidiaries and countries that promote the Open and InnerSource mindset across the company.
 
 ## Status
 

@@ -46,10 +46,10 @@ In addition it helps to provide clear [contribution guidelines](./base-documenta
 
 ## Known Instances
 
-- This was tried and proven successful at PayPal.
-- GitHub internally uses this pattern with a modified warranty timeline of 6 weeks.
-- Microsoft recommends this pattern as a principle - teams set their own specific time target matching their needs and confidence.
-- SAP leverages this pattern in their InnerSource-based Everest project to transform collaboration, ensuring contributions are not just accepted but also supported, enhancing trust and driving forward the culture of shared responsibility and innovation. See: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
+- **PayPal** Tried this and it was proven successful.
+- **GitHub** internally uses this pattern with a modified warranty timeline of 6 weeks.
+- **Microsoft** recommends this pattern as a principle - teams set their own specific time target matching their needs and confidence.
+- **SAP** leverages this pattern in their InnerSource-based Everest project to transform collaboration, ensuring contributions are not just accepted but also supported, enhancing trust and driving forward the culture of shared responsibility and innovation. See: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
 
 ## Authors
 

@@ -128,12 +128,12 @@ started right away: [README-template.md](templates/README-template.md),
 
 ## Known Instances
 
-* Europace AG - See blog post [InnerSource: Adding base documentation](https://tech.europace.de/post/innersource-base-documentation/)
-* Paypal Inc.
-* Mercado Libre - create a documentation site that contains how to get started with InnerSource and also define the basic artifacts that a repository must have to be InnerSource (README, CONTRIBUTING, CODING_GUIDELINES, etc).
-* Analog Devices Inc.
-* Airbus
-* Siemens automatically creates a checklist issue for every new InnerSource project to make maintainers aware of mandatory requirements (e.g. business approval, license & copyright, export control, contributing guidelines, maintainer maturity) as well as best practices (e.g. documentation as code, semantic versioning, continuous integration/deployment).
+* **Europace AG** - See blog post [InnerSource: Adding base documentation](https://tech.europace.de/post/innersource-base-documentation/)
+* **Paypal Inc.**
+* **Mercado Libre** - create a documentation site that contains how to get started with InnerSource and also define the basic artifacts that a repository must have to be InnerSource (README, CONTRIBUTING, CODING_GUIDELINES, etc).
+* **Analog Devices Inc.**
+* **Airbus**
+* **Siemens** automatically creates a checklist issue for every new InnerSource project to make maintainers aware of mandatory requirements (e.g. business approval, license & copyright, export control, contributing guidelines, maintainer maturity) as well as best practices (e.g. documentation as code, semantic versioning, continuous integration/deployment).
 
 ## Authors
 

@@ -74,10 +74,10 @@ to a lower need to repeat explanations.
 
 ## Known Instances
 
-* Europace AG
-* Paypal Inc.
-* Mercado Libre
-* Siemens makes extensive use of communication channels accessible to all employees for all user questions and discussions around code.siemens.com, InnerSource and Open Source.
+* **Europace AG**
+* **Paypal Inc.**
+* **Mercado Libre**
+* **Siemens** makes extensive use of communication channels accessible to all employees for all user questions and discussions around code.siemens.com, InnerSource and Open Source.
 
 ## Authors
 

@@ -83,7 +83,7 @@ A formal contracting is also beneficial for contributors and communities:
 
 ## Known Instances
 
-- BIOS at Robert Bosch GmbH
+- BIOS at **Robert Bosch GmbH**
 
 ## Status
 

@@ -92,7 +92,7 @@ They will provide a head-and-shoulders improvement in on-the-ground results over
 
 ## Known Instances
 
-* Nike
+* **Nike**
 
 ## Status
 

@@ -58,8 +58,8 @@ Having excellent and dedicated community leaders is a precondition for the succe
 
 ## Known Instances
 
-* _BIOS at Robert Bosch GmbH_. Note that InnerSource at Bosch was, for the majority, aimed at increasing innovation and to a large degree dealt with internal facing products. This pattern is currently not used at Bosch for lack of funding.
-* _Airbus_. A data scientist wanted to improve the collaboration with peers in the group and found: i) many developers (beyond data science) wanted that too and were happy someone was taking care of the issue, and ii) support from line manager and middle management to eventually act as the _de facto_ community leader, on top of his regular line of duty.
+* BIOS at **Robert Bosch GmbH**. Note that InnerSource at Bosch was, for the majority, aimed at increasing innovation and to a large degree dealt with internal facing products. This pattern is currently not used at Bosch for lack of funding.
+* **Airbus**. A data scientist wanted to improve the collaboration with peers in the group and found: i) many developers (beyond data science) wanted that too and were happy someone was taking care of the issue, and ii) support from line manager and middle management to eventually act as the _de facto_ community leader, on top of his regular line of duty.
 
 ## Alias
 

@@ -121,10 +121,10 @@ All Trusted Committers of a project are published.
 
 ## Known Instances
 
-* Europace AG
-* GitHub
-* Robert Bosch GmbH
-* Siemens' InnerSource strategy is built upon the guiding principles of Documentation, Workflow, Transparency, Continuous Integration and Culture which are detailed in their InnerSource portal.
+* **Europace AG**
+* **GitHub**
+* **Robert Bosch GmbH**
+* **Siemens'** InnerSource strategy is built upon the guiding principles of Documentation, Workflow, Transparency, Continuous Integration and Culture which are detailed in their InnerSource portal.
 
 ### Europace AG
 

@@ -60,7 +60,7 @@ When used in combination with the InnerSource Portal pattern, the Gig Marketplac
 ## Known Instances
 
 * A large financial services organization has used the creation of an InnerSource Gig Marketplace website to foster their InnerSource program.
-* SAP implemented the Gig Marketplace pattern - a new InnerSource program was added to the internal job platform where positions and similar offerings can be posted.
+* **SAP** implemented the Gig Marketplace pattern - a new InnerSource program was added to the internal job platform where positions and similar offerings can be posted.
 * The Gig Marketplace pattern has been proven to work extremely well with the associated [InnerSource Portal](./innersource-portal.md) pattern in this context.  The InnerSource Portal increases awareness of specific projects currently underway while the Gig Marketplace advertises tasks of a certain type available to be worked on within those projects.
 
 ## Status

@@ -141,9 +141,9 @@ The same levels make sense inside of organizations.
 
 ## Known Instances
 
-- BBC - referenced in this talk: [Ownership in a DevOps and InnerSource environment - Tom Sadler (BBC)](https://www.youtube.com/watch?v=O8TK7QG3FjM)
-- Flutter Entertainment
-- Europace AG
+- **BBC** - referenced in this talk: [Ownership in a DevOps and InnerSource environment - Tom Sadler (BBC)](https://www.youtube.com/watch?v=O8TK7QG3FjM)
+- **Flutter Entertainment**
+- **Europace AG**
 
 ### Flutter Entertainment
 

@@ -69,7 +69,7 @@ Feeling part of a group and being given some structure and responsibility genera
 
 ## Known Instances
 
-* WellSky
+* **WellSky**
 
 ## Status
 

@@ -49,8 +49,8 @@ development but also during the planning phase of new features:
 
 ## Known Instances
 
-* Europace AG - See blog post [Issue Use Cases](https://tech.europace.de/post/using-issues-for-asking-questions-and-tracking-work/)
-* Siemens manages work on their InnerSource Platform in a fully transparent way. Therefore the work on the InnerSource Platform itself is organized as an InnerSource project. This includes tracking enhancements and bugs, as well as marketing, communication activities and support requests from users.
+* **Europace AG** - See blog post [Issue Use Cases](https://tech.europace.de/post/using-issues-for-asking-questions-and-tracking-work/)
+* **Siemens** manages work on their InnerSource Platform in a fully transparent way. Therefore the work on the InnerSource Platform itself is organized as an InnerSource project. This includes tracking enhancements and bugs, as well as marketing, communication activities and support requests from users.
 
 ## Authors
 

@@ -210,10 +210,10 @@ long term.
 
 ## Known Instances
 
-* Entelgy
-* Zylk
-* Bitergia
-* Airbus
+* **Entelgy**
+* **Zylk**
+* **Bitergia**
+* **Airbus**
 
 ## Authors
 

@@ -71,9 +71,9 @@ Overdoing it may feel insincere and mechanical and defeat your purpose in reachi
 
 ## Known Instances
 
-* Nike (multiple projects)
-* SAP - InnerSource initiatives like the Dojo and Everest projects are elevated by the 'Praise Participants' pattern, where the SAP Appreciate program plays a key role in fostering a culture of gratitude and recognition, driving innovation and collaboration to new heights. See: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
-* Siemens awards successful InnerSource projects and contributors at their yearly internal InnerSource Summit.
+* **Nike** (multiple projects)
+* **SAP** - InnerSource initiatives like the Dojo and Everest projects are elevated by the 'Praise Participants' pattern, where the SAP Appreciate program plays a key role in fostering a culture of gratitude and recognition, driving innovation and collaboration to new heights. See: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
+* **Siemens** awards successful InnerSource projects and contributors at their yearly internal InnerSource Summit.
 
 ## Status
 

@@ -57,8 +57,8 @@ Release notes are also a great opportunity to [praise participants](praise-parti
 
 ## Known Instances
 
-* Comcast (multiple projects)
-* GitHub (multiple projects)
+* **Comcast** (multiple projects)
+* **GitHub** (multiple projects)
 
 ## Authors
 

@@ -114,9 +114,9 @@ The repository activity score is a simple calculation based on the GitHub API. I
 
 ## Known Instances
 
-* Used in SAP's InnerSource project portal to define the default order of the InnerSource projects. It was first created in July 2020 and is fine-tuned and updated frequently ever since. When proposed to the InnerSource Commons in July 2020, this pattern emerged. Also see [Michael Graf & Harish B (SAP) at ISC.S11 - The Unexpected Path of Applying InnerSource Patterns](https://www.youtube.com/watch?v=6r9QOw9dcQo&list=PLCH-i0B0otNQZQt_QzGR9Il_kE4C6cQRy&index=6).
-* Airbus took a lot of inspiration from this pattern to create an "InnerSource score" that combines the activity score together with checks from the [Standard Base Documentation](./base-documentation.md) and the [InnerSource License](./innersource-license.md).
-* Siemens includes repository activity in their InnerSource project quality score. Maintainers can use the quality score to improve their project and communicate their score via badges.
+* **SAP** - Used in SAP's InnerSource project portal to define the default order of the InnerSource projects. It was first created in July 2020 and is fine-tuned and updated frequently ever since. When proposed to the InnerSource Commons in July 2020, this pattern emerged. Also see [Michael Graf & Harish B (SAP) at ISC.S11 - The Unexpected Path of Applying InnerSource Patterns](https://www.youtube.com/watch?v=6r9QOw9dcQo&list=PLCH-i0B0otNQZQt_QzGR9Il_kE4C6cQRy&index=6).
+* **Airbus** took a lot of inspiration from this pattern to create an "InnerSource score" that combines the activity score together with checks from the [Standard Base Documentation](./base-documentation.md) and the [InnerSource License](./innersource-license.md).
+* **Siemens** includes repository activity in their InnerSource project quality score. Maintainers can use the quality score to improve their project and communicate their score via badges.
 
 ## Status
 

@@ -41,7 +41,7 @@ Company A wants to introduce its first InnerSource initiative. Most managers in
 
 ## Known Instances
 
-* BIOS at Robert Bosch GmbH (in the early stages of adoption, only - 2009-2012)
+* BIOS at **Robert Bosch GmbH** (in the early stages of adoption, only - 2009-2012)
 
 ## Status
 

@@ -72,9 +72,9 @@ Related to this pattern is the [30 Day Warranty](30-day-warranty.md) pattern tha
 
 ## Known Instances
 
-* Europace AG
-* Flutter Entertainment: A [Flutter InnerSource application](https://innersource.flutter.com/sdlc/) has a shared code "service" repository with cross-team contribution and CI pipeline to build and publish a shared release artifact. Each adopting team has a "deployment config" repository defining their own deployment. This is driven by varying regulatory requirements, service and incident management practices and infrastructure skill sets in different areas of the business.
-* WellSky (see [Continuous InnerSource in Production - 5 Times](https://www.youtube.com/watch?v=loSTj4yIG9Q&pp=ygUkY29udGludW91cyBpbm5lcnNvdXJjZSBpbiBwcm9kdWN0aW9u))
+* **Europace AG**
+* **Flutter Entertainment**: A [Flutter InnerSource application](https://innersource.flutter.com/sdlc/) has a shared code "service" repository with cross-team contribution and CI pipeline to build and publish a shared release artifact. Each adopting team has a "deployment config" repository defining their own deployment. This is driven by varying regulatory requirements, service and incident management practices and infrastructure skill sets in different areas of the business.
+* **WellSky** (see [Continuous InnerSource in Production - 5 Times](https://www.youtube.com/watch?v=loSTj4yIG9Q&pp=ygUkY29udGludW91cyBpbm5lcnNvdXJjZSBpbiBwcm9kdWN0aW9u))
 
 ## Status
 

@@ -53,9 +53,9 @@ Finally, starting as an experiment makes it much easier to sidestep regulations
 
 ## Known Instances
 
-- Robert Bosch GmbH (globally distributed software development)
-- Airbus: the data science community collaborated on shared Python libraries that eventually lead to a group-wide InnerSource scheme for any software.
-- Siemens started their [InnerSource Platform](https://about.gitlab.com/customers/siemens/) code.siemens.com from a single department with a few hundred users. Over the years they scaled it to a company-wide service with 50,000 active users.
+- **Robert Bosch GmbH** (globally distributed software development)
+- **Airbus**: the data science community collaborated on shared Python libraries that eventually lead to a group-wide InnerSource scheme for any software.
+- **Siemens** started their [InnerSource Platform](https://about.gitlab.com/customers/siemens/) code.siemens.com from a single department with a few hundred users. Over the years they scaled it to a company-wide service with 50,000 active users.
 
 ## Status
 

@@ -123,12 +123,10 @@ there is a plan for responsible stewardship.
 
 ## Known Instances
 
-This has been tried and proven successful at:
-
-- Nike
-- PayPal
-- Mercado Libre - adds a section in the `CONTRIBUTING.md` file to inform who the Trusted Committers are.
-- Robert Bosch GmbH - we didn't call the role 'Trusted Committer' but we had this role at the beginning of our InnerSource journey. Trusted Committers would be funded for 100 % of their time to be able to focus on this role.
+- **Nike**
+- **PayPal**
+- **Mercado Libre** - adds a section in the `CONTRIBUTING.md` file to inform who the Trusted Committers are.
+- **Robert Bosch GmbH** - we didn't call the role 'Trusted Committer' but we had this role at the beginning of our InnerSource journey. Trusted Committers would be funded for 100 % of their time to be able to focus on this role.
 
 ![Trusted Committer section in CONTRIBUTING.md of Mercado Libre](../../assets/img/mercadolibre-trusted-committers.png "Trusted Committer section in CONTRIBUTING.md of Mercado Libre")
-Original file line number
+Diff line change
@@ Expand Up @@
     ## Known Instances
-    * Nike
+    * **Nike**
     ## Status
@@ Expand Down @@