|
|
|
|
|
by nknight
5307 days ago
|
|
No, it's not. The core of why we disagree is your bizarre double standard. There are no circumstances under which I would find a corporation's proprietary use of BSD code more socially acceptable than a GPL project's open-source use of BSD code. This is a fundamental disagreement of principles, not a disagreement about proper enforcement mechanisms. You and I have utterly different views of what the "OSS social contract" is even about, much less says. |
|
It's not a double standard. The purpose of the BSD license to encourage widespread adoption which will hopefully lead to widespread contribution, under the assumption that the best way to encourage adoption and contribution is to not enforce it.
If a commercial vendor uses BSD licensed code for a proprietary product, they can and do still donate code back. If they fail to do so immediately, they might do so in the future -- this often occurs as vendors build larger systems on top of a BSD licensed code base.
The GPL, however, is purpose-built to break the social mechanisms by which BSD licensed code propagates by implementing an irreversibly viral one-way licensing OSS ecosystem. RMS has stated repeatedly that he won't be happy until all software is GPL and it's simply not possible to compete with GPL software due to the network effects of large, interconnected GPL-only software stack.
Finally, legal codification of behavior often has large unintended consequences. Choosing to use social pressure to discourage certain uses of your software while not legally forbidding it does not create a double standard.