Relicensing: what's legal and what's right
Relicensing: what's legal and what's right
Posted Sep 4, 2007 19:41 UTC (Tue) by ncm (guest, #165)In reply to: Relicensing: what's legal and what's right by butlerm
Parent article: Relicensing: what's legal and what's right
It is simply not true that the BSD license text in a dual-licensed work "must be preserved of course". Yes, it says so in the BSD license text itself, but the dual-licensing specifically allows you to ignore any or all requirements in the BSD text, if you choose to distribute under the other license -- not excepting that one.
Theo is completely wrong on his legal argument. That doesn't mean he's wrong when he says it's rude not to dual-license further changes. Rudeness is, after all, something he knows far more about than most of us.
Non-BSD people often wonder at the seeming logical loopiness in BSD license reasoning. However, there is method to be discovered there, although it took me a long time to find it. The freedom BSD people want to retain is the right to take the code they have written (and the code in which it's embedded) and use it in any employer's product, even if that product will be proprietary. If they and their colleagues release their code under GPL, then the list of employers where they can use their own code gets much smaller.
