Announce: Reusable Zope Public License 2.1
We have updated the Zope Public License (ZPL) to revision 2.1. ZPL 2.1 is reusable. It supports having a consistent license for Zope and third-party products without requiring 3rd-party developers to assign copyright to Zope Corporation. It is important that add-on products for Zope be released under the ZPL. Why? Two reasons: * The ZPL is a flexible license that supports both commercial and non-commercial use of the software. * If Zope add-on products are released under the ZPL, then users of Zope and the add-on products only have one license to worry about. Keeping track of many different licenses is a burden to users. For more information, see: http://www.zope.org/Resources/License Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
It is important that add-on products for Zope be released under the ZPL.
What is the reason for not using the verbatim 3-clause BSD license? The 4th clause in ZPL 2.1 is redundant, IANAL, though. The 5th is confusing. What's the situation with *BSD like ports where the source code is patched right before compiling? What is the "date of change" in that case? Or, if I use a file from Zope in my own product, do I have to include the change notice in it? If I use only the half of the code? Or just a few lines? I like the BSD license because it's simple, I don't have to think about the details, just keep the copyright notes and everything will be fine. Regards, Sandor
zope@netchan.cotse.net wrote:
The 5th is confusing. What's the situation with *BSD like ports where the source code is patched right before compiling? What is the "date of change" in that case?
In that case the ZPL'd program isn't being redistributed modified, so the 5th clause doesn't apply.
participants (3)
-
Jamie Heilman -
Jim Fulton -
zope＠netchan.cotse.net