Feature

Plone Foundation Approves Relicensing Policy

Dee-Ann LeBlanc avatar
By
SAVED

Plone Foundation Approves Relicensing Policy

As we've mentioned previously, the Plone (news, site) community has been in discussions over a slight change to licensing policy. No, Plone is not changing licenses. It's sticking with the GPL.

However, Plone is now also offering the option for those building Plone Framework Components to apply for permission to use a modified BSD license for their components instead of the GPL.

This move is primarily meant to make it easier for componentized Plone code to interact with Zope and Python projects without causing GPL violations. Requests will be considered on a case-by-case basis for components that:

  • Are in the plone.* namespace, not the plone.app.* namespace.
  • Don't have imports from GPL-licensed code.

The primary developer/maintainer must be willing to ensure the component won't acquire dependencies on GPL-licensed code.

For the official description of the new policy and associated FAQs, see the Plone Framework Components Relicensing Policy document.

About the Author
Dee-Ann LeBlanc

Dee-Ann is the Open Source and Open Standards Contributing editor for CMSWire. She's spent the last sixteen years writing on Linux, open source, open standards, and more. Connect with Dee-Ann LeBlanc:

Featured Research