On Thu, Nov 21, 2013 at 6:00 AM, Jonathan Wilson <[email protected]> wrote: >> However, would it not be a better practice to maintain the FL/OSS parts in >> an internal repository as an integral part of the device development >> process, > ... > It would be impossible to expect that every change to a FOSS package > (kernel, busybox, whatever else) be vetted to make sure its legally clean > and releasable before it was pushed to the internal tree
Having a lawyer-filter on a git repo would kill productivity, but the vetting process has to happen before a product ships. If you're on a tight release schedule, you've got to budget the appropriate amount of time for review, whether that's a little time each week or a big chunk of time at the end of the project. >... Getting all the legal things right to make sure that the source code is in > compliance with the FOSS licenses..[and etc].. is hard > and takes time. Indeed it can. But if you only take this step after shipping a product, there's no way to revert code that can't legally be released. Or to put it another way, if you clean your car each week, it will stay relatively tidy. If you wait for only once a year, you might find a stain on the carpet that has set and will never come out. --R
