[License-review] For Approval: License Zero Reciprocal Public License
kyle at kemitchell.com
Fri Oct 20 00:27:42 UTC 2017
Revising the text of the proposed license, per feedback here
on license-review and elsewhere.
Also replying to the original message this time. If I
revise again, I'll do the same, so it's easier to find.
First the new text, then a few notes.
License Zero Reciprocal Public License <Version>
Copyright <Year> <Copyright Holder>
Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the
2. Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or
other materials provided with the distribution.
3. Uses with any modification that is not "Open Source"
as defined by the Open Source Initiative must be
limited to <Grace Period> calendar days.
4. Uses as part of, or in development of, other
software that is not "Open Source" as defined by the
Open Source Initiative must be limited to <Grace
Period> calendar days.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS 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 HOLDER OR CONTRIBUTORS 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.
- I've removed all mention of agent for sale of alternative
licenses, as well as the automatic waiver of the copyleft
conditions. My motivation was twofold. For one, those
features produced considerable comment, concern, and
confusion, aside from the main issue of use conditions
triggering copyleft. For two, the aim of each can be
achieved otherwise, outside the license text. As a result,
the proposal is now _exactly_ BSD-2-Clause, plus new
conditions 3 and 4.
- The copyleft triggers now speak directly in terms of OSD
conformance, to catch both source availability and license
terms requirements. (The assumption is that L0-R, in some
form, will eventually be recognized itself, so L0-R code
can clearly incorporate L0-R code.) But that aside, I
think the new language goes more directly to intent, and
reads more clearly.
- I've split the new conditions across two numbered items.
This should help clarify that unmodified use alone does
not trigger share-alike.
- I was tempted to define terms for repeated words and
phrases, but held the urge back. BSD-2-Clause doesn't do
so, and for this kind of license, stylistically, I think
that's probably best.
Kyle Mitchell, attorney // Oakland // (510) 712 - 0933
More information about the License-review