What is the proper way of including a GPL licensed code in an extension

We need to use code from this repository GitHub - zsiki/Find-GCP: Find ArUco markers in digital photos for the photogrammetry extension we are building. This code is licensed under GPL2.

My understanding is historical GPL licenses are not considered compatible with Slicer’s license and community’s modus operandi.

If we provide a button for the user to clone/download the repo (like ffmpeg) at the time of execution, is that considered acceptable? If not, what would be the acceptable approach?

As long as we aren’t the ones distributing the code then there’s no problem with users installing GPL’d or similar code to use with Slicer. So yes, a button like the one for ffmpeg is a good solution.

1 Like

AFAIK, It is not always that simple.

Code that depends on GPL’d code may potentially be considered a “derivative work” (which would trigger the license incompatibilities), regardless of if the GPL’d code is distributed with it. Details of how you use that code matter, and the existence alternatives (i.e. pieces of code that could replace the GPL’d module) may matter.

I am not a lawyer, and the only safe advice is to consult one.