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

[Bruce Perens]

Kyle,

It seems to me that you got the more than 30 days discussion that you were
entitled to. IMO you started with an attempt to transcend the Open Source
model (although that was not immediately obvious to me) and you pushed as
hard as you could, and you failed. Whatever injury you accumulated in doing
so was a reasonable cost of the attempt and IMO not OSI's problem.

Note that I contribute my effort to this committee pro bono, and the other
folks here who are admitted to the bar do similarly while their time is
worth much more than mine, and you got copious use of all of our time. So,
I think we're even.

For the record, I recommend that the license not be approved.

Why don't you try it with a user community? Maybe someone will like it.

    Thanks

    Bruce


On Wed, Nov 8, 2017 at 11:10 PM, Kyle Mitchell <kyle at kemitchell.com> wrote:

> On 2017-11-08 18:11, Simon Phipps wrote:
> > > I asked the questions in hopes of hearing OSI's answers.
> > > Others, leaning both ways, have agreed they aren't cut and
> > > dry.  Perhaps the committee will come back, and constrain me
> > > to just the kind of license you have in mind.
> >
> > That's not how OSI or the license review process works. OSI waits for
> this
> > public forum to reach a stable consensus, then evaluates it against
> mission
> > and principle, then crystalises the community opinion if they match. OSI
> > will not offer opinions on licenses either here or privately, and this
> > forum is the "committee".
>
> Thanks so much, Simon.  I know I accidentally rankled you a
> while back.  But please know I'm sincerely grateful for your
> pointers on process.  It takes time, I know.
>
> For what it's worth, my confusion here traces back to
> https://opensource.org/approval once more:
>
>   What Will Happen
>
>   1. The License Review community will discuss on the
>      mailing list for at least 30 days.  The submitter
>      should participate in this discussion by replying to
>      any questions asked or claims made about the license.
>
>   2. The License Review Chair will summarize and present
>      recommendations to OSI Board (and copy the list).
>
>   3. The OSI Board will make the final decision, or requests
>      for additional information, at the next monthly
>      meeting.
>
>   4. The License Review Chair will report back to the List.
>
>   5. If Approved, the OSI Website will be updated as
>      appropriate.
>
> The website names Luis License Review Chair, but I
> understand he no longer holds the post.  I gathered that
> Richard does, somewhere along the way.  I can't recall
> offhand how.  And I took his recent e-mail laying out
> questions for the board as preparation for the report
> mentioned above.
>
> I so wish that my first e-mail to license-discuss had been a
> request for an overview of the process, soup to nuts.
> Instead, I did what looked for all the world like my
> homework, and followed its instructions.  I can't help
> feeling that's hurt more than helped me.
>
> I have no desire to lay blame anywhere, on anyone.  But
> someone should please update /approval, before it takes
> another victim.  If only to replace it with instructions to
> inquire on this list.
>
> Best,
>
> K
>
> --
> Kyle Mitchell, attorney // Oakland // (510) 712 - 0933
> _______________________________________________
> License-review mailing list
> License-review at opensource.org
> https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20171109/e327d4b8/attachment.html>