News for hackers. Stuff that matters.
Re:Mono Relicensed as MIT by twblalock on Thursday March 31, 2016 @03:52PM (#11400102)
It would be trivially easy for an engineer to add a GPL-licensed dependency to a project without realizing it, perhaps via a transitive dependency, thereby causing the company to be in breach of the GPL.

If you don't audit, you don't know if you are in breach of the GPL or not. Your corporate counsel will want you to audit. You can't reasonably take any action, including open sourcing your project or even posting code snippets on a company engineering blog, until you know which licenses you actually use.

Re:Mono Relicensed as MIT by belorn on Thursday March 31, 2016 @05:12PM (#11400588)
Its about as trivial as for a web developer to accidentally use a proprietary image they found on the web, a game developer that use the unreal engine, or a marketing using someones music in a commercial.

Its quite common to find commercial copyright infringement in all of those (except for the unreal engine, since I don't know publicized case of that), and there are artists who earn a fair income by contacting infringes and demand payment or a cease and desist. I wouldn't however describe that as being bitten by the rightful author, but put the blame on the developer who is using someone else work without permission, especially if they their own business model is based on copyright.

Re:Mono Relicensed as MIT by cyphar on Thursday March 31, 2016 @08:06PM (#11401571)
> It would be trivially easy for an engineer to add a GPL-licensed dependency to a project without realizing it, perhaps via a transitive dependency, thereby causing the company to be in breach of the GPL.

Just as easily as it is for a designer to use a copyrighted work. The GPL isn't a boogieman, every project that's under the GPL says so. If a developer isn't mindful enough to realise that they shouldn't randomly copy-paste library dependencies without knowing anything about them isn't a very good developer.

Re:Mono Relicensed as MIT by twblalock on Thursday March 31, 2016 @08:48PM (#11401777)
Try running mvn:dependency-tree on any large enterprise Java project, and see what comes out. If you told me you were familiar with every single library in the output, I would not believe you.
Re:Mono Relicensed as MIT by cyphar on Thursday March 31, 2016 @09:35PM (#11401963)
Doesn't mvn show license information?
Re:Mono Relicensed as MIT by WayneBro on Sunday April 03, 2016 @10:17AM (#11416167)
> If a developer isn't mindful enough to realise that they shouldn't randomly copy-paste library dependencies without knowing anything about them isn't a very good developer.

That's a logical fallacy called: No true Scotsman. In this case - Good developers can be good at some things but bad at other things, so there's absolutely zero correlation between "good/bad developers" and "people who remember/forget to think about licensing".

Re:Mono Relicensed as MIT by WayneBro on Sunday April 03, 2016 @10:07AM (#11416131)
If you don't consider the GPL to be boogieman, how do you feel about predatory lenders and loan sharks? All of them are just agreements...right?

In a predatory lending/loan sharking scheme, the lender offers their product (money) to people who need it (borrowers) who must agree to extraordinarily high interest rates.

This seems very similar to the GPL since it's just a software agreement that includes extraordinary clauses for developer who "borrows" the product.

Re:Mono Relicensed as MIT by klodolph on Thursday March 31, 2016 @04:01PM (#11400164)
It's not just that corporate counsel will want you to audit. I worked at a company where I found a GPL violation and wanted to comply, but if we started complying with the GPL it would have shown that we knew that we previously hadn't been complying, so I was told to not comply. Ugh. Just for redistributing a couple binaries, there were no libraries involved.