Hacker News new | ask | show | jobs
by zdw 5307 days ago
The GPL is fundamentally a protection against companies distributing private modified forks. It wasn't created to give BSD code creators a bad day - basically what you're describing is collateral damage. I think most reasonable non-zealot OSS developers totally understand where you're coming from.

An interesting twist would be a BSD style license that states that if the code is incorporated into a GPL style licensed project, patches to your specific code subset must also be BSD licensed. Kind of like incorporating a LGPL library into a commercial product.

1 comments

> An interesting twist would be a BSD style license that states that if the code is incorporated into a GPL style licensed project, patches to your specific code subset must also be BSD licensed.

I've used mixed licenses to achieve this in the past. The individual source files remain BSD licensed. The whole work, in aggregate, is GPL licensed.

It only works if the dependencies are one-way, though, and you keep the BSD code fairly isolated.