From 29a0949ec6857bfed12a8bbf37a90a901bb29033 Mon Sep 17 00:00:00 2001 From: Russ Rutledge Date: Wed, 20 May 2026 16:28:36 -0500 Subject: [PATCH 01/12] Add Thales Group as Known Instance across five patterns Based on Marius Moulis's InnerSource Commons talk "Why People Matter Most: Building a Sustainable InnerSource Strategy" (May 2026), Thales Group's 10-year ISPO experience is added as a Known Instance to: - Praise Participants: Thales applies the pattern explicitly, with formal awards at the annual "Tales I Days" event - Developer Incentive Alignment: InnerSource on the expert career path as proof of leadership/expertise (replaces "TBD" Known Instances) - InnerSource Ambassadors: Thales "Community Leaders" / quarterly Steering Board as a structured bottom-up/top-down governance loop - InnerSource Hackathon: Tales I Days combines hackathon + conference + awards in one annual in-person event - InnerSource License: Thales's framework of four ready-to-use licenses developed with legal partners Co-Authored-By: Claude Sonnet 4.6 --- ...loper-incentive-alignment-for-innersource-contribution.md | 2 +- patterns/1-initial/innersource-ambassador.md | 1 + patterns/2-structured/innersource-hackathon.md | 1 + patterns/2-structured/innersource-license.md | 5 +++++ patterns/2-structured/praise-participants.md | 1 + 5 files changed, 9 insertions(+), 1 deletion(-) diff --git a/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md b/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md index b0827dc4c..6693b6b3f 100644 --- a/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md +++ b/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 diff --git a/patterns/1-initial/innersource-ambassador.md b/patterns/1-initial/innersource-ambassador.md index cbb9e9931..17901937e 100644 --- a/patterns/1-initial/innersource-ambassador.md +++ b/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 diff --git a/patterns/2-structured/innersource-hackathon.md b/patterns/2-structured/innersource-hackathon.md index 2f11878be..8d7ff05cd 100644 --- a/patterns/2-structured/innersource-hackathon.md +++ b/patterns/2-structured/innersource-hackathon.md @@ -104,6 +104,7 @@ All these help scale InnerSource in the organization. ## 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 diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md index 981c4f9cb..1fc708545 100644 --- a/patterns/2-structured/innersource-license.md +++ b/patterns/2-structured/innersource-license.md @@ -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 @@ -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. 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 diff --git a/patterns/2-structured/praise-participants.md b/patterns/2-structured/praise-participants.md index 7836f815b..bd7224598 100644 --- a/patterns/2-structured/praise-participants.md +++ b/patterns/2-structured/praise-participants.md @@ -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, 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 From bd9e618f2543a8edcff4df6a6f2de2ff39441e46 Mon Sep 17 00:00:00 2001 From: rrrutledge Date: Wed, 27 May 2026 14:11:13 -0500 Subject: [PATCH 02/12] Apply suggestion from @rrrutledge --- patterns/2-structured/praise-participants.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/2-structured/praise-participants.md b/patterns/2-structured/praise-participants.md index bd7224598..3b2185356 100644 --- a/patterns/2-structured/praise-participants.md +++ b/patterns/2-structured/praise-participants.md @@ -74,7 +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, 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). +* **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/O 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 From 72dba0843dcc480c621c6e47490c5b6e0a8307fd Mon Sep 17 00:00:00 2001 From: Russ Rutledge Date: Fri, 29 May 2026 12:55:05 -0500 Subject: [PATCH 03/12] Address PR feedback from Marius on Thales Known Instances - Fix "Tales I Days" typo -> "Thales I/O Days" in hackathon and praise-participants - Clarify hackathon entry: full remote 2-day hackathon + in-person conference, awards open to all job families - Remove "at no cost" from innersource-license Thales entry Co-Authored-By: Claude Sonnet 4.6 --- patterns/2-structured/innersource-hackathon.md | 2 +- patterns/2-structured/innersource-license.md | 2 +- patterns/2-structured/praise-participants.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/patterns/2-structured/innersource-hackathon.md b/patterns/2-structured/innersource-hackathon.md index 8d7ff05cd..2e1b48fe4 100644 --- a/patterns/2-structured/innersource-hackathon.md +++ b/patterns/2-structured/innersource-hackathon.md @@ -104,7 +104,7 @@ All these help scale InnerSource in the organization. ## 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). +* **Thales Group** - Thales I/O Days combine a full remote 2-day Hackathon and an annual in-person conference with an award ceremony open to all job families, not only engineering. 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 on the corporate software factory (GitLab-based). The in-person conference and awards portion broadens InnerSource awareness beyond software development, with attendance from managers and non-engineering staff such as procurement and hardware engineers. 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 diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md index 1fc708545..9bda2180d 100644 --- a/patterns/2-structured/innersource-license.md +++ b/patterns/2-structured/innersource-license.md @@ -91,7 +91,7 @@ For more details see the InnerSource Commons Community call from 09/2023 [Improv ### 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). +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, 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 diff --git a/patterns/2-structured/praise-participants.md b/patterns/2-structured/praise-participants.md index 3b2185356..619dc1d67 100644 --- a/patterns/2-structured/praise-participants.md +++ b/patterns/2-structured/praise-participants.md @@ -74,7 +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, calling out contributors in the moment and amplifying recognition at the annual "Tales I/O 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). +* **Thales Group** - The Thales ISPO explicitly applies this pattern organization-wide, calling out contributors in the moment and amplifying recognition at the annual "Thales I/O 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 From 81a2d310df025ca3a29144fd9849ecadb2280953 Mon Sep 17 00:00:00 2001 From: Russ Rutledge Date: Fri, 29 May 2026 13:01:35 -0500 Subject: [PATCH 04/12] Improve grammar and sentence structure of Thales hackathon entry Co-Authored-By: Claude Sonnet 4.6 --- patterns/2-structured/innersource-hackathon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/2-structured/innersource-hackathon.md b/patterns/2-structured/innersource-hackathon.md index 2e1b48fe4..9bf08baed 100644 --- a/patterns/2-structured/innersource-hackathon.md +++ b/patterns/2-structured/innersource-hackathon.md @@ -104,7 +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 an annual in-person conference with an award ceremony open to all job families, not only engineering. 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 on the corporate software factory (GitLab-based). The in-person conference and awards portion broadens InnerSource awareness beyond software development, with attendance from managers and non-engineering staff such as procurement and hardware engineers. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis). +* **Thales Group** - The annual Thales I/O Days event combines a fully remote, two-day hackathon with an in-person conference and award ceremony open to all job families, not just engineering. The hackathon is designed for engineers new to InnerSource, offering a structured, low-risk environment to contribute to real internal platforms alongside experienced practitioners on the corporate software factory (GitLab-based). The in-person conference and awards ceremony broaden InnerSource awareness beyond software development, drawing attendance from managers and non-engineering staff such as those in procurement and hardware 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 From 836af30b453f32c25d07cbcc600d2fcb22ff15e7 Mon Sep 17 00:00:00 2001 From: Russ Rutledge Date: Mon, 15 Jun 2026 10:34:00 -0500 Subject: [PATCH 05/12] Incorporate Marius's Jun 11 review feedback across five patterns Updates Thales known instances per Marius Moulis's corrections: - developer-incentive-alignment: use his exact wording for the career path rationale - innersource-ambassador: rename "Community Leaders" to "Steering Board members", "business unit" to "organizational unit" - innersource-hackathon: "reward ceremony for key contributors" (not "award ceremony"), shorter description - innersource-license: trim to his shorter approved text - praise-participants: remove the career-path cross-reference, shorten to his approved text Co-Authored-By: Claude Sonnet 4.6 (1M context) --- ...eveloper-incentive-alignment-for-innersource-contribution.md | 2 +- patterns/1-initial/innersource-ambassador.md | 2 +- patterns/2-structured/innersource-hackathon.md | 2 +- patterns/2-structured/innersource-license.md | 2 +- patterns/2-structured/praise-participants.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md b/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md index 6693b6b3f..1a51c0494 100644 --- a/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md +++ b/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 -* **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). +* **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 diff --git a/patterns/1-initial/innersource-ambassador.md b/patterns/1-initial/innersource-ambassador.md index 17901937e..b5a683b84 100644 --- a/patterns/1-initial/innersource-ambassador.md +++ b/patterns/1-initial/innersource-ambassador.md @@ -76,7 +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). +- **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 diff --git a/patterns/2-structured/innersource-hackathon.md b/patterns/2-structured/innersource-hackathon.md index 9bf08baed..c9333c0ea 100644 --- a/patterns/2-structured/innersource-hackathon.md +++ b/patterns/2-structured/innersource-hackathon.md @@ -104,7 +104,7 @@ All these help scale InnerSource in the organization. ## Known Instances * **IKEA** (Ingka Group) -* **Thales Group** - The annual Thales I/O Days event combines a fully remote, two-day hackathon with an in-person conference and award ceremony open to all job families, not just engineering. The hackathon is designed for engineers new to InnerSource, offering a structured, low-risk environment to contribute to real internal platforms alongside experienced practitioners on the corporate software factory (GitLab-based). The in-person conference and awards ceremony broaden InnerSource awareness beyond software development, drawing attendance from managers and non-engineering staff such as those in procurement and hardware engineering. See: [Why People Matter Most: Building a Sustainable InnerSource Strategy](https://www.youtube.com/watch?v=r0dx84lUDYY) (InnerSource Commons, 2026, by Marius Moulis). +* **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 diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md index 9bda2180d..0aa3ef635 100644 --- a/patterns/2-structured/innersource-license.md +++ b/patterns/2-structured/innersource-license.md @@ -91,7 +91,7 @@ For more details see the InnerSource Commons Community call from 09/2023 [Improv ### 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, 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). +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 diff --git a/patterns/2-structured/praise-participants.md b/patterns/2-structured/praise-participants.md index 619dc1d67..95b078188 100644 --- a/patterns/2-structured/praise-participants.md +++ b/patterns/2-structured/praise-participants.md @@ -74,7 +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, calling out contributors in the moment and amplifying recognition at the annual "Thales I/O 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). +* **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 From 7a84fd51529ac9b204a87e68c067d8a93753f5e6 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Wed, 17 Jun 2026 07:27:12 +0200 Subject: [PATCH 06/12] Exclude MD060 markdownlint check. This has never failed in the pust, so must be some configuration drift. --- .markdownlint.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.markdownlint.json b/.markdownlint.json index 662a01cc2..282ad77b8 100644 --- a/.markdownlint.json +++ b/.markdownlint.json @@ -13,5 +13,6 @@ "MD034": false, "MD036": false, "MD040": false, - "MD041": false + "MD041": false, + "MD060": false } \ No newline at end of file From 7ba91d718f4f8b15e32a6bb43a7c346e02c1fc8d Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Wed, 17 Jun 2026 07:33:46 +0200 Subject: [PATCH 07/12] Fix some links, as reported by the GHA Link Checker --- ...oper-incentive-alignment-for-innersource-contribution.md | 6 +++--- patterns/2-structured/innersource-license.md | 2 +- translation/es/patterns/innersource-license.md | 2 +- translation/gl/patterns/innersource-license.md | 2 +- translation/ja/patterns/innersource-license.md | 2 +- translation/pt-br/patterns/innersource-license.md | 2 +- translation/zh/patterns/innersource-license.md | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md b/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md index 1a51c0494..b48b3d73d 100644 --- a/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md +++ b/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md @@ -16,7 +16,7 @@ Developers are not motivated to contribute to InnerSource because organizational ## Context -* There is a need to foster team-centric behaviour and limit instances of [ego-driven development](http://deliberate-software.com/ego-driven-development/) or idolizing a 'star developer.' +* There is a need to foster team-centric behavior and limit instances of [ego-driven development](https://deliberate-software.com/ego-driven-development/) or idolizing a 'star developer.' * There are multiple developers within the organization or business unit with the same or related areas of expertise, such as front-end development, devops, testing, etc. * Mid-to-top level management either do not have a technical background or their technical backgrounds and experiences are many years out of date; organizational emphasis is therefore on quantitative output of development team. * The organization wants to create more alignment between work efforts and external motivation without relying directly on financial rewards or quotas. @@ -26,7 +26,7 @@ Developers are not motivated to contribute to InnerSource because organizational 1. Existing attitudes and developer culture - * Team-centric behaviour is not evident. Developers of all levels tend to focus mostly on their own contributions. When stories are assigned, work is often done ‘locally’ and not pushed up or checked in until the end of the sprint. + * Team-centric behavior is not evident. Developers of all levels tend to focus mostly on their own contributions. When stories are assigned, work is often done ‘locally’ and not pushed up or checked in until the end of the sprint. * Asking developers to push code early and often is met with extreme resistance, accusations of micro-management, or claims that such a practice would slow velocity. * Existing practice commonly leads to duplicated work, missed requirements, or frequent gaps in the software or process. @@ -64,7 +64,7 @@ Developers are not motivated to contribute to InnerSource because organizational * job descriptions include mentorship & contribution language to set expectations up front & make it easier to assess if candidates have requisite skills/experience required * org is retaining and better utilizing existing talent * devs take on professional mentorship responsibilities for their peers rather than leaving it to non-technical management -* career progression clearly identified & understood by engs and management +* career progression clearly identified & understood by engineers and management ## Known Instances diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md index 0aa3ef635..d64fe1727 100644 --- a/patterns/2-structured/innersource-license.md +++ b/patterns/2-structured/innersource-license.md @@ -115,4 +115,4 @@ Thales Group created a framework of four ready-to-use InnerSource licenses, deve - **legal entity** - An entity that has its own legal rights and obligations (synonyms: company, subsidiary) (e.g. Lufthansa Systems GmbH, Lufthansa Industry Solutions TS GmbH, ...) [db-inner-source-license]: https://github.com/dbsystel/open-source-policies/tree/master/inner-source-license -[eupl]: https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12 +[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 \ No newline at end of file diff --git a/translation/es/patterns/innersource-license.md b/translation/es/patterns/innersource-license.md index e59d13bbc..ed1ba9aa5 100644 --- a/translation/es/patterns/innersource-license.md +++ b/translation/es/patterns/innersource-license.md @@ -108,7 +108,7 @@ Para más detalles, vea la llamada de la Comunidad InnerSource Commons de 09/202 - **entidad legal** - Una entidad que tiene sus propios derechos y obligaciones legales (sinónimos: empresa, subsidiaria) (por ejemplo, Lufthansa Systems GmbH, Lufthansa Industry Solutions TS GmbH, ...) [db-inner-source-license]: https://github.com/dbsystel/open-source-policies/tree/master/inner-source-license -[eupl]: https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12 +[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 ## Histórico de Traducciones diff --git a/translation/gl/patterns/innersource-license.md b/translation/gl/patterns/innersource-license.md index 024a19efe..30674ec11 100644 --- a/translation/gl/patterns/innersource-license.md +++ b/translation/gl/patterns/innersource-license.md @@ -88,7 +88,7 @@ Paga a pena mencionar que, ata agora, o software compartido baixo esta licenza I - **Entidade xurídica**: unha entidade que ten os seus propios dereitos e obrigas legais. (Sinónimos: empresa, filial. Por exemplo, Lufthansa Systems GmbH, Lufthansa Industry Solutions TS GmbH etc). [db-inner-source-license]: https://github.com/dbsystel/open-source-policies/tree/master/inner-source-license -[eupl]: https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12 +[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 ## Tradución diff --git a/translation/ja/patterns/innersource-license.md b/translation/ja/patterns/innersource-license.md index 44376f734..75a041c0f 100644 --- a/translation/ja/patterns/innersource-license.md +++ b/translation/ja/patterns/innersource-license.md @@ -90,7 +90,7 @@ DB 社の中で最初の法人(企業) は、このインナーソース ライ - **法的エンティティ** - 独自の法的権利と義務を有するエンティティ (同義語: グループ子会社、子会社、関連会社) (例: Microsoft Japan, GitHub, LinkedIn) [db-inner-source-license]: https://github.com/dbsystel/open-source-policies/tree/master/inner-source-license -[eupl]: https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12 +[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 ## 翻訳の履歴 diff --git a/translation/pt-br/patterns/innersource-license.md b/translation/pt-br/patterns/innersource-license.md index aff5f8f3d..10f4933a8 100644 --- a/translation/pt-br/patterns/innersource-license.md +++ b/translation/pt-br/patterns/innersource-license.md @@ -88,7 +88,7 @@ Vale mencionar que até agora, o software compartilhado sob essa licença InnerS -entidade jurídica - Uma entidade que possui seus próprios direitos e obrigações legais (sinônimos: empresa, subsidiária) (por exemplo, Lufthansa Systems GmbH, Lufthansa Industry Solutions TS GmbH, ...) [db-inner-source-license]: https://github.com/dbsystel/open-source-policies/tree/master/inner-source-license -[eupl]: https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12 +[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 ## Histórico de Tradução diff --git a/translation/zh/patterns/innersource-license.md b/translation/zh/patterns/innersource-license.md index 5fc1eb414..d9ee79322 100644 --- a/translation/zh/patterns/innersource-license.md +++ b/translation/zh/patterns/innersource-license.md @@ -88,7 +88,7 @@ DB AG内部的第一批法律实体（公司）正在使用他们的内源许可 - **法律实体** - 拥有自身的法律权利和义务的实体（同义词：公司，子公司）（例如汉莎系统有限公司，汉莎工业解决方案TS有限公司，...） [db-inner-source-license]: https://github.com/dbsystel/open-source-policies/tree/master/inner-source-license -[eupl]: https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12 +[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 ## 翻译校对 From ec16a7701ba8f64e6ad9188ccfa9c679db927d4e Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Wed, 17 Jun 2026 07:37:17 +0200 Subject: [PATCH 08/12] Fix codeowner specification for the Brazilian Portuguese translation --- .github/CODEOWNERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index f59f70dd7..25faf15ea 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -14,8 +14,8 @@ /book/ja/ @yuhattor /translation/zh/ @WillemJiang /book/zh/ @WillemJiang -/translation/pt/ @jrcosta @zilio -/book/pt/ @jrcosta @zilio +/translation/pt-br/ @jrcosta @zilio +/book/pt-br/ @jrcosta @zilio /pattern-categorization/pt-br/ @jrcosta @zilio /translation/gl/ @psanxiao /book/gl/ @psanxiao From 9a8692d87072cbc929487a570caa6b392dd40721 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Wed, 17 Jun 2026 07:40:00 +0200 Subject: [PATCH 09/12] Fix markdownlint --- patterns/2-structured/innersource-license.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md index d64fe1727..1d31ac84c 100644 --- a/patterns/2-structured/innersource-license.md +++ b/patterns/2-structured/innersource-license.md @@ -115,4 +115,4 @@ Thales Group created a framework of four ready-to-use InnerSource licenses, deve - **legal entity** - An entity that has its own legal rights and obligations (synonyms: company, subsidiary) (e.g. Lufthansa Systems GmbH, Lufthansa Industry Solutions TS GmbH, ...) [db-inner-source-license]: https://github.com/dbsystel/open-source-policies/tree/master/inner-source-license -[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 \ No newline at end of file +[eupl]: https://interoperable-europe.ec.europa.eu/collection/eupl/eupl-text-eupl-12 From 5c39abc3f8055cc5d643b709c17eb4f7447ab0ab Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Wed, 17 Jun 2026 22:15:42 +0200 Subject: [PATCH 10/12] Trying new vale GHA --- .github/workflows/vale.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/vale.yml b/.github/workflows/vale.yml index 0792228cf..d34857448 100644 --- a/.github/workflows/vale.yml +++ b/.github/workflows/vale.yml @@ -21,7 +21,7 @@ jobs: - uses: actions/checkout@v6 - name: Vale Linting - uses: errata-ai/vale-action@v2 + uses: vale-cli/vale-action@v2 with: files: '["patterns/2-structured/", "patterns/3-validated/"]' vale_flags: "--glob=*.md" From b15135e1d558ff61cf3b676d0ccfe7421319faac Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Wed, 17 Jun 2026 22:30:43 +0200 Subject: [PATCH 11/12] Moving custom accept list to the correct folder --- .../{ => .vale-config/styles}/config/vocabularies/Base/accept.txt | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/vale/{ => .vale-config/styles}/config/vocabularies/Base/accept.txt (100%) diff --git a/.github/vale/config/vocabularies/Base/accept.txt b/.github/vale/.vale-config/styles/config/vocabularies/Base/accept.txt similarity index 100% rename from .github/vale/config/vocabularies/Base/accept.txt rename to .github/vale/.vale-config/styles/config/vocabularies/Base/accept.txt From a7504ff1432c9670fe7d86d2acf21ce4f2f0990d Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Wed, 17 Jun 2026 22:50:52 +0200 Subject: [PATCH 12/12] Revert "Moving custom accept list to the correct folder" This reverts commit b15135e1d558ff61cf3b676d0ccfe7421319faac. --- .../{.vale-config/styles => }/config/vocabularies/Base/accept.txt | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/vale/{.vale-config/styles => }/config/vocabularies/Base/accept.txt (100%) diff --git a/.github/vale/.vale-config/styles/config/vocabularies/Base/accept.txt b/.github/vale/config/vocabularies/Base/accept.txt similarity index 100% rename from .github/vale/.vale-config/styles/config/vocabularies/Base/accept.txt rename to .github/vale/config/vocabularies/Base/accept.txt