<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear License Review,<br>
<br>
At the Board meeting on June 25, 2021, the Board adopted the
recommendation of the License Committee and APPROVED the Zope
Public License v.2.1 as an Open Source Initiative Certified
license in the category of Licenses That Are Redundant With More
Popular Licenses. Further, the Zope Public License Version 2.0
will be moved to the Superseded Licenses category.</p>
<p>Pamela S. Chestek<br>
Chair, License Committee<br>
Open Source Initiative<br>
<br>
</p>
On 6/22/21 12:08 PM, Pamela Chestek wrote:<br>
<blockquote type="cite"
cite="mid:2b95df1b-6f5d-4578-3a6c-d87092b458a2@opensource.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Resending, copying the OSI Board this time.<br>
<br>
Pam<br>
<br>
<div class="moz-signature">Pamela Chestek<br>
Chair, License Committee<br>
Open Source Initiative</div>
<div class="moz-cite-prefix"><br>
On 6/22/2021 12:05 PM, Pamela Chestek wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b93a5c04-3f28-c876-3657-7258e8b866be@opensource.org">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
Dear License Review,<br>
<br>
Below is the recommendation of the License Committee on the Zope
Public License.<br>
<br>
Pam<br>
<br>
Pamela Chestek<br>
Chair, License Committee<br>
Open Source Initiative<br>
<br>
License: Zope Public License (ZPL) Version 2.1, SPDX ZPL-2.1
(Exhibit A)<br>
Submitted: April 6, 2021, <a class="moz-txt-link-freetext"
href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2021-April/005124.html"
moz-do-not-send="true">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2021-April/005124.html</a>
<br>
Decision date: due no later than the first Board meeting after
June 5, 2021.<br>
<br>
License Review Committee Recommendation: <br>
<br>
<i>Resolved that it is the opinion of the OSI that the Zope
Public License (ZPL) Version 2.1 conforms to the OSD and
assures software freedom and that the license be approved as
an Open Source Initiative Certified license in the category of
Licenses That Are Redundant With More Popular Licenses.
Further, the Zope Public License Version 2.0 will be moved to
the Superseded Licenses category.</i><i><br>
</i><br>
<u>Rationale Document</u><br>
<br>
Notes: Version 2.0 of the license was OSI approved. The version
of the license under review, version 2.1, is from about 2005 and
the license submitter believes that version 2.0 has not been
used for more than 10 years. <a class="moz-txt-link-freetext"
href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2021-April/005124.html"
moz-do-not-send="true">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2021-April/005124.html</a><br>
<br>
The primary changes between version 2.0 and version 2.1 were to
(i) remove the hard-coded name of Zope Corporation from the
license and substitute “Copyright Holders” and (ii) refer to a
separate document with the copyright notice rather than an
included notice, with some additional edits for related changes
(for example, substituting “accompanying” for “above”). <br>
<br>
Version 2.0 of the license was in the “Non-reusable Licenses”
category but Version 2.1 is suitable for Licenses That Are
Redundant With More Popular Licenses, since the Zope name is no
longer within the license. The license is similar to the 3
Clause BSD license, which is the reason it is redundant.<br>
<br>
No one on License-Review objected to approving the license or to
the change of license category.<br>
<br>
The license submitter agreed that version 2 of the license could
be listed as superseded. <a class="moz-txt-link-freetext"
href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2021-April/005131.html"
moz-do-not-send="true">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2021-April/005131.html</a>
<br>
<br>
<u>Exhibit A</u><br>
<br>
Zope Public License (ZPL) Version 2.1<br>
<br>
A copyright notice accompanies this license document that
identifies the copyright holders.<br>
<br>
This license has been certified as open source. It has also been
designated as GPL compatible by the Free Software Foundation
(FSF).<br>
<br>
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:<br>
<br>
1. Redistributions in source code must retain the accompanying
copyright notice, this list of conditions, and the following
disclaimer.<br>
<br>
2. Redistributions in binary form must reproduce the
accompanying copyright notice, this list of conditions, and the
following disclaimer in the documentation and/or other materials
provided with the distribution.<br>
<br>
3. Names of the copyright holders must not be used to endorse or
promote products derived from this software without prior
written permission from the copyright holders.<br>
<br>
4. The right to distribute this software or to use it for any
purpose does not give you the right to use Servicemarks (sm) or
Trademarks (tm) of the copyright holders. Use of them is covered
by separate agreement with the copyright holders.<br>
<br>
5. If any files are modified, you must cause the modified files
to carry prominent notices stating that you changed the files
and the date of any change.<br>
<br>
Disclaimer<br>
<br>
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS'' AND
ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.On 4/6/2021 12:53 PM, Jens Vagelpohl wrote:<br>
<blockquote type="cite"
cite="mid:4586E116-2DEC-432D-8CB9-BAD105DA1FC7@netz.ooo">
<pre class="moz-quote-pre" wrap="">Hi,
My name is Jens Vagelpohl and I am release manager for the Zope web application server and many of its add-on packages maintained in the GitHub organization “zopefoundation” at <a class="moz-txt-link-freetext" href="https://github.com/zopefoundation" moz-do-not-send="true">https://github.com/zopefoundation</a>.
Almost all of our products, the oldest starting in the late 1990s, have been published under the Zope Public License, which had been certified by the OSI many years ago. The latest version on file at the OSI is version 2.0, see <a class="moz-txt-link-freetext" href="https://opensource.org/licenses/ZPL-2.0" moz-do-not-send="true">https://opensource.org/licenses/ZPL-2.0</a>, which has existed since 2001.
The ZPL version 2.0 makes references to Zope Corporation as holding copyrights to code in Zope and related packages. However, after lobbying by the Zope Foundation Zope Corporation assigned code copyrights to the foundation in te mid-2000s. The Zope Public License was rewritten to account for this copyright change and we removed all references to Zope Corporation and released as ZPL version 2.1. The earliest license copies I found in our repositories for version 2.1 are from 2005.
At this point the ZPL version 2.0 hasn’t been used for a decade. All source code had been switched to ZPL 2.1 more than 10 years ago, and Zope Corporation has been defunct for at least as long. I do not know why no foundation representative reached out to the OSI and asked for an update to the published version on the OSI website, even though I was secretary for the Zope Foundation Board of Directors at the time.
I am hereby asking for legacy approval for the Zope Public License version 2.1. I have attached a copy of the license and a copy of the copyright header we attach to all source code files in our repositories.
Thank you for your help!
Jens Vagelpohl
Release Manager, Zope
<a class="moz-txt-link-freetext" href="https://plone.org/community/zope-team" moz-do-not-send="true">https://plone.org/community/zope-team</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.
License-review mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org" moz-do-not-send="true">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" moz-do-not-send="true">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>