3 ms·

For [L]GPLv2 it's super simple - release any changed code and anything that links closely to it. If you publish all your source you basically can't fail to do t

For [L]GPLv2 it's super simple - release any changed code and anything that links closely to it. If you publish all your source you basically can't fail to do this right. For GPLv3, it's that simple most of the time. You talk about embedded which suggests you may be thinking primarily of the "tivoization" clauses designed to prevent user lockout. Again, if you're a fully open source project this will be hard to fail because the user should be able to just copy whatever you do in development. It's when you try to prevent user updates while allowing your own that this applies.

hospitalJail 4y ago
That was basically my thought, I'm just worried that if I link to the code online, that someone could claim 'Well I don't have internet'. Bam lawsuit.
- h2odragon 4y ago
  I suspect that publishing it public to the internet is sufficient. If you really wanna cover your ass offer to mail someone the source on a CD for "reasonable handling fees"... which can reasonably be fairly high if someone demands such service.
  - zerocrates 4y ago
    This was changed in GPLv3. To my reading, section 6(b)(2) means that if you're distributing a physical product, you can just include a link to a URL where the source can be downloaded for free. You could read 6(b) to mean that you have to offer consumers the choice between physical-delivery-at-cost and for-free-download of the source... but I don't think that's the right reading.
- pabs3 4y ago
  Maybe offer the source code at the point of purchase? Could even sell USB/SD with source code on it. Folks who want the code offline can buy them and copy the code where they want it. OTOH, the internet is a "medium customarily used for software interchange" so maybe that would be fine, but the internet wouldn't "accompany" the device. Also, in GPLv2 you are allowed to just send a note "you can get source from us delivered on a storage device for $X", so if you do the purchase thing, plus write a note with every device about how to get the code on the internet or on disk, you should be fine.

hospitalJail 4y ago

That was basically my thought, I'm just worried that if I link to the code online, that someone could claim 'Well I don't have internet'. Bam lawsuit.

h2odragon 4y ago
I suspect that publishing it public to the internet is sufficient. If you really wanna cover your ass offer to mail someone the source on a CD for "reasonable handling fees"... which can reasonably be fairly high if someone demands such service.
- zerocrates 4y ago
  This was changed in GPLv3. To my reading, section 6(b)(2) means that if you're distributing a physical product, you can just include a link to a URL where the source can be downloaded for free. You could read 6(b) to mean that you have to offer consumers the choice between physical-delivery-at-cost and for-free-download of the source... but I don't think that's the right reading.
pabs3 4y ago
Maybe offer the source code at the point of purchase? Could even sell USB/SD with source code on it. Folks who want the code offline can buy them and copy the code where they want it. OTOH, the internet is a "medium customarily used for software interchange" so maybe that would be fine, but the internet wouldn't "accompany" the device. Also, in GPLv2 you are allowed to just send a note "you can get source from us delivered on a storage device for $X", so if you do the purchase thing, plus write a note with every device about how to get the code on the internet or on disk, you should be fine.