🇯🇵 Japanese: Content Consistency Issue #807
Description
i18n Contents Consistency Issue
The following files may have consistency issues with the English version. Please check and update the files.
This issue is created when any of the English patterns have changed (in folder ). It compares the git update history to let you know what updates are overdue. The issue should be closed when the update is complete.
Review Committee (patterns/2-structured/review-committee.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/review-committee.md b/patterns/2-structured/review-committee.md
# index f27d793..1252af2 100644
# --- a/patterns/2-structured/review-committee.md
# +++ b/patterns/2-structured/review-committee.md
@@ -41,7 +41,7 @@ Company A wants to introduce its first InnerSource initiative. Most managers in
## Known Instances
-* BIOS at Robert Bosch GmbH (in the early stages of adoption, only - 2009-2012)
+* BIOS at **Robert Bosch GmbH** (in the early stages of adoption, only - 2009-2012)
## Status
Start as an Experiment (patterns/2-structured/start-as-experiment.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/start-as-experiment.md b/patterns/2-structured/start-as-experiment.md
# index b5ddcac..13451ae 100644
# --- a/patterns/2-structured/start-as-experiment.md
# +++ b/patterns/2-structured/start-as-experiment.md
@@ -53,9 +53,9 @@ Finally, starting as an experiment makes it much easier to sidestep regulations
## Known Instances
-- Robert Bosch GmbH (globally distributed software development)
-- Airbus: the data science community collaborated on shared Python libraries that eventually lead to a group-wide InnerSource scheme for any software.
-- Siemens started their [InnerSource Platform](https://about.gitlab.com/customers/siemens/) code.siemens.com from a single department with a few hundred users. Over the years they scaled it to a company-wide service with 50,000 active users.
+- **Robert Bosch GmbH** (globally distributed software development)
+- **Airbus**: the data science community collaborated on shared Python libraries that eventually lead to a group-wide InnerSource scheme for any software.
+- **Siemens** started their [InnerSource Platform](https://about.gitlab.com/customers/siemens/) code.siemens.com from a single department with a few hundred users. Over the years they scaled it to a company-wide service with 50,000 active users.
## Status
Maturity Model (patterns/2-structured/maturity-model.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/maturity-model.md b/patterns/2-structured/maturity-model.md
# index 629c2e4..cfc66dd 100644
# --- a/patterns/2-structured/maturity-model.md
# +++ b/patterns/2-structured/maturity-model.md
@@ -210,10 +210,10 @@ long term.
## Known Instances
-* Entelgy
-* Zylk
-* Bitergia
-* Airbus
+* **Entelgy**
+* **Zylk**
+* **Bitergia**
+* **Airbus**
## Authors
Issue Tracker Use Cases (patterns/2-structured/issue-tracker.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/issue-tracker.md b/patterns/2-structured/issue-tracker.md
# index 1de6c76..17bb85d 100644
# --- a/patterns/2-structured/issue-tracker.md
# +++ b/patterns/2-structured/issue-tracker.md
@@ -49,8 +49,8 @@ development but also during the planning phase of new features:
## Known Instances
-* Europace AG - See blog post [Issue Use Cases](https://tech.europace.de/post/using-issues-for-asking-questions-and-tracking-work/)
-* Siemens manages work on their InnerSource Platform in a fully transparent way. Therefore the work on the InnerSource Platform itself is organized as an InnerSource project. This includes tracking enhancements and bugs, as well as marketing, communication activities and support requests from users.
+* **Europace AG** - See blog post [Issue Use Cases](https://tech.europace.de/post/using-issues-for-asking-questions-and-tracking-work/)
+* **Siemens** manages work on their InnerSource Platform in a fully transparent way. Therefore the work on the InnerSource Platform itself is organized as an InnerSource project. This includes tracking enhancements and bugs, as well as marketing, communication activities and support requests from users.
## Authors
Transparent Cross-Team Decision Making using RFCs (patterns/2-structured/transparent-cross-team-decision-making-using-rfcs.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 110 days.
# diff --git a/patterns/2-structured/transparent-cross-team-decision-making-using-rfcs.md b/patterns/2-structured/transparent-cross-team-decision-making-using-rfcs.md
# index 5c46178..d267f50 100644
# --- a/patterns/2-structured/transparent-cross-team-decision-making-using-rfcs.md
# +++ b/patterns/2-structured/transparent-cross-team-decision-making-using-rfcs.md
@@ -99,6 +99,7 @@ Also for decision making outside of pure software design decisions, transparent
- **Uber** - According to this blog post by Gergely Orosz: [Scaling Engineering Teams via RFCs: Writing Things Down][uber].
- **Google Design Docs** - As described in this blog post by Malte Ubl [Design Docs at Google][google]
- **DAZN** (10/2021) - One way that DAZN makes technical decisions is via RFCs. RFCs are used for decisions that apply to engineering-wide processes only! The RFCs live in a GitHub repository, and technical standards are then gradually adopted within their tools and by their engineers. An RFC can be raised by any engineer, and voted on by all engineers. If upvotes exceed downvotes, the RFC is adopted. It’s worth noting, that the RFC voting process hasn’t yet been “stress-tested” by any contentious decisions. - As described in this blog post by Lou Bichard: [Building A DX Team: Lessons Learned][dazn]
+- **SAP** (03/2024) - SAP has a mature tool-assisted process for document review across teams. It is primarily used for the review of Architecture Decision Records (ADR) originating from cross-team work done on the Cross-Product Architecture collaboration model. Some noteworthy implementation differences from this pattern: The review process is not easily available for decisions on small projects. Also, the documents are not restricted to InnerSource projects only. - As described in the blog post [Cross-Product Architecture: Embracing Conway's Law for Better Software Architecture][sap-cpa].
## Status
@@ -124,3 +125,4 @@ Structured
[bbc]: https://www.youtube.com/watch?v=U6zlghE0HcE
[google]: https://www.industrialempathy.com/posts/design-docs-at-google/
[dazn]: https://medium.com/dazn-tech/building-a-dx-team-lessons-learned-4a66446088bc
+[sap-cpa]: https://community.sap.com/t5/technology-blogs-by-sap/cross-product-architecture-embracing-conway-s-law-for-better-software/ba-p/13648600Dedicated Community Leader (patterns/2-structured/dedicated-community-leader.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/dedicated-community-leader.md b/patterns/2-structured/dedicated-community-leader.md
# index 8f5235d..2799d3e 100644
# --- a/patterns/2-structured/dedicated-community-leader.md
# +++ b/patterns/2-structured/dedicated-community-leader.md
@@ -58,8 +58,8 @@ Having excellent and dedicated community leaders is a precondition for the succe
## Known Instances
-* _BIOS at Robert Bosch GmbH_. Note that InnerSource at Bosch was, for the majority, aimed at increasing innovation and to a large degree dealt with internal facing products. This pattern is currently not used at Bosch for lack of funding.
-* _Airbus_. A data scientist wanted to improve the collaboration with peers in the group and found: i) many developers (beyond data science) wanted that too and were happy someone was taking care of the issue, and ii) support from line manager and middle management to eventually act as the _de facto_ community leader, on top of his regular line of duty.
+* BIOS at **Robert Bosch GmbH**. Note that InnerSource at Bosch was, for the majority, aimed at increasing innovation and to a large degree dealt with internal facing products. This pattern is currently not used at Bosch for lack of funding.
+* **Airbus**. A data scientist wanted to improve the collaboration with peers in the group and found: i) many developers (beyond data science) wanted that too and were happy someone was taking care of the issue, and ii) support from line manager and middle management to eventually act as the _de facto_ community leader, on top of his regular line of duty.
## Alias
Contracted Contributor (patterns/2-structured/contracted-contributor.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/contracted-contributor.md b/patterns/2-structured/contracted-contributor.md
# index 0790f67..eba1510 100644
# --- a/patterns/2-structured/contracted-contributor.md
# +++ b/patterns/2-structured/contracted-contributor.md
@@ -83,7 +83,7 @@ A formal contracting is also beneficial for contributors and communities:
## Known Instances
-- BIOS at Robert Bosch GmbH
+- BIOS at **Robert Bosch GmbH**
## Status
Trusted Committer (patterns/2-structured/trusted-committer.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/trusted-committer.md b/patterns/2-structured/trusted-committer.md
# index 085513c..b826f19 100644
# --- a/patterns/2-structured/trusted-committer.md
# +++ b/patterns/2-structured/trusted-committer.md
@@ -123,12 +123,10 @@ there is a plan for responsible stewardship.
## Known Instances
-This has been tried and proven successful at:
-
-- Nike
-- PayPal
-- Mercado Libre - adds a section in the `CONTRIBUTING.md` file to inform who the Trusted Committers are.
-- Robert Bosch GmbH - we didn't call the role 'Trusted Committer' but we had this role at the beginning of our InnerSource journey. Trusted Committers would be funded for 100 % of their time to be able to focus on this role.
+- **Nike**
+- **PayPal**
+- **Mercado Libre** - adds a section in the `CONTRIBUTING.md` file to inform who the Trusted Committers are.
+- **Robert Bosch GmbH** - we didn't call the role 'Trusted Committer' but we had this role at the beginning of our InnerSource journey. Trusted Committers would be funded for 100 % of their time to be able to focus on this role.
Communication Tooling (patterns/2-structured/communication-tooling.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/communication-tooling.md b/patterns/2-structured/communication-tooling.md
# index b2abf51..b0605ee 100644
# --- a/patterns/2-structured/communication-tooling.md
# +++ b/patterns/2-structured/communication-tooling.md
@@ -74,10 +74,10 @@ to a lower need to repeat explanations.
## Known Instances
-* Europace AG
-* Paypal Inc.
-* Mercado Libre
-* Siemens makes extensive use of communication channels accessible to all employees for all user questions and discussions around code.siemens.com, InnerSource and Open Source.
+* **Europace AG**
+* **Paypal Inc.**
+* **Mercado Libre**
+* **Siemens** makes extensive use of communication channels accessible to all employees for all user questions and discussions around code.siemens.com, InnerSource and Open Source.
## Authors
Cross-Team Project Valuation (patterns/2-structured/crossteam-project-valuation.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/crossteam-project-valuation.md b/patterns/2-structured/crossteam-project-valuation.md
# index 96b89c8..dd2adfd 100644
# --- a/patterns/2-structured/crossteam-project-valuation.md
# +++ b/patterns/2-structured/crossteam-project-valuation.md
@@ -92,7 +92,7 @@ They will provide a head-and-shoulders improvement in on-the-ground results over
## Known Instances
-* Nike
+* **Nike**
## Status
Praise Participants (patterns/2-structured/praise-participants.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/praise-participants.md b/patterns/2-structured/praise-participants.md
# index 12d176b..7836f81 100644
# --- a/patterns/2-structured/praise-participants.md
# +++ b/patterns/2-structured/praise-participants.md
@@ -71,9 +71,9 @@ Overdoing it may feel insincere and mechanical and defeat your purpose in reachi
## Known Instances
-* 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.
+* **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.
## Status
InnerSource License (patterns/2-structured/innersource-license.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md
# index bc031e9..c085653 100644
# --- a/patterns/2-structured/innersource-license.md
# +++ b/patterns/2-structured/innersource-license.md
@@ -55,6 +55,7 @@ The license simplifies the conversations within our organization about sharing s
- **Robert Bosch GmbH**
- **Airbus**
- **GovTech (Singapore Government)**
+- **Siemens** has developed their own InnerSource license alongside other necessary legal agreements between subsidiaries.
### DB Systel
Common Requirements (patterns/2-structured/common-requirements.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 372 days.
# diff --git a/patterns/2-structured/common-requirements.md b/patterns/2-structured/common-requirements.md
# index 0381be2..b2c688e 100644
# --- a/patterns/2-structured/common-requirements.md
# +++ b/patterns/2-structured/common-requirements.md
@@ -16,7 +16,7 @@ The common code in the shared repository isn't meeting the needs of all the proj
* Someone (or some project) wrote the code in the first place and contributed it to the repository.
* The common code is a small percentage of the overall deliverable from any of the projects.
* Each project has its own delivery schedule, set of deliverables and customers.
-* This pattern applies in either of these situations:
+* This pattern applies in any of these situations:
* there is a **Strong Code Owner** i.e. all changes to the shared repository have to be approved by the repo owner
* there is **weak code ownership** i.e. no one really owns the code
* there is **no Benevolent Sponsor** i.e. no organization or executive is providing resources to organize the common code in an InnerSource fashionInnerSource Portal (patterns/2-structured/innersource-portal.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/innersource-portal.md b/patterns/2-structured/innersource-portal.md
# index 0473fd5..823af86 100644
# --- a/patterns/2-structured/innersource-portal.md
# +++ b/patterns/2-structured/innersource-portal.md
@@ -108,6 +108,7 @@ It is a good solution for a portal with a few dozen projects, though.
* **Mercado Libre** use an instance of the [SAP portal](https://github.com/SAP/project-portal-for-innersource) to discover existing InnerSource projects within the organization.
* **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.
## References
Service vs. Library (patterns/2-structured/service-vs-library.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/service-vs-library.md b/patterns/2-structured/service-vs-library.md
# index 51bde3c..7370bb1 100644
# --- a/patterns/2-structured/service-vs-library.md
# +++ b/patterns/2-structured/service-vs-library.md
@@ -72,9 +72,9 @@ Related to this pattern is the [30 Day Warranty](30-day-warranty.md) pattern tha
## Known Instances
-* Europace AG
-* Flutter Entertainment: A [Flutter InnerSource application](https://innersource.flutter.com/sdlc/) has a shared code "service" repository with cross-team contribution and CI pipeline to build and publish a shared release artifact. Each adopting team has a "deployment config" repository defining their own deployment. This is driven by varying regulatory requirements, service and incident management practices and infrastructure skill sets in different areas of the business.
-* WellSky (see [Continuous InnerSource in Production - 5 Times](https://www.youtube.com/watch?v=loSTj4yIG9Q&pp=ygUkY29udGludW91cyBpbm5lcnNvdXJjZSBpbiBwcm9kdWN0aW9u))
+* **Europace AG**
+* **Flutter Entertainment**: A [Flutter InnerSource application](https://innersource.flutter.com/sdlc/) has a shared code "service" repository with cross-team contribution and CI pipeline to build and publish a shared release artifact. Each adopting team has a "deployment config" repository defining their own deployment. This is driven by varying regulatory requirements, service and incident management practices and infrastructure skill sets in different areas of the business.
+* **WellSky** (see [Continuous InnerSource in Production - 5 Times](https://www.youtube.com/watch?v=loSTj4yIG9Q&pp=ygUkY29udGludW91cyBpbm5lcnNvdXJjZSBpbiBwcm9kdWN0aW9u))
## Status
30 Day Warranty (patterns/2-structured/30-day-warranty.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/30-day-warranty.md b/patterns/2-structured/30-day-warranty.md
# index b21ab81..9f60805 100644
# --- a/patterns/2-structured/30-day-warranty.md
# +++ b/patterns/2-structured/30-day-warranty.md
@@ -46,10 +46,10 @@ In addition it helps to provide clear [contribution guidelines](./base-documenta
## Known Instances
-- This was tried and proven successful at PayPal.
-- GitHub internally uses this pattern with a modified warranty timeline of 6 weeks.
-- Microsoft recommends this pattern as a principle - teams set their own specific time target matching their needs and confidence.
-- SAP leverages this pattern in their InnerSource-based Everest project to transform collaboration, ensuring contributions are not just accepted but also supported, enhancing trust and driving forward the culture of shared responsibility and innovation. See: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
+- **PayPal** Tried this and it was proven successful.
+- **GitHub** internally uses this pattern with a modified warranty timeline of 6 weeks.
+- **Microsoft** recommends this pattern as a principle - teams set their own specific time target matching their needs and confidence.
+- **SAP** leverages this pattern in their InnerSource-based Everest project to transform collaboration, ensuring contributions are not just accepted but also supported, enhancing trust and driving forward the culture of shared responsibility and innovation. See: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
## Authors
Gig Marketplace (patterns/2-structured/gig-marketplace.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/gig-marketplace.md b/patterns/2-structured/gig-marketplace.md
# index 7e2ae37..69552cb 100644
# --- a/patterns/2-structured/gig-marketplace.md
# +++ b/patterns/2-structured/gig-marketplace.md
@@ -60,7 +60,7 @@ When used in combination with the InnerSource Portal pattern, the Gig Marketplac
## Known Instances
* A large financial services organization has used the creation of an InnerSource Gig Marketplace website to foster their InnerSource program.
-* SAP implemented the Gig Marketplace pattern - a new InnerSource program was added to the internal job platform where positions and similar offerings can be posted.
+* **SAP** implemented the Gig Marketplace pattern - a new InnerSource program was added to the internal job platform where positions and similar offerings can be posted.
* The Gig Marketplace pattern has been proven to work extremely well with the associated [InnerSource Portal](./innersource-portal.md) pattern in this context. The InnerSource Portal increases awareness of specific projects currently underway while the Gig Marketplace advertises tasks of a certain type available to be worked on within those projects.
## StatusRepository Activity Score (patterns/2-structured/repository-activity-score.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/repository-activity-score.md b/patterns/2-structured/repository-activity-score.md
# index 9aadaec..73c26a5 100644
# --- a/patterns/2-structured/repository-activity-score.md
# +++ b/patterns/2-structured/repository-activity-score.md
@@ -114,9 +114,9 @@ The repository activity score is a simple calculation based on the GitHub API. I
## Known Instances
-* Used in SAP's InnerSource project portal to define the default order of the InnerSource projects. It was first created in July 2020 and is fine-tuned and updated frequently ever since. When proposed to the InnerSource Commons in July 2020, this pattern emerged. Also see [Michael Graf & Harish B (SAP) at ISC.S11 - The Unexpected Path of Applying InnerSource Patterns](https://www.youtube.com/watch?v=6r9QOw9dcQo&list=PLCH-i0B0otNQZQt_QzGR9Il_kE4C6cQRy&index=6).
-* Airbus took a lot of inspiration from this pattern to create an "InnerSource score" that combines the activity score together with checks from the [Standard Base Documentation](./base-documentation.md) and the [InnerSource License](./innersource-license.md).
-* Siemens includes repository activity in their InnerSource project quality score. Maintainers can use the quality score to improve their project and communicate their score via badges.
+* **SAP** - Used in SAP's InnerSource project portal to define the default order of the InnerSource projects. It was first created in July 2020 and is fine-tuned and updated frequently ever since. When proposed to the InnerSource Commons in July 2020, this pattern emerged. Also see [Michael Graf & Harish B (SAP) at ISC.S11 - The Unexpected Path of Applying InnerSource Patterns](https://www.youtube.com/watch?v=6r9QOw9dcQo&list=PLCH-i0B0otNQZQt_QzGR9Il_kE4C6cQRy&index=6).
+* **Airbus** took a lot of inspiration from this pattern to create an "InnerSource score" that combines the activity score together with checks from the [Standard Base Documentation](./base-documentation.md) and the [InnerSource License](./innersource-license.md).
+* **Siemens** includes repository activity in their InnerSource project quality score. Maintainers can use the quality score to improve their project and communicate their score via badges.
## Status
Document your Guiding Principles (patterns/2-structured/document-your-guiding-principles.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/document-your-guiding-principles.md b/patterns/2-structured/document-your-guiding-principles.md
# index 9fbd159..7224d6b 100644
# --- a/patterns/2-structured/document-your-guiding-principles.md
# +++ b/patterns/2-structured/document-your-guiding-principles.md
@@ -121,10 +121,10 @@ All Trusted Committers of a project are published.
## Known Instances
-* Europace AG
-* GitHub
-* Robert Bosch GmbH
-* Siemens' InnerSource strategy is built upon the guiding principles of Documentation, Workflow, Transparency, Continuous Integration and Culture which are detailed in their InnerSource portal.
+* **Europace AG**
+* **GitHub**
+* **Robert Bosch GmbH**
+* **Siemens'** InnerSource strategy is built upon the guiding principles of Documentation, Workflow, Transparency, Continuous Integration and Culture which are detailed in their InnerSource portal.
### Europace AG
Standard Base Documentation (patterns/2-structured/base-documentation.md)
For more information, please compare the original file(en) with the translated file. You can view the differences on GitHub. The number of days since overdue updates is 6 days.
# diff --git a/patterns/2-structured/base-documentation.md b/patterns/2-structured/base-documentation.md
# index dd2a864..9004df8 100644
# --- a/patterns/2-structured/base-documentation.md
# +++ b/patterns/2-structured/base-documentation.md
@@ -128,12 +128,12 @@ started right away: [README-template.md](templates/README-template.md),
## Known Instances
-* Europace AG - See blog post [InnerSource: Adding base documentation](https://tech.europace.de/post/innersource-base-documentation/)
-* Paypal Inc.
-* Mercado Libre - create a documentation site that contains how to get started with InnerSource and also define the basic artifacts that a repository must have to be InnerSource (README, CONTRIBUTING, CODING_GUIDELINES, etc).
-* 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).
+* **Europace AG** - See blog post [InnerSource: Adding base documentation](https://tech.europace.de/post/innersource-base-documentation/)
+* **Paypal Inc.**
+* **Mercado Libre** - create a documentation site that contains how to get started with InnerSource and also define the basic artifacts that a repository must have to be InnerSource (README, CONTRIBUTING, CODING_GUIDELINES, etc).
+* **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).
## Authors