Adding GovTech GPSL as a Known Instance to the InnerSource License pa…

…ttern (#605) * Remove space in tablet, to get the content to render correctly in the ToC * Preparing structure to allow us to capture multiple known instances * Adding GovTech (Singapore Government) as a known instance to the InnerSource License pattern. Description based on ISC community call. --------- Co-authored-by: spier <[email protected]>
InnerSourceCommons · Mar 5, 2024 · b27a5c7 · b27a5c7
1 parent 04caa7c
commit b27a5c7
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 4 deletions.
diff --git a/book/en/toc.md b/book/en/toc.md
@@ -30,7 +30,7 @@ Instead edit toc_template.md
 * [Extensions for Sustainable Growth](../../patterns/2-structured/extensions-for-sustainable-growth.md) - An InnerSource project is receiving too many contributions, making maintenance difficult. By offering an extension mechanism outside of the core project, the maintainers enable scaling of project capabilities with minimal cost and maintenance overhead.
 * [Gig Marketplace](../../patterns/2-structured/gig-marketplace.md) - Establish a marketplace by creating an intranet website that lists specific InnerSource project needs as "Gigs" with explicit time and skill requirements.  This will enable managers to better understand their employee’s time commitment and professional benefits thereby increasing the likelihood of garnering approval to make InnerSource contributions.
 * [Group Support](../../patterns/2-structured/group-support.md) - What happens if a team or individual no longer supports an InnerSource project? Keep the project alive by forming a group of interested individuals.
-* [InnerSource License](../../patterns/2-structured/innersource-license.md) - Two legal entities that belong to the same organization want to share software source code with each other but they are concerned about the implications in terms of legal liabilities or cross-company accounting.
+* [InnerSource License](../../patterns/2-structured/innersource-license.md) - Two legal entities that belong to the same organization want to share software source code with each other but they are concerned about the implications in terms of legal liabilities or cross-company accounting. An InnerSource License provides a reusable legal framework for the sharing of source code within the organization. This opens up new collaboration options, and makes the rights and obligations of the involved legal entities explicit.
 * [InnerSource Portal](../../patterns/2-structured/innersource-portal.md) - Potential contributors cannot easily discover InnerSource projects that they are interested in. By creating an intranet website that indexes all available InnerSource project information you enable contributors to learn about projects that might interest them and InnerSource project owners to attract an outside audience.
 * [Issue Tracker Use Cases](../../patterns/2-structured/issue-tracker.md) - The InnerSource host team fails to make not only plans and progress but also context for changes transparent. This is solved by increasing the use cases for the project issue tracker to also serve brainstorming, implementation discussion, and feature design.
 * [Maturity Model](../../patterns/2-structured/maturity-model.md) - Teams have started adopting InnerSource. The practice is spreading to multiple departments. However, the understanding of what constitutes an InnerSource project varies. The solution is to provide a maturity model to allow for teams to go through a self check and discover patterns and practices that they are not yet aware of.

diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md
@@ -5,7 +5,6 @@ InnerSource License
 ## Patlet
 
 Two legal entities that belong to the same organization want to share software source code with each other but they are concerned about the implications in terms of legal liabilities or cross-company accounting.
-
 An **InnerSource License** provides a reusable legal framework for the sharing of source code within the organization. This opens up new collaboration options, and makes the rights and obligations of the involved legal entities explicit.
 
 ## Problem
@@ -55,8 +54,9 @@ The license simplifies the conversations within our organization about sharing s
 - **DB Systel**
 - **Robert Bosch GmbH**
 - **Airbus**
+- **GovTech (Singapore Government)**
 
-## DB Systel
+### DB Systel
 
 DB Systel created their own InnerSource License, see [DB Inner Source License][db-inner-source-license]. They used the [EUPL][eupl], as that offered an open source like starting point, and then worked out the constraints and additional rules required in their specific organizational context.
 
@@ -73,10 +73,19 @@ The mentioned collaboration challenges include:
 
 It is worth mentioning that so far the software shared under this InnerSource license is mostly tooling, infrastructure, and tools lower in the stack.
 
-## Airbus
+### Airbus
 
 Airbus created ad hoc InnerSource licenses to enable InnerSource way of working within a large part of the group.
 
+### GovTech (Singapore Government)
+
+GovTech is responsible for the delivery of the Singapore government's digital services to the public.
+They created the GovTech Public Sector License (GPSL) as a permissive license to ensure that code can be shared between legal entities across government.
+The GPSL covers both usage of code by licensees (agencies and their vendors) as well as contributions back to GovTech.
+Following open source practices, the GPSL `LICENSE` file is included in each repository that is made available as InnerSource.
+
+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.
+
 ## Status
 
 * Structured