How to Maintain Open Source Compliance After Code Changes

Posted by bob on Mar 17, 2017 3:06 AM EDT
Linux.com - Original Content; By Ibrahim Haddad
Mail this story
Print this story

The previous article in this series covered how to establish a baseline for open source software compliance by finding exactly which open source software is already in use and under which licenses it is available. But how do you make sure that future revisions of the same product (or other products built using the initial baseline) stay compliant once the baseline is established?

Full Story

  Nav
» Read more about: Story Type: News Story; Groups: Linux

« Return to the newswire homepage

This topic does not have any threads posted yet!

You cannot post until you login.