Pulp Licensing FAQ » History » Revision 2
Revision 1 (bmbouter, 02/04/2019 10:49 PM) → Revision 2/8 (bmbouter, 02/28/2019 04:07 PM)
# Pulp3 Licensing FAQ ### Why would Pulp3 Plugins be affected by the license of the pulpcore-plugin package? The GPL FAQ states that subclassing as a mechansism is creating a derivative work. https://www.gnu.org/licenses/gpl-faq.en.html#OOPLang 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 GPLv2 or later" compatible license. ### GPLv2 or later? Why GPLv2? The Because pulpcore-plugin and pulpcore and pulpcore-plugin packages both extend their license to users a "GPLv2 or later". currently use GPLv2. https://github.com/pulp/pulp/blob/master/COPYRIGHT#L5 https://github.com/pulp/pulp/blob/master/LICENSE https://github.com/pulp/pulpcore-plugin/blob/master/COPYRIGHT#L5 https://github.com/pulp/pulpcore-plugin/blob/master/LICENSE So a plugin can choose the license they want to use as either GPLv2 or GPLv3. ### Why does the pulpcore package matter? Plugin code is only imported from pulpcore-plugin, not pulpcore? 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. ### Can I combine What are the GPLv2 or GPLv3 licensed code with other compatible license types? It depends The gnu website has lots of info on if the other license this. This is "compatible" with GPLv2 or GPLv3. a good place to start. https://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean ### Can I combine GPLv2 or GPLv3 licensed code with Apache 2.0 licensed code? No for GPLv2, Yes for GPLv3. https://www.gnu.org/licenses/license-list.html#apache2
.