Slashdot Mirror


Bruce Perens On Combining GPL and Proprietary Software

jammag writes "Combining GPL and proprietary software is ever more common, especially in the world of embedded devices like cell phones. But the question is: how to combine them legally. As sticky as the issue is, there is an answer, as self titled "open source strategic consultant" Bruce Perens explains. The proper procedure entails fully understanding what type of open source software you're using, and knowing why you need to combine these disparate licenses. The problem, he notes, is that many companies don't know or care about doing this legally. 'They're used to just "clicking yes" with no regard to what they're committing themselves and their company to.' Hopefully Perens' guide can be read by more company execs — resulting in fewer lawsuits going forward (but we're not holding our breath)." update 21:31 GMT by SM: Bruce wrote in to make sure we knew he was not a lawyer, even though he is weighing in on a legal issue; updated to reflect.

2 of 218 comments (clear)

  1. Re:Commitments? by Bruce+Perens · · Score: 5, Insightful

    Most employees aren't legally empowered to commit their company / organisation to anything. They don't have the authority to sign contracts on behalf of the company / organisation.

    Yes. But "my employee did this, and he didn't have authority to do so" hasn't worked very effectively as a defense regarding software license violation and copyright infringement - or anything else. Or those BSA audits would have turned out differently, etc. Ultimately, the stockholders and management are responsible for what the company does even if they are so out of control that their employees do stuff without being instructed to :-)

    Bruce

  2. Re:The silly multi-processor workaround by Bruce+Perens · · Score: 4, Insightful

    GPL3 fixes this for the GPL part. Which is one reason I take GPL3 seriously for my own work.