On the 'death penalty' thing
On the 'death penalty' thing
Posted Feb 2, 2012 14:37 UTC (Thu) by khim (subscriber, #9252)In reply to: On the 'death penalty' thing by hummassa
Parent article: A tempest in a toybox
This just does not happen... or should not happen. In any case, if people commit *proprietary* stuff to the repository without due dilligence, the stakes are really higher.
Absolutely not. In fact this is standard industry practiceâ„¢: You commit everything to repository - SDKs, all the tools, compilers, etc. Everything. This may be formal violation of the license for some tools, but even this is not enforceable in most jurisdictions (if you have enough licenses to cover all the developers then you can just say you use repository for backup purposes). As long you don't distribute content of your repo everything is fine. But if you want to publish GPLed part then you need to separate the wheat from the lentil!
Again, everyone should just act -- in the prep of a software-including product -- just as they would if free-licensed software pieces were proprietary-licensed software pieces: with due dilligence.
It's much harder with free software. With proprietary software you usually don't have sources to modify, thus chance of mistakes is small. In some rare cases you do - but even then you mostly use vendor-supplied binaries and use sources only as reference. With free software not only you have sources - you often need to modify them slightly to make them usable (compileable, for example)! This raises risk of accidental violation hundredfold (if not thousandfold).
I can't in good conscience call the process which requires strict rules and serious effort "trivial", sorry. It's not that hard (some proprietary tools require significantly more work if you want to stay compliant), but it's not "trivial" either.
