Skip to content

Commit 4a1091a

Browse files
committed
Merge branch 'main' into career-booster
2 parents c5d7bd3 + a4c8487 commit 4a1091a

File tree

9 files changed

+97
-20
lines changed

9 files changed

+97
-20
lines changed

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,7 @@ Our mission
9393
* [Circle Communities](/patterns/1-initial/circle-communities.md) - *InnerSource adoption is slow in organizations due to limited understanding, engagement, and contextual relevance. Circle Communities address this by fostering synchronous conversations that build connections, close knowledge gaps, and cultivate collaboration and continuous learning.*
9494
* [Internal Developer Platform](/patterns/1-initial/internal-developer-platform.md) - *As InnerSource adoption increases throughout an organisation, it is not unusual that project teams start to face inefficiencies in scaling their efforts due to fragmented tooling, environments, and workflows. An Internal Developer Platform (IDP) provides a way to tackle this type of challenges through a centralized, self-service system that standardizes development environments and integrates tools to enhance consistency, collaboration, and developer productivity.*
9595
* [Document Architecture Decisions](/patterns/1-initial/document-architecture-decisions.md) - *InnerSource contributors often face challenges in grasping the system's design rationale, which can result in misalignment between maintainers, contributors, and stakeholders — potentially discouraging participation. To enhance decision-making and transparency, we recommend capturing architecture decisions and their consequences in a lightweight, accessible format to streamline onboarding, clarify decisions, and support long-term project sustainability.*
96+
* [InnerSource Incentives and Disincentives](/patterns/1-initial/incentives-and-disincentives.md) - *Lack of awareness for incentives as well well as disincentives for InnerSource contribution decrease the chances of an InnerSource project receiving contributions; this is addressed by sharing a comprehensive list of potential incentives and disincentives.
9697

9798
<!--
9899
NOTE: The 'Initial' Patterns below don't have a Patlet yet, which is essential for readers to quickly browse our patterns.

pattern-categorization/package-lock.json

