Add Thales Group as Known Instance across five patterns

patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md

@@ -68,7 +68,7 @@ Developers are not motivated to contribute to InnerSource because organizational
 
 ## Known Instances
 
-TBD
+* **Thales Group** - InnerSource contributions are a formal part of the expert career path at Thales. The Thales ISPO positioned InnerSource participation as demonstrable proof of leadership and technical expertise, which engineers can reference when seeking promotion to senior or expert levels. The rationale: an engineer who finds time to contribute to InnerSource projects on top of their operational commitments has demonstrated exactly the kind of initiative and cross-team collaboration that defines senior expertise. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).
 
 ## Status  
 

patterns/1-initial/innersource-ambassador.md

@@ -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 "Community Leaders." Each Community Leader owns an InnerSource community within their business 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
 

patterns/2-structured/innersource-hackathon.md

@@ -104,6 +104,7 @@
 ## Known Instances
 
 * **IKEA** (Ingka Group)
+* **Thales Group** integrates a hackathon into their annual "Tales I Days" — a full-day, in-person event combining conference talks, a formal awards ceremony for top contributors, and a hands-on hackathon on the corporate software factory (GitLab-based). The hackathon is specifically designed for engineers new to InnerSource, giving them a structured, low-risk environment to practice on real internal platforms alongside experienced practitioners. Managers and non-engineering staff such as procurement and hardware engineers also attend the conference portion, broadening InnerSource awareness beyond software development. 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

patterns/2-structured/innersource-license.md

@@ -57,6 +57,7 @@
 - **GovTech (Singapore Government)**
 - **Siemens** has developed their own InnerSource license alongside other necessary legal agreements between subsidiaries.
 - **Mercedes-Benz**
+- **Thales Group**
 
 ### DB Systel
 
@@ -88,6 +89,10 @@
 
 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. The licenses are made available to any InnerSource participant within the group at no cost — removing the per-project negotiation overhead that would otherwise slow code sharing across Thales's many business lines and global entities. The legal framework is one of two foundational pillars of the Thales InnerSource strategy, complementing the technical enabler (a corporate software factory based on GitLab). 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

patterns/2-structured/praise-participants.md

@@ -74,6 +74,7 @@
 * **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, calling out contributors in the moment and amplifying recognition at the annual "Tales I Days" event, where top contributors and community advocates across InnerSource and open source receive formal awards. Thales also extended the pattern by tying InnerSource contribution to the expert career path as proof of leadership and expertise. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis).
 
 ## Status