Open ajorg-aws opened 3 years ago
IANAL, but why wouldn't linking to KDE/snoreToast repo and maybe more specifically linking to https://github.com/KDE/snoretoast/releases/tag/v0.7.0 be considered as disclosing the corresponding source through the same place, and thus complying with the license?
If you can confirm that that's the correct tag for the build included in the repo, and that no modifications were made before compiling it might be sufficient. The license also requires Installation Information, such that it's important to know how it's compiled as well. If that information is also provided at that tag then that can be sufficient.
Technically the GPL requires that you, the distributor, provide the source code you used, rather than relying on the upstream to provide it, but it's unlikely anyone is going to be that nit-picky about it if you're sure you're pointing to the right source code for the build you're providing, especially if the upstream is a reputable group like KDE.
It's also supposed to be complete, so if snoreToast has dependencies outside of the KDE source tree (Qt?) we've got to be able to point to those too.
Can you provide the Corresponding Source for the builds of snoreToast included in releases of node-notifier, for compliance with the LGPL-3.0 license for that component? Providing this is needed to allow users of node-notifier to comply with that license when redistributing.