Lines changed: 9 additions & 9 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
## Title
2+
3+
InnerSource Incentives and Disincentives
4+
5+
## Patlet
6+
7+
Lack of awareness for incentives as well well as disincentives for InnerSource contribution decrease the chances of an InnerSource project receiving contributions; this is addressed by sharing a comprehensive list of potential incentives and disincentives.
8+
9+
## Problem
10+
11+
Soliciting contributions to an InnerSource project in a corporate environment, where every potential contributor is fully utilized is a difficult task.
12+
Contribution will likely contribute only, if there is an incentive for them to do so and if disincentives are absent.
13+
Without awareness of these incentives and disincentives, a maintainer will likely face challenges actively soliciting contributions.
14+
It is important for Trusted Committers to be aware of and advertise incentives for potential contributors.
15+
16+
## Context
17+
18+
* Potential contributors in a corporate environment are most likely fully utilized and have no "free" time to contribute to InnerSource projects, especially when they are not directly related to their work.
19+
* Especially in early stages of InnerSource adoption, potential contributors as well as inexperienced Trusted Committers might not be aware of the incentives of InnerSource contribution.
20+
21+
## Forces
22+
23+
* The more awareness a Trusted Committer has for the potential incentives and disincentives for InnerSource contribution, the more likely will they be able to successfully advertise them and successfully solicit contributions.
24+
* The higher the incentive to contribute to an InnerSource project, the more likely it will receive contributions.
25+
* The more potential contributors are aware of incentives for InnerSource contribution, the more likely is their contribution.
26+
* Even small disincentives will likely deter potential contributors to contribute.
27+
28+
## Solutions
29+
30+
The incentives and disincentives for InnerSource contribution depend on the concrete organizational context of the InnerSource program.
31+
This pattern provides a list of potential incentives and disincentives for InnerSource contribution, which allows both Trusted Committers and potential Contributors to quickly assess, which incentives and disincentives are present in their concrete context.
32+
These are listed in alphabetical order in the following two sections.
33+
34+
### Potential Incentives
35+
36+
* **Achieving mastery** in your craft
37+
* **Autonomy** in how contributions are crafted
38+
* **Collaboration with like-minded people**
39+
* **Free stuff**, such as e. g. free CI/CD infrastructure
40+
* Help other people **grow personally**, specifically as a Trusted Committer
41+
* **Intellectual Challenge**
42+
* **Making work easier/more productive/more fun** for yourself and your peers
43+
* **Personal mobility** within the organization, e. g. by collaboration with peers outside of your team, gaining visibility and the opportunity to move to different areas of the organization
44+
* **Sense of Impact** of ones contribution inside and outside of the organization
45+
* **Showcasing your successes** and receiving feedback and appreciation
46+
* **Time to contribute**, so that contributions can be made during working hours
47+
48+
### Potential Disincentives
49+
50+
* **Absence or lack of free, essential development infrastructure** such as e. g. CI/CD infrastructure
51+
* **Conflicting InnerSource related goals or incentives in the leadership hierarchy** leading to ambiguity and dissatisfaction by all parties involved in InnerSource
52+
* **For managers: high transparency for their peers in how the managers staff contributes to InnerSource projects**, especially when there is financial pressure and a significant amount of contributions are made outside of their "silo" and leading to local optimization
53+
* **Local optimization**, impeding contributions to "non-local" projects (different silo)
54+
* **Monetary rewards** for knowledge workers (see [RSA Animate on Motivation (by Dan Pink)](https://www.youtube.com/watch?v=u6XAPnuFjJc))
55+
* **No or lack of time to contribute during working hours**, resulting in InnerSource being on-top effort
56+
* **Too much freedom**, resulting in fragmentation and lack of orientation and alignment
57+
58+
## Resulting Context
59+
60+
Both Trusted Committers and (potential) Contributors are aware of the _potential_ incentives and disincentives for InnerSource contribution.
61+
They can assess which incentives and disincentives are present in their context and thus make an informed and balanced decision, whether or not to contribute.
62+
It is less likely that potential contributors don't contribute due to unawareness of incentives.
63+
Trusted Committers can actively leverage incentives when soliciting contributions.
64+
65+
## Known Instances
66+
67+
TBD
68+
69+
## Authors
70+
71+
* Georg Grütter (Robert Bosch GmbH)
72+
73+
## Status
74+
75+
* Initial
76+
* Drafted at the InnerSource Gathering Berlin 2025

patterns/2-structured/innersource-portal.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ InnerSource projects at your organization are increasing but potential contribut
1414

1515
## Story
1616

17-
You are attempting to establish an InnerSource practice within your organization. You are aware of some projects being run using an InnerSource model but their existence is only being communicated via word of mouth, email or sidebar conversations with other employees. As a result InnerSource project owners are finding it difficult to attract contributors.
17+
You are attempting to establish an InnerSource practice within your organization. You are aware of some projects being run using an InnerSource model but their existence is only being communicated via word of mouth, email or sidebar conversations with other employees. As a result InnerSource project owners are finding it difficult to attract contributors.
1818

19-
There is no single, shared resource for employees across the organization to access which will allow them to easily discover all ongoing InnerSource projects. This is severely limiting the growth potential of every InnerSource project.
19+
There is no single, shared resource for employees across the organization to access which will allow them to easily discover all ongoing InnerSource projects. This is severely limiting the growth potential of every InnerSource project.
2020

2121
What can be done to help all InnerSource projects raise their visibility to as large an audience as possible and attract contributors organization-wide?
2222

@@ -45,9 +45,9 @@ Create an InnerSource Portal intranet website where InnerSource project owners c
4545

4646
Key properties of the portal are:
4747

48-
* Visitors to the InnerSource Portal should be able to see all available projects as well as search for specific projects based on various criteria such as project name, technologies in use, contributor names, sponsoring business unit etc.
49-
* The information displayed via the InnerSource Portal should be under the full control of the InnerSource project owners at all times. Preferably, by sourcing this information directly from a specific data file or meta-data stored in the project repository itself.
50-
* Project owners should include all relevant information concerning their projects within those data files including the project name, trusted contributors' names, a brief description and links to the code repository or any supporting documentation.
48+
* Visitors to the InnerSource Portal should be able to see all available projects as well as search for specific projects based on various criteria such as project name, technologies in use, contributor names, sponsoring business unit etc.
49+
* The information displayed via the InnerSource Portal should be under the full control of the InnerSource project owners at all times. Preferably, by sourcing this information directly from a specific data file or meta-data stored in the project repository itself.
50+
* Project owners should include all relevant information concerning their projects within those data files including the project name, trusted contributors' names, a brief description and links to the code repository or any supporting documentation.
5151
* (optional) While most organizations will choose to make their portal only available on their intranet, some organizations have opted to make their portal available on the public internet. The latter can be interesting for organizations that want to show additional information about their InnerSource approach in their portal e.g. for branding and recruitment purposes.
5252

5353
When launching the portal, a communications campaign promoting the addition of InnerSource data files or meta-data to code repositories should be considered, to bolster the number of projects displayed within the portal.
@@ -99,7 +99,7 @@ It is a good solution for a portal with a few dozen projects, though.
9999
* [Gamification As Means of Cultural Change and InnerSource Engagement Booster](https://www.oreilly.com/library/view/oscon-2018-/9781492026075/video321579.html) | Shelly Nizri | OSCON 2018 - Portland, Oregon
100100
* Of Islands, Monsters & InnerSource [(slides)](https://docs.google.com/presentation/d/1P1OCEK9B6eSrVRUclVWY6meSI-qHOBjM_UAPNvCZamU/edit#slide=id.p15), [(video)](https://drive.google.com/file/d/1pM89uHMn0vhE3ayFJDGYcCO8R0tAXXZD/view?usp=drivesdk) | InnerSource Spring Summit 2019 (Galway, Ireland)
101101
* The [code](https://gitlab.com/gilda2) realizing this platform has been open sourced.
102-
* **American Airlines** promotes InnerSource projects via an [internal InnerSource Marketplace](https://tech.aa.com/2020-10-30-innersource/). Similarly to SAP, projects self-register by adding `innersource` as a GitHub topic. Projects are searchable and filterable by language, topics, number of open issues, etc.
102+
* **American Airlines** promotes InnerSource projects via an [internal InnerSource Marketplace](https://web.archive.org/web/20240226230502/https://tech.aa.com/2020-10-30-innersource). Similarly to SAP, projects self-register by adding `innersource` as a GitHub topic. Projects are searchable and filterable by language, topics, number of open issues, etc.
103103
* **Banco Santander** has created a public portal called "Santander ONE Europe InnerSource Community" to support and increase InnerSource adoption. In addition to the catalog of projects the portal includes relevant content such as documentation, way of working, news, and events.
104104

105105
![Santander InnerSource Portal](../../assets/img/santander_portal.png "Banco Santander InnerSource Portal")

translation/es/patterns/innersource-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ Es una buena solución para un portal con unas pocas docenas de proyectos, sin e
9999
* [Gamificación Como Medio de Cambio Cultural y Potenciador de Compromiso InnerSource](https://www.oreilly.com/library/view/oscon-2018-/9781492026075/video321579.html) | Shelly Nizri | OSCON 2018 - Portland, Oregon
100100
* De Islas, Monstruos y InnerSource [(diapositivas)](https://docs.google.com/presentation/d/1P1OCEK9B6eSrVRUclVWY6meSI-qHOBjM_UAPNvCZamU/edit#slide=id.p15), [(video)](https://drive.google.com/file/d/1pM89uHMn0vhE3ayFJDGYcCO8R0tAXXZD/view?usp=drivesdk) | InnerSource Spring Summit 2019 (Galway, Irlanda)
101101
* El [código](https://gitlab.com/gilda2) que realiza esta plataforma ha sido de código abierto.
102-
* **American Airlines** promueve proyectos InnerSource a través de un [Mercado Interno InnerSource](https://tech.aa.com/2020-10-30-innersource/). De manera similar a SAP, los proyectos se auto-registran agregando `innersource` como un tema de GitHub. Los proyectos son buscables y filtrables por idioma, temas, número de problemas abiertos, etc.
102+
* **American Airlines** promueve proyectos InnerSource a través de un [Mercado Interno InnerSource](https://web.archive.org/web/20240226230502/https://tech.aa.com/2020-10-30-innersource). De manera similar a SAP, los proyectos se auto-registran agregando `innersource` como un tema de GitHub. Los proyectos son buscables y filtrables por idioma, temas, número de problemas abiertos, etc.
103103
* **Banco Santander** ha creado un portal público llamado "Santander ONE Europe InnerSource Community" para apoyar e incrementar la adopción de InnerSource. Además del catálogo de proyectos, el portal incluye contenido relevante como documentación, forma de trabajo, noticias y eventos.
104104

105105
![Portal InnerSource de Santander](../../../assets/img/santander_portal.png "Portal InnerSource de Banco Santander")

translation/gl/patterns/innersource-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Unha [implantación de referencia](https://github.com/SAP/project-portal-for-inn
7070
* [Gamificación como medio de cambio cultural e potenciador de compromiso InnerSource](https://www.oreilly.com/library/view/oscon-2018-/9781492026075/video321579.html) | Shelly Nizri | OSCON 2018: Portland, Oregon.
7171
* De islas, monstros e InnerSource [(presentación)](https://docs.google.com/presentation/d/1P1OCEK9B6eSrVRUclVWY6meSI-qHOBjM_UAPNvCZamU/edit#slide=id.p15), [(vídeo)](https://drive.google.com/file/d/1pM89uHMn0vhE3ayFJDGYcCO8R0tAXXZD/view?usp=drivesdk) | Cume InnerSource primavera de 2019 (Galway, Ireland).
7272
* O [código](https://gitlab.com/gilda2) desta plataforma era de software libre.
73-
* **American Airlines** promove proxectos InnerSource a través dun [*Marketplace* InnerSource interno](https://tech.aa.com/2020-10-30-innersource/). Do mesmo xeito que SAP, os proxectos autorrexístranse engadindo InnerSource como tema de GitHub. Os proxectos pódense buscar e filtrar por idioma, temas, número de incidencias abertas etc.
73+
* **American Airlines** promove proxectos InnerSource a través dun [*Marketplace* InnerSource interno](https://web.archive.org/web/20240226230502/https://tech.aa.com/2020-10-30-innersource). Do mesmo xeito que SAP, os proxectos autorrexístranse engadindo InnerSource como tema de GitHub. Os proxectos pódense buscar e filtrar por idioma, temas, número de incidencias abertas etc.
7474
* **Banco Santander** creou un portal público chamado «Santander ONE Europe InnerSource Community» para dar soporte e mellorar a adopción de InnerSource. Ademais do catálogo de proxectos, o portal inclúe contidos relevantes como documentación, forma de traballar, noticias e eventos.
7575

7676
![Portal Santander InnerSource](../../../assets/img/santander_portal.png "Portal Santander InnerSource")

translation/ja/patterns/innersource-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@
7373

7474
コードはオープンソース化されており、[gitlab.com/gilda2](https://gitlab.com/gilda2)にて公開されています。
7575

76-
* **アメリカン航空**は、[インターナルインナーソースマーケットプレイス](https://tech.aa.com/2020-10-30-innersource/)を介してInnerSourceプロジェクトを推進しています。SAPと同様に、プロジェクトはGitHubのトピックとして `innersource` を追加することで自己登録されます。プロジェクトは、言語、トピック、オープンイシューの数などで検索やフィルタリングが可能です。
76+
* **アメリカン航空**は、[インターナルインナーソースマーケットプレイス](https://web.archive.org/web/20240226230502/https://tech.aa.com/2020-10-30-innersource)を介してInnerSourceプロジェクトを推進しています。SAPと同様に、プロジェクトはGitHubのトピックとして `innersource` を追加することで自己登録されます。プロジェクトは、言語、トピック、オープンイシューの数などで検索やフィルタリングが可能です。
7777

7878
* **Banco Santander**社は、インナーソースをサポートして増やすために、Santander ONE Europe InnerSource Communityという公開ポータルを作成しました。このポータルには、プロジェクトのカタログに加え、ドキュメント、仕事の進め方、ニュース、イベントなどの関連コンテンツが含まれています。
7979

0 commit comments

Comments
 (0)