From a99a4d62fde83a5be610c5d84d1e51407adedef6 Mon Sep 17 00:00:00 2001 From: Michael Basil Date: Mon, 8 Apr 2024 10:12:18 -0500 Subject: [PATCH] feat(30-day-warranty): SAP known instance teaser (#679) * feat(30-day-warranty): SAP known instance teaser --- patterns/2-structured/30-day-warranty.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/2-structured/30-day-warranty.md b/patterns/2-structured/30-day-warranty.md index 962301d6a..b21ab814d 100644 --- a/patterns/2-structured/30-day-warranty.md +++ b/patterns/2-structured/30-day-warranty.md @@ -49,7 +49,7 @@ In addition it helps to provide clear [contribution guidelines](./base-documenta - 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 - see: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916) +- 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