Skip to content

Mention how Siemens applies some patterns #801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 25, 2025
Merged

Mention how Siemens applies some patterns #801

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e549bc5
Mention how Siemens applies some patterns
fgreinacher Mar 20, 2025
7fcfcd8
Remove misleading link and split sentence
fgreinacher Mar 25, 2025
6978c87
Highlight dog fooding more
fgreinacher Mar 25, 2025
d2dac9f
Elaborate on checklist
fgreinacher Mar 25, 2025
e9a865c
Move ambassadors
fgreinacher Mar 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions patterns/2-structured/base-documentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 as well as best practices.

## Authors

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/communication-tooling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/dedicated-community-leader.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ Having excellent and dedicated community leaders is a precondition for the succe

* _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.
* _Siemens_ has 70 Social Coding Ambassadors from across subsidiaries and countries that promote the Open and InnerSource mindset across the company.

## Alias

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/document-your-guiding-principles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/innersource-license.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/innersource-portal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you comfortable sharing which tooling you are using for this? e.g. is it Backstage, a custom built site, something else?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the documentation portal we are using MkDocs in combination with our internal docs-theme we maintain (reused > 2400 times, also Inner Source). But we also have a dedicated app using Django and another popular innersource framework for the UI, there we have detailed re-use metrics and do also calculate the re-use, usage, quality metric and much more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the additional info @bufferoverflow. The measurement of re-use could even be a pattern in its own right but lets keep that for another day :) (I made a note of that)

How do you list the InnerSource projects? Do you just use the features of your gitlab instance to do that, or is there a dedicated places that shows InnerSource projects only?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're listing inner source projects on a dedicated page, also including additional data mentioned by @bufferoverflow above.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The measurement of re-use could even be a pattern in its own right but lets keep that for another day :) (I made a note of that)

@spier Yes, I think that would be worth to do. It's especially useful for reporting and if people see the numbers of re-use they could imagine the savings we had due to re-use Inner Source. This really helps to convince people.


## References

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/issue-tracker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/praise-participants.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/repository-activity-score.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/start-as-experiment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down