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

[Kyle Mitchell]

This message supplements the "Distinguish" section of my
submission of L0-R for approval, to rectify what seems now a
glaring omission:

10. L0-R shares much in common with the Reciprocal Public
    License 1.5.

    Like RPL-1.5:

    - L0-R requires release of private changes, without
      distribution in the GPL sense. RPL implements this in
      its definition of "Deployment", which includes use.

    - L0-R extends beyond modified versions and combinations
      of the licensed work to a broader set of materials.
      RPL implements this in its definition of "Required
      Components".

    - L0-R closes the SaaS/ASP loophole. RPL achieves this
      by defining "Deploy" to include "Serve", and defining
      both terms broadly.

    - L0-R is proposed as a possible public-license "front
      end" for businesses selling exceptions to its
      reciprocity terms. RPL's steward in fact continues to
      offer exceptions to RPL for sale online.

    - L0-R permits curing inadvertent failures to
      reciprocate within 30 days of becoming aware. Parts of
      RPL-1.5 section 12.1 have the same effect.

    Where RPL extends its trigger beyond modified versions
    and combinations in a single program for the specific
    purpose of making an effective reciprocity bargain for
    web frameworks, L0-R does so for developer tools.

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