Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ Developers are not motivated to contribute to InnerSource because organizational

## Known Instances

TBD
* **Thales Group** - InnerSource contributions are part of the expert career path at Thales. The Thales ISPO positioned InnerSource participation as demonstrable proof of leadership and expertise, which engineers can reference when seeking the expert career path. The rationale: building communities around specific topics on top of their operational commitments demonstrates leadership and recognised expertise on those topics. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).

## Status

Expand Down
1 change: 1 addition & 0 deletions patterns/1-initial/innersource-ambassador.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,7 @@ Here some examples from the commercial domain, academia and open source:
- **[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.
- **Robert Bosch GmbH** has the analogous concept of *Social Coding Advocates*.
- **Thales Group** calls these representatives "Steering Board members." Each Community Leader represents an InnerSource community within their organizational unit and meets quarterly with the Thales ISPO in a "Steering Board" session to surface blockers and emerging needs from the field. The ISPO carries these inputs to the executive sponsorship board, creating a structured bottom-up/top-down governance loop. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).

## Status

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/innersource-hackathon.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,7 @@ All these help scale InnerSource in the organization.
## Known Instances

* **IKEA** (Ingka Group)
* **Thales Group** - Thales I/O Days combine a full remote 2-day Hackathon and annual in-person conference with a reward ceremony for key contributors — open to all job families, not only engineering. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).
* **The Aerospace Corporation** organized an internal InnerSource contribution festival inspired by open source contribution festivals at conferences like KubeCon/CloudNativeCon. Aerospace is a Federally Funded Research and Development Center (FFRDC) where developers charge time to government contracts, making InnerSource adoption especially challenging because work not embedded in funded tasking does not happen. The event was organized by a software best practices team and held as a hybrid event (virtual and in-person in El Segundo, California). They secured dedicated funding so that all 31 participants across 21 departments could charge their time to the event. Tasks were prepared with project maintainers, documented with clear definitions of done and impact statements, and organized on task boards. At least one maintainer from every participating project was available for Q&A throughout the day. During and shortly after the event, 15 tickets were closed. Notably, one developer used the event to contribute a feature he needed back to an internal library rather than forking it — a direct demonstration of InnerSource solving the "fork storm" problem the company had been experiencing. Two-thirds of participants had never heard of InnerSource before the event, yet 100% of survey respondents agreed that InnerSource would have a positive impact on development and wanted to participate in a future event. Traffic to the company's internal documentation site nearly doubled in the month following the event. See: [Kickstarting InnerSource with a Contribfest](https://www.youtube.com/watch?v=J5KeCHFbnWA) (InnerSource Commons Summit 2025 talk by Trin Baumgarten and Caroline T Jones).

## Status
Expand Down
5 changes: 5 additions & 0 deletions patterns/2-structured/innersource-license.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ The license simplifies the conversations within our organization about sharing s
- **GovTech (Singapore Government)**
- **Siemens** has developed their own InnerSource license alongside other necessary legal agreements between subsidiaries.
- **Mercedes-Benz**
- **Thales Group**

### DB Systel

Expand Down Expand Up @@ -88,6 +89,10 @@ Following open source practices, the GPSL `LICENSE` file is included in each rep

For more details see the InnerSource Commons Community call from 09/2023 [Improving Engineering Collaboration across the Singapore Government through InnerSource](https://www.youtube.com/watch?v=-zu2X2iERv8&t=1257s&ab_channel=InnerSourceCommons) (around 20:50) by Hunter Nield.

### Thales Group

Thales Group created a framework of four ready-to-use InnerSource licenses, developed in close collaboration with legal partners. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).

## Status

* Structured
Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/praise-participants.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,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.
* **Thales Group** - The Thales ISPO explicitly applies this pattern organization-wide, during "Thales I/O Days" event, where top contributors and community advocates across InnerSource and open source receive awards. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).

## Status

Expand Down
Loading