You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was looking at the code to see how the metadata is extracted (to perhaps use it or learn from it, in my own extension based on the WD extension.
That WD extension is licensed as GPL v3. Now, I was reading about the compatibility of GPL v2 / v3 and it seems any codes can't be mixed in this situation: "According to the License compatibility matrix from GNU, if you link your GPLv2 (or later) software with an LGPLv3 library, the effective license for the product becomes GPLv3." - *.
Is there a good reason to have this strict GPL v2 situation, which outweighs the license incompatibility with other projects going forward?
The text was updated successfully, but these errors were encountered:
Hi, I was looking at the code to see how the metadata is extracted (to perhaps use it or learn from it, in my own extension based on the WD extension.
That WD extension is licensed as GPL v3. Now, I was reading about the compatibility of GPL v2 / v3 and it seems any codes can't be mixed in this situation: "According to the License compatibility matrix from GNU, if you link your GPLv2 (or later) software with an LGPLv3 library, the effective license for the product becomes GPLv3." - *.
Is there a good reason to have this strict GPL v2 situation, which outweighs the license incompatibility with other projects going forward?
The text was updated successfully, but these errors were encountered: