The Foundation feels that it benefits the community for a single organization to hold the rights to Plone. Prior to the Foundation, the intellectual property of Plone has been jointly held by individual developers and by Alan Runyan and Alexander Limi. While this has worked so far, the community members who formed the Foundation felt that having the Foundation hold these rights provides several benefits:

Minimizing confusion / maximizing business compatibility

Organizations considering adopting Plone have a simple answer for "Who owns this?", rather than a more complicated answer that might scare away the legally-cautious.

Trademark protection

By having the Foundation hold the trademarks and rights to the Plone branding assets, it can effectively protect these from unfair use.

Guarantee of future Open Source versions

The Foundation's contributor agreement will ensure that there will always be an OSI-approved version of Plone.

Support revenue for Foundation

In the future, the Foundation may be able to offer a non-GPL version of Plone in exchange for a license fee. That revenue could be used to support the Plone community, funding marketing and development.

A draft contributor agreement was shown to major contributors in mid-May. Several questions and suggestions were offered, and the agreement is currently being worked on to reflect these concerns. We will make an announcement when the next draft is ready for publication.

Questions & Answers

What license will Plone be issued under after this process?

The exact license has not yet been decided by this Foundation process, but the Foundation has stated that it will be an OSI-compliant ("Open Source") license.

Will Plone always be available under an OSI-approved/Open Source license? Couldn't the Board change its mind about this?

Plone will always be available under an OSI-approved license. The Foundation will work to ensure that the final contributor agreement makes this explicit and, if possible, makes that binding.

Will Plone be available under a non-GPL license?

The current Plone approach states that companies can negotiate a non-GPL license. Thus, the Foundation might pursue a dual-licensing (GPL and non-GPL) scheme - but, at this time, the Board has not yet created any policies on this. This is an important question for the community, of course, and the Foundation intends to have this conversation in a transparent way.

Why would anyone want a non-GPL Plone?

Two possible reasons: Some companies are reluctant to do in-house modifications of framework-like systems (such as Plone) that are under the GPL, fearing that a clause in the GPL might force them to disclose their internal work - thus wanting to license it under (for example) a BSD-style license. Second, companies may wish to offer a commercial version of Plone, under a conventional shrink-wrap license, without the obligation to reveal source code or share changes.

How much would a non-GPL version of Plone cost? Would a small company be able to afford one?

Neither the Foundation nor the Board have made any decisions about a non-GPL version, let alone about pricing. However, one of the Foundation's stated goals is to maintain a level playing field for Plone while trying to benefit all of the Plone commons.

If a non-GPL version was available, and a large company bought it, added features to it, and sold it, wouldn't they be using our work without an obligation to give back?

It's helpful to remember the core value open source provides: distributed development, maintenance, security checking, and support. Companies that build large features for Plone are already having to make decisions of whether to release their products under an open source license or not (since they could always release them as a Product, not as a modification to the Plone core). Despite this, though, many large and excellent contributions - such as Archetypes - have been made, and the Foundation hopes that companies will continue to do so. In any event, a company that purchases a non-GPL license (should such ever become available) is contributing financial resources to our community, which can be used to further develop, market, and protect the GPL version of Plone.

Has any corporate sponsor made the availability of a non-GPL version a condition for contributing?

No. The Foundation was formed to protect and promote Plone. Non-GPL versions are one benefit it could bring to Plone, but not a condition for formation or funding of the Foundation.

Why is this coming up now?

Dual-licensing offers have been a reality in Plone for at least six months; under the existing contributor agreement, contributors have explicitly given Alan Runyan and Alexander Limi this right. The only difference in the Foundation offering a dual-licensed version is that the Foundation will be able to use the funds for common good, without any question of personal gain.

What will the contributor agreement cover?

This agreement will be for the core Plone product only. Contributions to the Collective will continue to be available under whatever the project developers wish to use.

What rights will I continue to have for my contributions?

Contributors will be asked to transfer their intellectual property rights to the Foundation. In return, they will be given back irrevocable rights to use and distribute their contributions. They can even give their contributions to other Open Source projects (as long as its compatible with the license Plone itself is issued under) or use them in non-Open Source commercial applications (if that is compatible with the license Plone is under). Questions about the rights contributors retain is also critical, and still open. The Foundation will continue to discuss these questions with contributors to ensure that all views are heard.

Can I grant the Plone foundation a non-exclusive license to my contributions rather than an exclusive license, so that I can contribute the same code to other projects under different terms or use the contribution for other commercial endeavors?

Not according to the first draft of the contributor agreement. This is being considered for the new version of the agreement.

Can Open Source code from other projects be added to the Plone core (such as GPL JavaScript libraries)?

Under the first draft of the contributors agreement, it would appear that this would not be allowed, unless the authors of that code would enter into the contributors agreement. This is an ongoing concern, and one that will be addressed in later drafts of the contributors agreement.

Will the Foundation control use of the Plone trademark?

Yes. In order to keep the trademark, the Foundation (or any trademark owner) must demonstrate that they have acted to protect it. So there will be some sort of application process to use any Plone trademarks. It is expected, however, that the Foundation will honor its goal to be a level playing field and be both generous and open in this. To give a simple example, starting a site called plonerules.com should be very simple to get the permission for, but attempts to pass a site off as the Plone site will be stopped.

In addition, the general Plone Licensing FAQ answers many other questions about using and modifying Plone.