[License-review] For Approval: License Zero Reciprocal Public License

[Kyle Mitchell]

On 2017-10-24 15:10, Josh berkus wrote:
> So, one more question on that thread: can you explain what the first
> project you have in mind for this license is?  I ask that for two
> reasons, (1) it enables us to better picture how the license would be
> used, and (2) this committee doesn't want to approve a license with no
> confirmed users.

L0-R was written for use as one of two alternative public
licenses for users of licensezero.com, an online system for
selling exceptions to public licenses.  If you'd like, I can
poll those who expressed original interest in a copyleft
usable with License Zero, and see what work they had in
mind.  Knowing who I know, I'd suspect primarily npm
packages to start.  As for me, I would very likely apply
L0-R to the server software for License Zero itself, and to
separate license audit tools, going forward.

Of course, the license is a bit hard to adopt at the moment,
given its state of flux.  I'd imagined that I would find
terms acceptable to OSI, start using it and promoting its
use through License Zero after that, and then approach SPDX
with that evidence of use "in the wild" to hand.  It's a
goal of the license to be OSI-approved.  That creates a
certain loop the process...

The chicken-and-egg problem is a well-known brake on
proliferation, and one that mostly works for the greater
good.  I suppose I could end up suspending this process,
cutting a final L0-R version 1.0.0, using it, and promoting
it.  But then I'd end up coming right back to license-review
for the same questions already broached.  Questions likely
to result in revisions, and therefore relicensing hassles.

Much appreciate input here.

-- 
Kyle Mitchell, attorney // Oakland // (510) 712 - 0933