| ext_260933 ( |
I'm conflicted on this one.
While the underlying reasons are lame and undesirable from an OSS perspective, I'm having a hard time finding fault here. It's like the old joke about Doctor's advice that says, if it hurts when they do something, they should probably stop doing it. In this case, if using GPLed code is getting them sued, one possible solution is to comply with the license, the other solution is to simply stop using GPLed code. Both are equally valid choices, even if one is less desirable from an OSS advocacy perspective.
The onus is on the OSS community to clearly articulate the value provided by compliance that exceeds the value achieved by going back to a mix of proprietary and BSD licensed code.
While the underlying reasons are lame and undesirable from an OSS perspective, I'm having a hard time finding fault here. It's like the old joke about Doctor's advice that says, if it hurts when they do something, they should probably stop doing it. In this case, if using GPLed code is getting them sued, one possible solution is to comply with the license, the other solution is to simply stop using GPLed code. Both are equally valid choices, even if one is less desirable from an OSS advocacy perspective.
The onus is on the OSS community to clearly articulate the value provided by compliance that exceeds the value achieved by going back to a mix of proprietary and BSD licensed code.
(Reply to this) (Thread)