<div dir="ltr"><div>Dear Mccoy,</div><div>Attached below is the response I received from another lawyer. I'm going to ask some more lawyers if the license could be used to construe allowing fraud to occur in their name (or more generally fraud) at all. The attached message gives me the impression it could be a concern. Since the point of this license is to minimize lawsuits, I'm certainly not against throwing out the "No fraud" provision if it is really unnecessary. Assuming I throw out that provision, you mentioned the license is poorly executed. Can you tell me what other points I should consider for improvement?<br></div><div><br></div><div>Attached Message:<br></div><div>
If you intend a person to waive all IP rights forever, I am not sure why
you are trying to identify a work or derivatives in your draft. And
copyleft does not make sense unless it is bound to a single work.
<div><br>
</div>
<div>An unlimited capture grant would have a lot of problems, such as:</div>
<div><br>
</div>
<div>--The person would never be able to get a job again, as most
employers require assignments of rights, which would be impossible in
light of this license.</div>
<div>--The person could never run a business due to granting away all trademarks.</div>
<div>--It would probably be unenforceable in some jurisdictions because of its breadth.</div>
<div>--It would probably eventually be unenforceable in the US due to termination of transfers rules.</div>
<div>--It will have unintended consequences. What if in the future due
to changes in law a person gets an IP right in the person's own DNA,
facial features, fingerprints, etc.? </div>
<div><br>
</div>
<div>These are just some examples. I honestly do not think this approach is a good idea.</div>
<div><br>
</div>
<div>Waiver and licenses are the same thing, basically.</div>
<div><br>
</div>
<div>"M<font face="wf_segoe-ui_normal, Segoe UI, Segoe WP, Tahoma, Arial, sans-serif, serif, EmojiFont" color="#212121"><span style="font-size:15px">aximize IP rights by having the contributors agree to grant the public all their IP rights." just doesn't
make sense to an IP lawyer. That is minimizing IP rights.</span></font></div>
</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 16, 2020 at 1:29 PM <<a href="mailto:license-review-request@lists.opensource.org" target="_blank">license-review-request@lists.opensource.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send License-review mailing list submissions to<br>
<a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:license-review-request@lists.opensource.org" target="_blank">license-review-request@lists.opensource.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:license-review-owner@lists.opensource.org" target="_blank">license-review-owner@lists.opensource.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of License-review digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: License-review Digest, Vol 95, Issue 7 (McCoy Smith)<br>
2. Re: License-review Digest, Vol 95, Issue 8 (Alex Williams)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 16 Oct 2020 11:20:56 -0700<br>
From: "McCoy Smith" <mccoy@lexpan.law><br>
To: "'License submissions for OSI review'"<br>
<<a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a>><br>
Subject: Re: [License-review] License-review Digest, Vol 95, Issue 7<br>
Message-ID: <0af201d6a3e9$17ca4e10$475eea30$@lexpan.law><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
<br>
From: License-review <<a href="mailto:license-review-bounces@lists.opensource.org" target="_blank">license-review-bounces@lists.opensource.org</a>> On Behalf Of Alex Williams<br>
Sent: Friday, October 16, 2020 8:26 AM<br>
To: <a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
Subject: Re: [License-review] License-review Digest, Vol 95, Issue 7<br>
<br>
<br>
<br>
Would this intention be permissible within OSIs definition of open source? If so, do you believe I should add clarifying language such as:<br>
Fraudulent use does not terminate your license. However, no legal remedies for IP infringement are waived for fraudulent use.<br>
<br>
<br>
<br>
Given there exist already plenty of legal remedies (both civil, and criminal) for fraud, which for the most part are more punitive than those for IP infringement, I?d suggest maybe this is not something you want to keep in your license (particularly since it does raise issues with OSD conformance). It?s a bit like saying ?if you use this software for murder, I?ll sue you for copyright infringement!?<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/7c061599/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/7c061599/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 16 Oct 2020 13:28:00 -0500<br>
From: Alex Williams <<a href="mailto:implementnap@gmail.com" target="_blank">implementnap@gmail.com</a>><br>
To: <a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
Subject: Re: [License-review] License-review Digest, Vol 95, Issue 8<br>
Message-ID:<br>
<CA+ujgfNb16C392SE66eQZON=<a href="mailto:hdJhmM55_EQeTZta1Kxyyr1G-g@mail.gmail.com" target="_blank">hdJhmM55_EQeTZta1Kxyyr1G-g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Mccoy,<br>
I almost didn't see your message. Fortunately, the message archives made<br>
the message chain a little more clear.<br>
<br>
In reference to your comment about "source code", he license mentions<br>
"included work", which is meant to mean any copyrightable work including<br>
source code. Should I add a clarifying phrase such as work includes all<br>
copyrightable work including (but not limited to) software, etc?<br>
<br>
I ran this by various lawyers, but only one of them gave constructive<br>
feedback beyond this license is a "bad idea" or it's "pointless". Their<br>
feedback helped me clean it up a bit. What type of sign-off should I aim<br>
for from legal assistance to say this license is ready for OSI review?<br>
<br>
Here are some of the relevant public threads I've discussed this license so<br>
far:<br>
<a href="https://www.reddit.com/r/opensource/comments/j88b7j/antiip_license/" rel="noreferrer" target="_blank">https://www.reddit.com/r/opensource/comments/j88b7j/antiip_license/</a><br>
<a href="https://www.reddit.com/r/copyrightlaw/comments/j88d24/antiip_license/" rel="noreferrer" target="_blank">https://www.reddit.com/r/copyrightlaw/comments/j88d24/antiip_license/</a><br>
<br>
-Alex<br>
<br>
On Fri, Oct 16, 2020 at 10:27 AM <<br>
<a href="mailto:license-review-request@lists.opensource.org" target="_blank">license-review-request@lists.opensource.org</a>> wrote:<br>
<br>
> Send License-review mailing list submissions to<br>
> <a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:license-review-request@lists.opensource.org" target="_blank">license-review-request@lists.opensource.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:license-review-owner@lists.opensource.org" target="_blank">license-review-owner@lists.opensource.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of License-review digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: License-review Digest, Vol 95, Issue 7 (Alex Williams)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Fri, 16 Oct 2020 10:26:27 -0500<br>
> From: Alex Williams <<a href="mailto:implementnap@gmail.com" target="_blank">implementnap@gmail.com</a>><br>
> To: <a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
> Subject: Re: [License-review] License-review Digest, Vol 95, Issue 7<br>
> Message-ID:<br>
> <<br>
> <a href="mailto:CA%2BujgfM1ezJhS_95FcFW4tw5FBPyWriBHzba1vx_RLSFf_Fdpg@mail.gmail.com" target="_blank">CA+ujgfM1ezJhS_95FcFW4tw5FBPyWriBHzba1vx_RLSFf_Fdpg@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> Dear Kevin,<br>
> I wasn't clear with my wording. I believe the license is complete subject<br>
> to feedback I receive about how to improve its wording or to address any<br>
> issues that it might have.<br>
> I'm happy to move this to license discussion if you or any of the reviewers<br>
> believe that is appropriate. Should I do that now, or should I wait for<br>
> further questioning on this thread to get a better assessment of which list<br>
> the license is best in its current state?<br>
><br>
> I also should state that I'm not a lawyer. The intention with this<br>
> modification would be that if fraud is committed the license would stay<br>
> fully intact... but the owner's reserve the right to sue for IP<br>
> infringement for the limited area of areas associated with the fraud.<br>
><br>
> For example, identity theft defrauds a bank rather than the owner of the<br>
> identity. Some people argue identity is a form of IP. So, in this case<br>
> the "No fraud" clause would clarify that the owners are not waiving their<br>
> right to recourse in damages caused by identity theft.<br>
><br>
> Would this intention be permissible within OSIs definition of open source?<br>
> If so, do you believe I should add clarifying language such as:<br>
> Fraudulent use does not terminate your license. However, no legal remedies<br>
> for IP infringement are waived for fraudulent use.<br>
><br>
> -Alex<br>
><br>
> On Fri, Oct 16, 2020 at 10:00 AM <<br>
> <a href="mailto:license-review-request@lists.opensource.org" target="_blank">license-review-request@lists.opensource.org</a>> wrote:<br>
><br>
> > Send License-review mailing list submissions to<br>
> > <a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
> ><br>
> > To subscribe or unsubscribe via the World Wide Web, visit<br>
> ><br>
> ><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
> ><br>
> > or, via email, send a message with subject or body 'help' to<br>
> > <a href="mailto:license-review-request@lists.opensource.org" target="_blank">license-review-request@lists.opensource.org</a><br>
> ><br>
> > You can reach the person managing the list at<br>
> > <a href="mailto:license-review-owner@lists.opensource.org" target="_blank">license-review-owner@lists.opensource.org</a><br>
> ><br>
> > When replying, please edit your Subject line so it is more specific<br>
> > than "Re: Contents of License-review digest..."<br>
> ><br>
> ><br>
> > Today's Topics:<br>
> ><br>
> > 1. Re: Anti-IP License (McCoy Smith)<br>
> > 2. Re: license review request (Simon Phipps)<br>
> > 3. Re: License-review Digest, Vol 95, Issue 6 (Alex Williams)<br>
> > 4. Re: License-review Digest, Vol 95, Issue 6 (Kevin P. Fleming)<br>
> ><br>
> ><br>
> > ----------------------------------------------------------------------<br>
> ><br>
> > Message: 1<br>
> > Date: Fri, 16 Oct 2020 07:04:13 -0700<br>
> > From: "McCoy Smith" <mccoy@lexpan.law><br>
> > To: "'License submissions for OSI review'"<br>
> > <<a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a>><br>
> > Subject: Re: [License-review] Anti-IP License<br>
> > Message-ID: <064601d6a3c5$3a973080$afc59180$@lexpan.law><br>
> > Content-Type: text/plain; charset="us-ascii"<br>
> ><br>
> > This is an interesting concept, but poorly executed. Kevin points out one<br>
> > problem. Another is that it doesn't anywhere discuss source code (which<br>
> > would seem to violate OSD 2).<br>
> > I'd say this is one that really needs a lawyer's involvement, to ensure<br>
> its<br>
> > terms meet the goals of the author and also satisfy the OSD.<br>
> > FWIW, I'm not sure how this would be found "unconscionable" at least<br>
> under<br>
> > USA law; it appears to be something like an attempt to do a copyleft<br>
> public<br>
> > domain dedication, which AFAIK, isn't unconscionable.<br>
> ><br>
> > > -----Original Message-----<br>
> > > From: License-review <<a href="mailto:license-review-bounces@lists.opensource.org" target="_blank">license-review-bounces@lists.opensource.org</a>> On<br>
> > > Behalf Of Kevin P. Fleming<br>
> > > Sent: Friday, October 16, 2020 6:29 AM<br>
> > > To: License submissions for OSI review<br>
> > <<a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a>><br>
> > > Subject: Re: [License-review] Anti-IP License<br>
> > ><br>
> > > On Fri, Oct 16, 2020 at 8:18 AM Alex Williams <<a href="mailto:implementnap@gmail.com" target="_blank">implementnap@gmail.com</a>><br>
> > > wrote:<br>
> > ><br>
> > > > No Fraud<br>
> > > ><br>
> > > > No Licensable IP or Restricted work may be used to commit fraud. If<br>
> you<br>
> > are<br>
> > > found guilty of committing fraud using any of the Licensable IP or a<br>
> > Restricted<br>
> > > work in a court of law, then your license ends immediately.<br>
> > ><br>
> > > This is a restriction on use, and thus generally considered to be<br>
> > incompatible<br>
> > > with the OSD. If this was to have any chance at approval at all, the<br>
> > license<br>
> > > termination would need to apply to only the limited usage of the<br>
> covered<br>
> > > works which were involved in the fraudulent activity. If the licensee<br>
> > also<br>
> > uses<br>
> > > the covered works in other activities, which have not been determined<br>
> to<br>
> > be<br>
> > > fraudulent, then those licenses would have to stay in force. My opinion<br>
> > of<br>
> > > course, IANAL, yadda yadda.<br>
> > ><br>
> > > _______________________________________________<br>
> > > The opinions expressed in this email are those of the sender and not<br>
> > necessarily<br>
> > > those of the Open Source Initiative. Communication from the Open Source<br>
> > > Initiative will be sent from an <a href="http://opensource.org" rel="noreferrer" target="_blank">opensource.org</a> email address.<br>
> > ><br>
> > > License-review mailing list<br>
> > > <a href="mailto:License-review@lists.opensource.org" target="_blank">License-review@lists.opensource.org</a><br>
> > > <a href="http://lists.opensource.org/mailman/listinfo/license-" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-</a><br>
> > > <a href="http://review_lists.opensource.org" rel="noreferrer" target="_blank">review_lists.opensource.org</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > Message: 2<br>
> > Date: Fri, 16 Oct 2020 15:08:09 +0100<br>
> > From: Simon Phipps <<a href="mailto:simon@webmink.com" target="_blank">simon@webmink.com</a>><br>
> > To: mccoy@lexpan.law, License submissions for OSI review<br>
> > <<a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a>><br>
> > Subject: Re: [License-review] license review request<br>
> > Message-ID:<br>
> > <<br>
> > <a href="mailto:CAA4ffp_gmiN81MbjknO-jp54%2Bs7yiJ2o55cwXW%2BQCjQKPyOFhg@mail.gmail.com" target="_blank">CAA4ffp_gmiN81MbjknO-jp54+s7yiJ2o55cwXW+QCjQKPyOFhg@mail.gmail.com</a>><br>
> > Content-Type: text/plain; charset="utf-8"<br>
> ><br>
> > I agree. This is a submission that would have been better caught in<br>
> > moderation and rejected with an explanation of the misunderstanding.<br>
> ><br>
> > S.<br>
> ><br>
> > On Fri, Oct 16, 2020 at 2:53 PM McCoy Smith <mccoy@lexpan.law> wrote:<br>
> ><br>
> > > This appears to be nothing more than 2-clause BSD:<br>
> > > <a href="https://opensource.org/licenses/BSD-2-Clause" rel="noreferrer" target="_blank">https://opensource.org/licenses/BSD-2-Clause</a><br>
> > ><br>
> > ><br>
> > ><br>
> > > It?s not clear why you are looking for approval for an already-approved<br>
> > > license.<br>
> > ><br>
> > ><br>
> > ><br>
> > > [Also, you didn?t seem to provide the information required for a<br>
> license<br>
> > > submission: <a href="https://opensource.org/approval" rel="noreferrer" target="_blank">https://opensource.org/approval</a>, in particular, whether<br>
> this<br>
> > > received legal review and distinguishing it from OSI approved licenses,<br>
> > > particularly BSD 2-clause]<br>
> > ><br>
> > ><br>
> > ><br>
> > > *From:* License-review <<a href="mailto:license-review-bounces@lists.opensource.org" target="_blank">license-review-bounces@lists.opensource.org</a>><br>
> *On<br>
> > > Behalf Of *Seung-Eon Roh<br>
> > > *Sent:* Friday, October 9, 2020 1:16 PM<br>
> > > *To:* <a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
> > > *Subject:* [License-review] license review request<br>
> > ><br>
> > ><br>
> > ><br>
> > > Dear,<br>
> > ><br>
> > ><br>
> > ><br>
> > > I?m writing to request an approval of open source license for a matlab<br>
> > > code for neuroscience data analysis.<br>
> > ><br>
> > ><br>
> > ><br>
> > > *Submission type*: Approval<br>
> > ><br>
> > ><br>
> > ><br>
> > > *License name*: Calcium signal processing for neuroscience<br>
> > ><br>
> > ><br>
> > ><br>
> > > *License*:<br>
> > ><br>
> > > Copyright (c) 2020, Seung-Eon Roh<br>
> > ><br>
> > > All rights reserved.<br>
> > ><br>
> > ><br>
> > ><br>
> > > Redistribution and use in source and binary forms, with or without<br>
> > > modification, are permitted provided that the following conditions are<br>
> > met:<br>
> > ><br>
> > ><br>
> > ><br>
> > > * Redistributions of source code must retain the above copyright<br>
> > ><br>
> > > notice, this list of conditions and the following disclaimer.<br>
> > ><br>
> > > * Redistributions in binary form must reproduce the above copyright<br>
> > ><br>
> > > notice, this list of conditions and the following disclaimer in<br>
> > ><br>
> > > the documentation and/or other materials provided with the<br>
> > > distribution<br>
> > ><br>
> > ><br>
> > ><br>
> > > THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS<br>
> > > IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED<br>
> TO,<br>
> > > THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR<br>
> > > PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR<br>
> > > CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,<br>
> > > EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,<br>
> > > PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR<br>
> > PROFITS;<br>
> > > OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF<br>
> LIABILITY,<br>
> > > WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR<br>
> > > OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF<br>
> > > ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.<br>
> > ><br>
> > ><br>
> > ><br>
> > > *The link to public link for the code*:<br>
> > ><br>
> > > <a href="https://github.com/NeuRoh1/Calcium_signal_processing" rel="noreferrer" target="_blank">https://github.com/NeuRoh1/Calcium_signal_processing</a><br>
> > ><br>
> > ><br>
> > ><br>
> > > I?m enclosing a Matlab code which will be licensed for.<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > ><br>
> > > This licensing is intended to support the supplement documentation of<br>
> > > matlab code for an article publication in eLife Journal. Please let me<br>
> > know<br>
> > > if the request is in a good shape.<br>
> > ><br>
> > ><br>
> > ><br>
> > > Thanks,<br>
> > ><br>
> > ><br>
> > ><br>
> > > Seung-Eon Roh<br>
> > ><br>
> > > Post-doc researcher<br>
> > ><br>
> > > Department of Neuroscience<br>
> > ><br>
> > > Johns Hopkins University<br>
> > ><br>
> > > Baltimore, MD<br>
> > > _______________________________________________<br>
> > ><br>
> > -------------- next part --------------<br>
> > An HTML attachment was scrubbed...<br>
> > URL: <<br>
> ><br>
> <a href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/603e21d9/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/603e21d9/attachment-0001.html</a><br>
> > ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > Message: 3<br>
> > Date: Fri, 16 Oct 2020 09:47:35 -0500<br>
> > From: Alex Williams <<a href="mailto:implementnap@gmail.com" target="_blank">implementnap@gmail.com</a>><br>
> > To: <a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a><br>
> > Subject: Re: [License-review] License-review Digest, Vol 95, Issue 6<br>
> > Message-ID:<br>
> > <CA+ujgfOhjZQPEcuvsO1sbfCHzk68ZhYZt9R=<br>
> > <a href="mailto:GwrtdMRmWRv2Sw@mail.gmail.com" target="_blank">GwrtdMRmWRv2Sw@mail.gmail.com</a>><br>
> > Content-Type: text/plain; charset="utf-8"<br>
> ><br>
> > Dear Kevin:<br>
> > I thought about your comment on the fraud section. I don't think we need<br>
> > license termination for that section. What if the section merely read:<br>
> > No Licensable IP or Restricted work may be used to commit fraud<br>
> ><br>
> > Would that change address your concern regarding "No Discrimination<br>
> against<br>
> > fields of endeavor"?<br>
> ><br>
> > Also, thank you for taking the time to review the license. If we can<br>
> > perfect it and get it approved, I plan to use it in my company and<br>
> > encourage others to do so as well. Overall, I think the license has<br>
> reached<br>
> > a stable point in terms of intent. However, I suspect there are sections<br>
> > where the wording can be improved. So, I'm happy to work with any<br>
> > constructive feedback you might have. In reference to one comment, I<br>
> > received recently here is one question I have: Here are my current<br>
> > questions:<br>
> > Is there any substantial difference between:<br>
> > a) "Licensable IP" means all IP the owners of the included work can or<br>
> > will be able to license.<br>
> > b) "Licensable IP" means all IP the owners of the included work can or<br>
> > will be able to license that would otherwise infringe that owner's IP<br>
> > rights.<br>
> ><br>
> > If so, which definition is better?<br>
> ><br>
> > -Alex<br>
> > -------------- next part --------------<br>
> > An HTML attachment was scrubbed...<br>
> > URL: <<br>
> ><br>
> <a href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/60aa7659/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/60aa7659/attachment-0001.html</a><br>
> > ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > Message: 4<br>
> > Date: Fri, 16 Oct 2020 10:59:23 -0400<br>
> > From: "Kevin P. Fleming" <<a href="mailto:kevin%2Bosi@km6g.us" target="_blank">kevin+osi@km6g.us</a>><br>
> > To: License submissions for OSI review<br>
> > <<a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensource.org</a>><br>
> > Subject: Re: [License-review] License-review Digest, Vol 95, Issue 6<br>
> > Message-ID:<br>
> > <CAE+UdorG=<br>
> > <a href="mailto:FKOCFbwEQq%2BADJKoY47sFfSqRQu06Tr_-AJ-kMPcQ@mail.gmail.com" target="_blank">FKOCFbwEQq+ADJKoY47sFfSqRQu06Tr_-AJ-kMPcQ@mail.gmail.com</a>><br>
> > Content-Type: text/plain; charset="UTF-8"<br>
> ><br>
> > If you're still drafting the license, this should be moved to<br>
> > license-discuss, not on license-review. Submission for approval should<br>
> > be for a license that you consider to be complete, and that you revise<br>
> > based on feedback during the review process.<br>
> ><br>
> > Regarding the 'field of endeavor' restriction, I'm not a lawyer, but I<br>
> > don't see how your suggested change would make any difference. If you<br>
> > tell the licensee that the covered works cannot be used to commit<br>
> > fraud, then that implies that the license is<br>
> > vacated/nullified/terminated in that situation.<br>
> ><br>
> > On Fri, Oct 16, 2020 at 10:48 AM Alex Williams <<a href="mailto:implementnap@gmail.com" target="_blank">implementnap@gmail.com</a>><br>
> > wrote:<br>
> > ><br>
> > > Dear Kevin:<br>
> > > I thought about your comment on the fraud section. I don't think we<br>
> need<br>
> > license termination for that section. What if the section merely read:<br>
> > > No Licensable IP or Restricted work may be used to commit fraud<br>
> > ><br>
> > > Would that change address your concern regarding "No Discrimination<br>
> > against fields of endeavor"?<br>
> > ><br>
> > > Also, thank you for taking the time to review the license. If we can<br>
> > perfect it and get it approved, I plan to use it in my company and<br>
> > encourage others to do so as well. Overall, I think the license has<br>
> reached<br>
> > a stable point in terms of intent. However, I suspect there are sections<br>
> > where the wording can be improved. So, I'm happy to work with any<br>
> > constructive feedback you might have. In reference to one comment, I<br>
> > received recently here is one question I have: Here are my current<br>
> > questions:<br>
> > > Is there any substantial difference between:<br>
> > > a) "Licensable IP" means all IP the owners of the included work can<br>
> or<br>
> > will be able to license.<br>
> > > b) "Licensable IP" means all IP the owners of the included work can<br>
> or<br>
> > will be able to license that would otherwise infringe that owner's IP<br>
> > rights.<br>
> > ><br>
> > > If so, which definition is better?<br>
> > ><br>
> > > -Alex<br>
> > > _______________________________________________<br>
> > > The opinions expressed in this email are those of the sender and not<br>
> > necessarily those of the Open Source Initiative. Communication from the<br>
> > Open Source Initiative will be sent from an <a href="http://opensource.org" rel="noreferrer" target="_blank">opensource.org</a> email<br>
> address.<br>
> > ><br>
> > > License-review mailing list<br>
> > > <a href="mailto:License-review@lists.opensource.org" target="_blank">License-review@lists.opensource.org</a><br>
> > ><br>
> ><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
> ><br>
> ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > Subject: Digest Footer<br>
> ><br>
> > _______________________________________________<br>
> > License-review mailing list<br>
> > <a href="mailto:License-review@lists.opensource.org" target="_blank">License-review@lists.opensource.org</a><br>
> ><br>
> ><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
> ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > End of License-review Digest, Vol 95, Issue 7<br>
> > *********************************************<br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> <a href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/32717750/attachment.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/32717750/attachment.html</a><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> _______________________________________________<br>
> License-review mailing list<br>
> <a href="mailto:License-review@lists.opensource.org" target="_blank">License-review@lists.opensource.org</a><br>
><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of License-review Digest, Vol 95, Issue 8<br>
> *********************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/1c4d04ea/attachment.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20201016/1c4d04ea/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org" target="_blank">License-review@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of License-review Digest, Vol 95, Issue 10<br>
**********************************************<br>
</blockquote></div>