License clarification (GPL vs LGPL)

[JV-Bio]

Hi,

I'm interested in using this library but noticed what appears to be conflicting licensing information.

The NuGet packages currently indicate the following licenses:

• NAPS2.Sdk (LGPL)
• NAPS2.Internals (LGPL)
• NAPS2.Images.Wpf (LGPL)
• NAPS2.Sdk.Worker.Win32 (LGPL)
• NAPS2.Escl.Server (LGPL)
• NAPS2.NTwain (MIT)
• NAPS2.WIA (MIT)

However, when following the Project URL from the NuGet packages to the main GitHub repository, both the LICENSE file and README state:

"NAPS2 is licensed under the GNU GPL 2.0 (or later). Some projects have additional license options..."

Could you clarify which license applies to the NuGet packages listed above?

Specifically, should these packages be considered LGPL/MIT as indicated on NuGet, or does the GPL license of the repository apply to them as well, with the LGPL/MIT licenses being additional licensing options for certain projects?

I would appreciate any guidance, as licensing requirements are an important consideration for our intended use.

In advance, thank you for your time and for maintaining the project.

Best regards,
Jesper Vestergård

[cyanfish]

The nuget licenses are the alternative licenses listed in the readme. You could choose to use them under GPL if you like but I've listed the packages as just LGPL since that's more relevant for library users.

NAPS2.NTwain/NAPS2.WIA are separate repos with their own MIT licenses.

[JV-Bio]

Thank you for your quick reply.

Does that mean when using the libraries like:

• NAPS2.Sdk
• NAPS2.Internals
• NAPS2.Images.Wpf
• NAPS2.Sdk.Worker.Win32
• NAPS2.Escl.Server
• NAPS2.NTwain
• NAPS2.WIA

they will be licensed only under the LGPL or MIT?

[cyanfish]

The LGPL projects are dual-licensed. This is for convenience of being able to give a single license for all NAPS2, but there's no particular reason for users to prefer GPL for the SDK over LGPL (since LGPL, as well as MIT, are GPL-compatible and allow relicensing).

Perhaps the confusion is this: a license gives you the rights to use the project under those terms. When there are multiple license options, you get to choose which of those you want to use, and can ignore the others.

[JV-Bio]

Thank you for the explanation.
My confusion came from not realizing that, in a dual-licensed project, I can simply choose which of the available licenses to use.

I had assumed there was a preferred license among the options.

I appreciate you taking the time to explain how NAPS2 uses this licensing approach.