From a2ea409d7f3cfc0fe639f92520712d3d0f074258 Mon Sep 17 00:00:00 2001 From: Michael Basil Date: Sun, 31 Mar 2024 08:59:43 -0500 Subject: [PATCH] Add SAP as known instance for the 30 Day Warranty and Praise Participants patterns (#672) * feat(praise-participants): Add SAP known instance * feat(30-day-warranty): Add SAP known instance --- patterns/2-structured/30-day-warranty.md | 1 + patterns/2-structured/praise-participants.md | 1 + 2 files changed, 2 insertions(+) diff --git a/patterns/2-structured/30-day-warranty.md b/patterns/2-structured/30-day-warranty.md index ce93a1b13..962301d6a 100644 --- a/patterns/2-structured/30-day-warranty.md +++ b/patterns/2-structured/30-day-warranty.md @@ -49,6 +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) ## Authors diff --git a/patterns/2-structured/praise-participants.md b/patterns/2-structured/praise-participants.md index 10271045b..026179ceb 100644 --- a/patterns/2-structured/praise-participants.md +++ b/patterns/2-structured/praise-participants.md @@ -68,6 +68,7 @@ Overdoing it may feel insincere and mechanical and defeat your purpose in reachi ## Known Instances * Nike (multiple projects) +* SAP - see: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916) ## Status