From 5e711f0133f5f58ab98e4c03b0475c63036e37c8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Georg=20Gr=C3=BCtter?= Date: Fri, 24 Nov 2023 21:57:15 +0100 Subject: [PATCH] InnerSource License: Added Robert Bosch GmbH as known instance (#532) * Added Robert Bosch GmbH as Known Instance * Add another force related to possible relicensing when moved from InnerSource to open source * Reformatting pattern, to include Airbus reference (pulled in via last update from main) --------- Co-authored-by: Sebastian Spier --- patterns/2-structured/innersource-license.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/patterns/2-structured/innersource-license.md b/patterns/2-structured/innersource-license.md index 54b5c55a3..169ea8a17 100644 --- a/patterns/2-structured/innersource-license.md +++ b/patterns/2-structured/innersource-license.md @@ -32,6 +32,7 @@ At the time of sharing the source code, it can not be reliably predicted what th - Freedom over using the software leads to competition, and spread of ownership - There are legal contracts in place which cover the sharing of source code. These contracts are not standardized, so they create additional effort in negotiating and understanding for every project. The existing contracts may also not allow sharing source code in an open enough sense to support a true InnerSource approach. - Alternatively, there are no legal contracts in place but source code is shared informally. That might create uncertainty in cases where clarity about ownership and rights and obligations is needed. +- Choosing a restrictive and/or copyleft license can constitute a barrier for InnerSource adoption. Specifically, limiting publication to the organisation might require a costly relicensing procedure prior to transitioning to Open Source. ## Solutions @@ -51,6 +52,12 @@ The license simplifies the conversations within our organization about sharing s ## Known Instances +- **DB Systel** +- **Robert Bosch GmbH** +- **Airbus** + +## 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. The first legal entities (companies) within the DB AG are using their InnerSource License. @@ -66,6 +73,8 @@ 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 created ad hoc InnerSource licenses to enable InnerSource way of working within a large part of the group. ## Status