4 ms·
Would this mean that only their changes to the GPL would be forced to be made public or the whole piece of software using it?
by mhh__ 7y ago
Would this mean that only their changes to the GPL would be forced to be made public or the whole piece of software using it?
- Wowfunhappy 7y agoThe whole thing.
- thrower123 7y agoThis is one reason I hate npm. Who really checks that sprawling byzantine dependency tree to make sure that there isn't some micropackage that has a GPL license that could get included and taint the whole thing? I just have the horrors when I look at the package.json file after the front-end folks have been allowed to run free...
- a_t48 7y agoShouldn't this be something that npm could support checking as a first class feature?
- deleted 7y ago[deleted]
- TheAceOfHearts 7y agoThere's tools [0] to help check the licenses of all your dependencies. I think larger companies build up a whitelist of libraries as they're reviewed and approved. [0] https://github.com/davglass/license-checker https://github.com/davglass/license-checker
- nfriedly 7y agoYep. When I was at IBM, part of releasing something was a review every of dependency and it's license. The stuff I worked on wasn't allowed to include any GPL code. (Or WTFPL, for that matter, but I think that had more to do with curse words than actual license issues.)
- Wowfunhappy 7y agoCouldn't you just "relicense" WTFPL code as MIT code (or proprietary code, for that matter) and call it a day?
- nfriedly 7y agoHaha, probably, but it wasn't a big deal to replace it with something else.
- Wowfunhappy 7y agoShouldn't you be more concerned about the quality of the code? If no one has bothered to check the license, I'm sure nobody has studied it for a backdoor.
- thrower123 7y agoThere are many reasons. That is another huge one. Most of the time, nobody even is aware that including some new widget code ends up downloading half the internet, making our code size increase, our build times extend, and opening up a huge volume of attack. No one has any idea what dragons might lurk in that mess, or sometimes even that there might be dragons at all.
- wltprgm 7y agoone can hope that front-end and back-end are truly separated
- giancarlostoro 7y agoCorrect and if nobody asks they are fine in doing so. But they must comply if possible. If the code is gone then I am not sure they can be forced to give it.
- vageli 7y ago> Correct and if nobody asks they are fine in doing so. But they must comply if possible. If the code is gone then I am not sure they can be forced to give it. There must be some kind of remedy available in that event.
- NedIsakoff 7y agoMoney
- giancarlostoro 7y agoUsually to the original developers (Authors of the licensed works) from which the GPL code came from.
- tptacek 7y agoThey would have to release the whole thing to come into compliance with the license, but they are not obligated to do so.