From 77af3e609fc34745f046e4c7a30b7fda6bd1a225 Mon Sep 17 00:00:00 2001 From: Mary Hardy Date: Wed, 6 May 2026 16:33:29 -0700 Subject: [PATCH] Removed an answer option regarding benefits of compliance Establishing a relationship with an open source project is a nice-to-have, but not a requirement for license compliance as presented here --- ...menting Open Source License Compliance Management (LFC194).md | 1 - 1 file changed, 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..416e1bc 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 @@ -637,7 +637,6 @@ Good relationships with the software communities are helpful in enhancing two-wa - The final product will be functional and high quality → Incorrect Answer - Potential compliance mistakes are addressed early --> Correct answer - Open source is used more efficiently and in a compliant manner --> Correct answer - - Meaningful relationships with the open source community are established --> Correct answer - There are no benefits, compliance generates additional cost in money and time → Incorrect Answer # Chapter 5. Developer Guidelines