From e9fbfbeb7d832699f2f07358a373a5d1cb97f019 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 4 Jan 2025 11:09:20 +0100 Subject: [PATCH] Removing optional Story block --- patterns/1-initial/internal-developer-platform.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/patterns/1-initial/internal-developer-platform.md b/patterns/1-initial/internal-developer-platform.md index cc563be7c..44ee4d86f 100644 --- a/patterns/1-initial/internal-developer-platform.md +++ b/patterns/1-initial/internal-developer-platform.md @@ -30,10 +30,6 @@ A lack of standardization across development environments and tools significantl Without a standardized foundation, InnerSource efforts struggle to scale as inconsistencies across teams lead to inefficiencies, delays, and misaligned governance practices. Contributors face challenges in understanding and integrating with unfamiliar environments, while teams resist external contributions due to perceived risks or integration overhead. An Internal Developer Platform (IDP) mitigates these issues by providing a self-service, unified platform that standardizes tools, processes, and environments. This enables InnerSource contributors to focus on delivering value rather than overcoming technical incompatibilities, fostering a culture of collaboration and accelerating the adoption of InnerSource at scale. -## Story (optional) - -(to be done) - ## Context This pattern emerges in organizations with multiple InnerSource development teams working on different projects. As teams grow and evolve, discrepancies in the setup of development environments and access to resources become more prominent, hampering collaboration, introducing security risks, and reducing developer productivity. The need for uniformity without compromising flexibility drives the adoption of an IDP.