Now, the projects are largely Javascript (Node / React) based, and this gets unwieldily and puts burden on us to make sure our developers understand the license and what the client's legal team will support. Our engineers are not lawyers, they are not well versed in IP law and under time constraints, so its not uncommon to pick out a package without doing due diligence or submitting it for legal review.
A compromise we made with one client, was saying if the package manifest is available for review in Github then they can veto a package that they see as non-compliant or not up to par.
But some of our newer clients' legal depts are taking things a step further, expecting our team to submit the license for review / approval, and attempting to put the burden on my team for legal liability if an OSS license created a conflict later, redlining that into the contract.
This would create a whole new category of additional work and expense that would slow down timelines and inflate the cost beyond where expectations are set.
What is a good way to deal with this? I've chatted about it with our lawyers and other than fighting these redlines in our contracts, we're not clear on whats a reasonable solution going forward.
No comments yet.
