You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: patterns/2-structured/30-day-warranty.md
+1
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,7 @@ In addition it helps to provide clear [contribution guidelines](./base-documenta
49
49
- This was tried and proven successful at PayPal.
50
50
- GitHub internally uses this pattern with a modified warranty timeline of 6 weeks.
51
51
- Microsoft recommends this pattern as a principle - teams set their own specific time target matching their needs and confidence.
52
+
- SAP - see: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
Copy file name to clipboardExpand all lines: patterns/2-structured/praise-participants.md
+1
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,7 @@ Overdoing it may feel insincere and mechanical and defeat your purpose in reachi
68
68
## Known Instances
69
69
70
70
* Nike (multiple projects)
71
+
* SAP - see: [InnerSource: First Contribution Explored](https://community.sap.com/t5/open-source-blogs/innersource-first-contribution-explored/ba-p/13644916)
0 commit comments