From 36b0e805e4e59bd70dae59fb27e94c72bb945698 Mon Sep 17 00:00:00 2001 From: Mary Hardy Date: Wed, 6 May 2026 16:27:51 -0700 Subject: [PATCH] Update guidance on open source review requests timing Revised the recommendation for initiating open source review requests to emphasize early action in the product development process. --- ...enting Open Source License Compliance Management (LFC194).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md b/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md index f617570..e239c52 100644 --- a/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md +++ b/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md @@ -596,7 +596,7 @@ It can be prevented by implementing blocks in approvals in the open source compl #### Failure to seek review of open source in a timely manner -This type of failure can be avoided by initiating open source review requests regardless of whether the engineering team has confirmed the adoption of the open source code. +This type of failure can be avoided by initiating open source review requests early in the product development. It can be prevented through education or, if the cause is lack of resources, by increasing resources (e.g., invest in more skilled people, more frequent review meetings, tools, etc.).