Pulp Licensing FAQ » History » Sprint/Milestone 1
bmbouter, 02/04/2019 10:49 PM
An initial buildout of FAQ info
1 | 1 | bmbouter | # Pulp3 Licensing FAQ |
---|---|---|---|
2 | |||
3 | ### Why would Pulp3 Plugins be affected by the license of the pulpcore-plugin package? |
||
4 | |||
5 | The GPL FAQ states that subclassing as a mechansism is creating a derivative work. https://www.gnu.org/licenses/gpl-faq.en.html#OOPLang |
||
6 | |||
7 | Coupled with the fact that theplugin API uses subclassing as a mechansism ( https://docs.pulpproject.org/en/pulpcore-plugin/nightly/plugin-writer/concepts/index.html#subclassing ) plugin code must be a GPLv2 or compatible license. |
||
8 | |||
9 | ### Why GPLv2? |
||
10 | |||
11 | Because pulpcore-plugin and pulpcore both currently use GPLv2. |
||
12 | |||
13 | https://github.com/pulp/pulp/blob/master/LICENSE |
||
14 | https://github.com/pulp/pulpcore-plugin/blob/master/LICENSE |
||
15 | |||
16 | ### Why does the pulpcore package matter? Plugin code is only imported from pulpcore-plugin, not pulpcore? |
||
17 | |||
18 | For technical reasons, many of the objects in pulpcore-plugin are imported and offered from the pulpcore asset itself. There are enough of these cases that offering pulpcore and pulpcore-plugin as separate license types is infeasible. |
||
19 | |||
20 | ### What are the GPLv2 compatible license types? |
||
21 | |||
22 | The gnu website has lots of info on this. This is a good place to start. https://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean |