Mention how Siemens applies some patterns (#801)

fgreinacher · nejch · spier · web-flow · commit 4472c6d71ff4 · 2025-03-25T10:25:06.000+01:00
* Mention how Siemens applies some InnerSource patterns

---------

Signed-off-by: Florian Greinacher &lt;florian.greinacher@siemens.com&gt;
Co-authored-by: Nejc Habjan &lt;nejc.habjan@siemens.com&gt;
Co-authored-by: Sebastian Spier &lt;github@spier.hu&gt;
diff --git a/patterns/1-initial/innersource-ambassador.md b/patterns/1-initial/innersource-ambassador.md
@@ -65,6 +65,7 @@ The rewards for the ambassadors will vary by individual motivations. Rewards tha
 
 - *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
 
diff --git a/patterns/2-structured/base-documentation.md b/patterns/2-structured/base-documentation.md
@@ -133,6 +133,7 @@ started right away: [README-template.md](templates/README-template.md),
 * 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
 
diff --git a/patterns/2-structured/communication-tooling.md b/patterns/2-structured/communication-tooling.md
@@ -77,6 +77,7 @@ to a lower need to repeat explanations.
 * 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
 
diff --git a/patterns/2-structured/document-your-guiding-principles.md b/patterns/2-structured/document-your-guiding-principles.md
@@ -124,6 +124,7 @@ All Trusted Committers of a project are published.
 * 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
 
diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md
@@ -55,6 +55,7 @@ The license simplifies the conversations within our organization about sharing s
 - **Robert Bosch GmbH**
 - **Airbus**
 - **GovTech (Singapore Government)**
+- **Siemens** has developed their own InnerSource license alongside other necessary legal agreements between subsidiaries.
 
 ### DB Systel
 
diff --git a/patterns/2-structured/innersource-portal.md b/patterns/2-structured/innersource-portal.md
@@ -108,6 +108,7 @@ It is a good solution for a portal with a few dozen projects, though.
 * **Mercado Libre** use an instance of the [SAP portal](https://github.com/SAP/project-portal-for-innersource) to discover existing InnerSource projects within the organization.
 * **Mercedes-Benz** is [using](https://opensource.mercedes-benz.com/news/sponsor_innersource_commonsoss) the SAP reference implementation mentioned above for their InnerSource Portal.
 * **WellSky** has a simple _Confluence Wiki_ page were InnerSource and reusable projects are listed.
+* **Siemens** has set up an internal portal that provides documentation for InnerSource maintainers, contributors, users and their managers. It also serves as an entry point to explore available projects and gives hints to improve project visibility.
 
 ## References
 
diff --git a/patterns/2-structured/issue-tracker.md b/patterns/2-structured/issue-tracker.md
@@ -50,6 +50,7 @@ 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.
 
 ## Authors
 
diff --git a/patterns/2-structured/praise-participants.md b/patterns/2-structured/praise-participants.md
@@ -73,6 +73,7 @@ Overdoing it may feel insincere and mechanical and defeat your purpose in reachi
 
 * 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
 
diff --git a/patterns/2-structured/repository-activity-score.md b/patterns/2-structured/repository-activity-score.md
@@ -116,6 +116,7 @@ The repository activity score is a simple calculation based on the GitHub API. I
 
 * 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
 
diff --git a/patterns/2-structured/start-as-experiment.md b/patterns/2-structured/start-as-experiment.md
@@ -55,6 +55,7 @@ Finally, starting as an experiment makes it much easier to sidestep regulations
 
 - 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
 
