Skip to content

Add NatWest Group as Known Instance across three patterns #942

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
rrrutledge wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add NatWest Group as Known Instance across three patterns #942

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74d6e30
Add NatWest Group as Known Instance across three patterns
rrrutledge Oct 16, 2026
adb257d
Apply writing review to NatWest Known Instance entries
rrrutledge Oct 16, 2026
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
2 changes: 2 additions & 0 deletions patterns/2-structured/base-documentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,7 @@
* The time for contributors to get up to speed is significantly reduced.
* Time spent on answering initial questions for [Trusted Committers](trusted-committer.md) is significantly reduced, leaving them more time to work on other tasks.
* Escalations due to misunderstandings and misalignment are significantly reduced.
* When many InnerSource projects in an organization follow the same base documentation standard, contributors moving from one project to another find the same information in the same place, so each new project they engage with costs them less to learn.

## Known Instances

Expand All @@ -134,6 +135,7 @@
* **Analog Devices Inc.**
* **Airbus**
* **Siemens** automatically creates a checklist issue for every new InnerSource project to make maintainers aware of mandatory requirements (e.g. business approval, license & copyright, export control, contributing guidelines, maintainer maturity) as well as best practices (e.g. documentation as code, semantic versioning, continuous integration/deployment).
* **NatWest Group** - The OSPO's InnerSource playbook includes a blueprint, a checklist for setting up a project for InnerSource with the base documentation standards (`README.md`, `CONTRIBUTING.md`, a communication section) embedded in it. The goal is consistency across projects. The OSPO also offers a readiness assessment against the standard, with must-have and nice-to-have recommendations - for example, rewording a "contact us" section so it invites users to contribute fixes rather than only report problems. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).

Check failure on line 138 in patterns/2-structured/base-documentation.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Cheong'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Cheong'?","location":{"path":"patterns/2-structured/base-documentation.md","range":{"start":{"line":138,"column":634},"end":{"line":138,"column":640}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

Check failure on line 138 in patterns/2-structured/base-documentation.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Pooi'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Pooi'?","location":{"path":"patterns/2-structured/base-documentation.md","range":{"start":{"line":138,"column":624},"end":{"line":138,"column":628}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

Check failure on line 138 in patterns/2-structured/base-documentation.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Enablement'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Enablement'?","location":{"path":"patterns/2-structured/base-documentation.md","range":{"start":{"line":138,"column":558},"end":{"line":138,"column":568}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

Check failure on line 138 in patterns/2-structured/base-documentation.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'OSPO's'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'OSPO's'?","location":{"path":"patterns/2-structured/base-documentation.md","range":{"start":{"line":138,"column":27},"end":{"line":138,"column":33}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

## Authors

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/innersource-portal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,7 @@
* **Mercedes-Benz** is [using](https://opensource.mercedes-benz.com/news/sponsor_innersource_commonsoss) the SAP reference implementation mentioned above for their InnerSource Portal.
* **WellSky** has a simple _Confluence Wiki_ page were InnerSource and reusable projects are listed.
* **Siemens** has set up an internal portal that provides documentation for InnerSource maintainers, contributors, users and their managers. It also serves as an entry point to explore available projects and gives hints to improve project visibility.
* **NatWest Group** reuses the software catalog in its existing internal Engineering Portal instead of building a separate portal: projects self-register by adding an InnerSource tag to their catalog config file, and engineers find them by searching on that tag. Registering and tagging is part of NatWest's InnerSource readiness standard. A communications campaign run with an internal practice team after launch grew the catalog to over 40 discoverable projects. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).

Check failure on line 112 in patterns/2-structured/innersource-portal.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Cheong'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Cheong'?","location":{"path":"patterns/2-structured/innersource-portal.md","range":{"start":{"line":112,"column":581},"end":{"line":112,"column":587}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

Check failure on line 112 in patterns/2-structured/innersource-portal.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Pooi'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Pooi'?","location":{"path":"patterns/2-structured/innersource-portal.md","range":{"start":{"line":112,"column":571},"end":{"line":112,"column":575}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

Check failure on line 112 in patterns/2-structured/innersource-portal.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Enablement'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Enablement'?","location":{"path":"patterns/2-structured/innersource-portal.md","range":{"start":{"line":112,"column":505},"end":{"line":112,"column":515}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

## References

Expand Down
1 change: 1 addition & 0 deletions patterns/2-structured/praise-participants.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,7 @@

## Known Instances

* **NatWest Group** - The OSPO presents InnerSource Ambassador and Contributor Recognition Awards at its quarterly internal InnerSource meetup, a hybrid event that rotates between UK and India offices. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).

Check failure on line 74 in patterns/2-structured/praise-participants.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Pooi'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Pooi'?","location":{"path":"patterns/2-structured/praise-participants.md","range":{"start":{"line":74,"column":308},"end":{"line":74,"column":312}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}

Check failure on line 74 in patterns/2-structured/praise-participants.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 馃惗
[ISC.Spelling] Did you really mean 'Enablement'?

Raw Output:
{"message":"[ISC.Spelling] Did you really mean 'Enablement'?","location":{"path":"patterns/2-structured/praise-participants.md","range":{"start":{"line":74,"column":242},"end":{"line":74,"column":252}}},"severity":"ERROR","code":{"value":"ISC.Spelling"}}
* **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.
Expand Down
Loading