Merge branch 'main' into enhance-base-documentation-from-talk

spier · web-flow · commit e8699a7d45d7 · 2026-07-11T15:30:11.000+02:00
diff --git 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
diff --git a/.github/vale/config/vocabularies/Base/accept.txt b/.github/vale/config/vocabularies/Base/accept.txt
@@ -1,7 +1,19 @@
-Adyen
-
+## For pattern: Standard Base Documentation
 [Ii]nvariants?
 Devs
 Erinle
 Feyijimi
-Agentic
+Agentic
+
+## For pattern: Maturity Model   
+Adyen
+
+## For pattern: InnerSource Hackathon   
+Ingka
+Manoharan
+Shanmugapriya
+Kickstarting
+Contribfest
+Baumgarten
+Trin
+El
diff --git a/.github/workflows/all-patterns-listed.yml b/.github/workflows/all-patterns-listed.yml
@@ -13,7 +13,7 @@ jobs:
   all-patterns-listed:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
 
       - name: Check if all patterns are listed in README.md
         run: |
diff --git a/.github/workflows/book.yml b/.github/workflows/book.yml
@@ -18,7 +18,7 @@ jobs:
         language: [en, ja, zh, pt-br, gl, es]
 
     steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v7
 
     - uses: ruby/setup-ruby@v1
       with:
diff --git a/.github/workflows/generate-mindmap.yml b/.github/workflows/generate-mindmap.yml
@@ -27,7 +27,7 @@ jobs:
       contents: write
 
     steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v7
     - name: Use Node.js
       uses: actions/setup-node@v6
       with:
diff --git a/.github/workflows/i18n-consistency-checker.yaml b/.github/workflows/i18n-consistency-checker.yaml
@@ -17,7 +17,7 @@ jobs:
       matrix:
         language: [ja, zh, pt-br, gl, es]
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
         with:
           fetch-depth: '0'
       - name: Check consistency and create issue
diff --git a/.github/workflows/link-checker-prs.yml b/.github/workflows/link-checker-prs.yml
@@ -15,7 +15,7 @@ jobs:
   linkChecker:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
@@ -29,7 +29,7 @@ jobs:
           echo "MARKDOWN_FILES=$md_files" >> $GITHUB_ENV
 
       - name: Restore lychee cache
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: .lycheecache
           key: cache-lychee-${{ github.sha }}
diff --git a/.github/workflows/link-checker.yml b/.github/workflows/link-checker.yml
@@ -15,10 +15,10 @@ jobs:
   linkChecker:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
 
       - name: Restore lychee cache
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: .lycheecache
           key: cache-lychee-${{ github.sha }}
diff --git a/.github/workflows/lint-patterns.yml b/.github/workflows/lint-patterns.yml
@@ -18,7 +18,7 @@ jobs:
   validate:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v7
     - name: Problem Matcher for markdownlint-cli
       uses: xt0rted/markdownlint-problem-matcher@v3
     - name: Lint pattern files (markdown)
diff --git a/.github/workflows/markdownlint.yml b/.github/workflows/markdownlint.yml
@@ -20,7 +20,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v7
     - name: Use Node.js
       uses: actions/setup-node@v6
       with:
diff --git a/.github/workflows/pattern-metrics.yaml b/.github/workflows/pattern-metrics.yaml
@@ -29,7 +29,7 @@ jobs:
         echo "last_month=$first_day..$last_day" >> "$GITHUB_ENV"
 
     - name: Check out the code so we can get the CODEOWNERS names
-      uses: actions/checkout@v6
+      uses: actions/checkout@v7
       with:
         sparse-checkout: |
           .github/CODEOWNERS
diff --git a/.github/workflows/vale.yml b/.github/workflows/vale.yml
@@ -18,10 +18,10 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v7
 
     - 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"
diff --git a/.markdownlint.json b/.markdownlint.json
@@ -13,5 +13,6 @@
     "MD034": false,
     "MD036": false,
     "MD040": false,
-    "MD041": false
+    "MD041": false,
+    "MD060": false
 }
diff --git 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,11 +64,11 @@ 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
 
-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  
 
diff --git 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 "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
@@ -104,7 +104,30 @@ All these help scale InnerSource in the organization.
 ## Known Instances
 
 * **IKEA** (Ingka Group)
-* **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).
+* **Thales Group**
+* **The Aerospace Corporation**
+
+### IKEA (Ingka Group)
+
+**IKEA** (Ingka Group) organized a company-wide InnerSource hackathon to scale InnerSource adoption beyond the early adopters already familiar with open source practices. Despite leadership support, IKEA struggled to spread InnerSource awareness to engineers new to collaborative ways of working and to attract contributions to existing InnerSource projects. The event was organized and run by Ingka Group's Open Source Program Office (OSPO), which also supports InnerSource adoption across the engineering organization.
+
+The hackathon was held as a virtual, one-day event open to all developers in the company, with a few extra days allowed for participants to finish and submit their work. Participants could join individually or in teams and chose from two categories: (1) **start a new InnerSource project** — either from scratch with documentation in place from the beginning, or by converting an existing project to follow InnerSource guidelines and publishing it in the company's InnerSource marketplace; or (2) **contribute to an existing InnerSource project** — before the event, project maintainers pre-listed features and issues tagged as "hackathon" or "good first issue" so participants could pick them up on the day. The judging panel comprised representatives from different business areas across the company, all strong advocates of InnerSource.
+
+The event drew participation from engineers across **six countries** and resulted in contributions to around **six InnerSource projects**. The InnerSource project landscape grew by approximately **50%** as a result of the event. One newly created project was identified as a strong candidate for open sourcing. Notably, the hackathon reached many developers who would not have engaged with InnerSource through conventional awareness campaigns — making it especially effective for the late majority who had previously ignored the topic.
+
+Shanmugapriya Manoharan (Engineering Advisor, OSPO, IKEA IT AB) shared this experience at an InnerSource Commons community call in December 2024. See: [Hackathon: A Fun and safe approach to get started with InnerSource](https://youtu.be/7RWJUKanbqQ) (InnerSource Commons Community Call, December 2024).
+
+### Thales Group
+
+**Thales Group** runs Thales I/O Days, combining 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
+
+**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
 
@@ -116,4 +139,4 @@ All these help scale InnerSource in the organization.
 
 ## Acknowledgments
 
-* Trin Baumgarten and Caroline T Jones (The Aerospace Corporation) for [sharing their experience](https://www.youtube.com/watch?v=J5KeCHFbnWA) at the InnerSource Commons Summit.
+* Trin Baumgarten and Caroline T. Jones (The Aerospace Corporation) for [sharing their experience](https://www.youtube.com/watch?v=J5KeCHFbnWA) at the InnerSource Commons Summit.
diff --git 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. 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
@@ -110,4 +115,4 @@ For more details see the InnerSource Commons Community call from 09/2023 [Improv
 - **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
diff --git 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, 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
 
diff --git 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
@@ -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
@@ -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
@@ -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
@@ -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
 
 ## 翻译校对
 
