From a93e1b924977733c9404611af11d79a1ca6593c7 Mon Sep 17 00:00:00 2001 From: Jayendran Arumugam <25414541+jayendranarumugam@users.noreply.github.com> Date: Sun, 14 Jan 2024 17:21:11 +0530 Subject: [PATCH] Fixing broken link --- docs/measuring_success.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/measuring_success.md b/docs/measuring_success.md index 6ec3826..37d058f 100644 --- a/docs/measuring_success.md +++ b/docs/measuring_success.md @@ -36,7 +36,7 @@ Here is a list of some recommended checklist items to review when adopting Inner ## Expanding your checklist -Many companies have already adopted InnerSource or are currently in the process. There is a lot of great information from many resources including [InnerSource Commons](https://innersourcecommons.org/) and [PayPal's journey](https://innersourcecommons.org/assets/files/InnerSourceChecklist.pdf) just to name a few. Below is an expanded checklist compiled from many resources including PayPal, GNU Manifesto, and the Apache Way. +Many companies have already adopted InnerSource or are currently in the process. There is a lot of great information from many resources including [InnerSource Commons](https://innersourcecommons.org/) and [PayPal's journey](https://innersourcecommons.org/documents/books/InnerSourceChecklist.pdf) just to name a few. Below is an expanded checklist compiled from many resources including PayPal, GNU Manifesto, and the Apache Way. ### Team - [ ] **Are team members ready for the challenges of InnerSource?**