Skip to content

Add Thales Group as Known Instance across five patterns - #909

Merged
spier merged 12 commits into
InnerSourceCommons:mainfrom
rrrutledge:add-thales-known-instances
Jun 17, 2026
Merged

Add Thales Group as Known Instance across five patterns#909
spier merged 12 commits into
InnerSourceCommons:mainfrom
rrrutledge:add-thales-known-instances

Conversation

@rrrutledge

@rrrutledge rrrutledge commented May 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds Thales Group as a 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 has run an InnerSource Program Office for 10 years across 85,000+ employees in 65 countries.

  • Praise Participants — Thales applies this pattern explicitly by name, with per-contribution recognition plus formal awards at the annual "Tales I Days" in-person event
  • Developer Incentive Alignment for InnerSource Contribution — InnerSource contributions are on the expert career path as proof of leadership and expertise; replaces "TBD" Known Instances
  • InnerSource Ambassadors — Thales "Community Leaders" meet quarterly with the ISPO as a "Steering Board," creating a structured bottom-up/top-down governance loop
  • InnerSource Hackathon — Tales I Days combines hackathon + conference + awards ceremony in one annual in-person event open to non-engineering staff as well
  • InnerSource License — Thales created four ready-to-use InnerSource licenses with legal partners, available at no cost to all participants

Test plan

  • Verify all five YouTube links resolve to the correct talk
  • Confirm each entry matches the surrounding Known Instances formatting style (bullet style, bold org name, trailing citation)
  • Check that the Thales section in InnerSource License appears correctly between GovTech and the Status section

🤖 Generated with Claude Code

@rrrutledge @claude
Add Thales Group as Known Instance across five patterns
29a0949 
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 <noreply@anthropic.com>
rrrutledge
rrrutledge commented May 27, 2026
View reviewed changes
Comment thread patterns/2-structured/praise-participants.md Outdated
rrrutledge and others added 3 commits May 27, 2026 14:11
@rrrutledge
Apply suggestion from @rrrutledge
bd9e618
@rrrutledge @claude
Address PR feedback from Marius on Thales Known Instances
72dba08 
- 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 <noreply@anthropic.com>
@rrrutledge @claude
Improve grammar and sentence structure of Thales hackathon entry
81a2d31 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot mentioned this pull request Jun 1, 2026
Open
rrrutledge and others added 3 commits June 15, 2026 10:34
@rrrutledge @claude
Incorporate Marius's Jun 11 review feedback across five patterns
836af30 
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) <noreply@anthropic.com>
@spier
Exclude MD060 markdownlint check. This has never failed in the pust, …
7a84fd5 
…so must be some configuration drift.
@spier
Fix some links, as reported by the GHA Link Checker
7ba91d7
@spier

spier commented Jun 17, 2026

Copy link
Copy Markdown
Member

For the translation leads that got notified on this PR: I only made a minor fix to one link/URL. So nothing to do for you here. Sorry for the alert :)

@spier

spier commented Jun 17, 2026

Copy link
Copy Markdown
Member

@rrrutledge I cannot tell where Marius's Jun 11 review feedback happened, but I am assuming in some other channel (slack, email, etc).

Therefore I will go ahead and merge.

@rrrutledge

rrrutledge commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

Thank you! I had been iterating with Marius in Slack, and he signed off just now :)

@spier

spier commented Jun 17, 2026

Copy link
Copy Markdown
Member

Something changed in the vale style checker, which is why the GitHub Action vale.yml is failing.

I tried various things, including updating the GitHub action but so far no luck.

One lead that might cause the issue, is the folder to which our isc-styles package gets synced.

As GHA

When vale runs as a GHA as part of this, it loads the package into this folder:
SUCCESS Synced 1 package(s) to '.../InnerSourcePatterns/.github/vale'

Locally

When running this locally I see this instead
SUCCESS Synced 1 package(s) to '.../InnerSourcePatterns/.github/vale/.vale-config/styles'

As I am not able to fix this quickly, will still merge this PR here and fix the issue separately i.e. on a new branch/PR.

@spier
spier merged commit 3ebd603 into InnerSourceCommons:main Jun 17, 2026
9 of 11 checks passed
@spier spier added 2-structured Patterns with existing instances (Please see our contribution handbook for details) 📖 Type - Content Work Working on contents is the main focus of this issue / PR labels Jun 17, 2026
@spier spier added the 🐅 patterns-in-the-wild InnerSource patterns that were spotted in the wild. We can extract Known Instances and new patterns. label Jun 17, 2026
@spier

spier commented Jun 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

@rrrutledge your changes are now live e.g. see https://patterns.innersourcecommons.org/p/innersource-hackathon#known-instances

Thank you for integrating this content from the community calls into our patterns!

@rrrutledge rrrutledge mentioned this pull request Aug 11, 2026
Open
2 tasks
rrrutledge added a commit to rrrutledge/InnerSourcePatterns that referenced this pull request Aug 11, 2026
@rrrutledge @claude
Accept a transcript directly, and bundle one talk into one PR
3adb219 
Two corrections per review:

- Step 1 now accepts a transcript handed to it directly (the
  going-forward case: an automated source pulls a Zoom transcript once a
  community call finishes, with no YouTube URL involved at all) as well
  as a YouTube URL to fetch from - the URL-fetch path stays for backlog
  talks and one-off requests.
- Step 8's "one concern per PR" is replaced with "one talk = one PR":
  bundle everything a single talk's analysis found - Known Instances
  across multiple patterns, clarifications, new pattern drafts - into
  one PR, matching how InnerSourceCommons#909 actually added Thales across five patterns
  in a single PR. Only split PRs across genuinely different source talks.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@spier spier spier approved these changes
@lenucksi lenucksi Awaiting requested review from lenucksi lenucksi is a code owner
@NewMexicoKid NewMexicoKid Awaiting requested review from NewMexicoKid NewMexicoKid is a code owner
@cewilliams cewilliams Awaiting requested review from cewilliams cewilliams is a code owner
@robtuley robtuley Awaiting requested review from robtuley robtuley is a code owner
@yuhattor yuhattor Awaiting requested review from yuhattor yuhattor is a code owner
@psanxiao psanxiao Awaiting requested review from psanxiao psanxiao is a code owner
@WillemJiang WillemJiang Awaiting requested review from WillemJiang WillemJiang is a code owner

Assignees

No one assigned

Labels

2-structured Patterns with existing instances (Please see our contribution handbook for details) 📖 Type - Content Work Working on contents is the main focus of this issue / PR 🐅 patterns-in-the-wild InnerSource patterns that were spotted in the wild. We can extract Known Instances and new patterns.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@rrrutledge @spier