Shouldn't the Licenses page for Extensions state GPL is *required* for addons? #104850

Closed
opened 2024-06-27 21:00:03 +02:00 by Mahid Sheikh · 1 comment
Contributor

Page Information
File: manual/advanced/extensions/licenses.rst
Blender Version: 4.2
Documentation Language: English
Permanent Link

Short description of error
Addons utilize/link to bpy, which is under the GPL. Currently, the manual says the following:

For add-ons and themes the recommended license is GNU General Public License v2.0 or later. For assets, the required license is Public Domain (CC0).

The term recommended implies that an addon using the GPL is optional; however, because addons use bpy, and bpy is under the GPL (and not under something like the LGPL), addons are required to use the GPL, even if bpy is technically not shipped with addons. As per the GNU FAQ:

Does the GPL have different requirements for statically vs dynamically linked modules with a covered work? (#GPLStaticVsDynamic)

No. Linking a GPL covered work statically or dynamically with other modules is making a combined work based on the GPL covered work. Thus, the terms and conditions of the GNU General Public License cover the whole combination.

The manual should thus be clarified to avoid licensing issues with addons and the GPL

**Page Information** File: `manual/advanced/extensions/licenses.rst` Blender Version: `4.2` Documentation Language: `English` [Permanent Link](https://docs.blender.org/manual/en/4.2/advanced/extensions/licenses.html#extension-licenses) **Short description of error** Addons utilize/link to `bpy`, which is under the GPL. Currently, the manual says the following: > For add-ons and themes the recommended license is GNU General Public License v2.0 or later. For assets, the required license is Public Domain (CC0). The term *recommended* implies that an addon using the GPL is optional; however, because addons use `bpy`, and `bpy` is under the GPL (and not under something like the LGPL), addons are required to use the GPL, even if `bpy` is technically not shipped with addons. As per the [GNU FAQ](https://www.gnu.org/licenses/gpl-faq.en.html#GPLStaticVsDynamic): > #### Does the GPL have different requirements for statically vs dynamically linked modules with a covered work? (#GPLStaticVsDynamic) > No. Linking a GPL covered work statically or dynamically with other modules is making a combined work based on the GPL covered work. Thus, the terms and conditions of the GNU General Public License cover the whole combination. The manual should thus be clarified to avoid licensing issues with addons and the GPL
Mahid Sheikh added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2024-06-27 21:00:04 +02:00

This page states:

The Blender Extensions Platform only supports free and open source extensions compatible with Blender’s license: GNU General Public License v3.0 or later.

So the GPL isn't required, just GPL compatibility.

This page states: ``` The Blender Extensions Platform only supports free and open source extensions compatible with Blender’s license: GNU General Public License v3.0 or later. ``` So the GPL isn't required, just GPL compatibility.
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2024-07-01 10:07:16 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-manual#104850
No description provided.