<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    David -<br>
    <br>
    Ok, that is what I was hoping to hear.   I was concerned when I saw
    <br>
    JSHint output from the continuous build.<br>
    <br>
    Example:<br>
    <p>Build succeeded.<br>
    </p>
    <p><img src="cid:part1.05000609.02020104@linux.vnet.ibm.com" alt=""></p>
    <br>
    <br>
    <div class="moz-cite-prefix">On 9/10/2014 2:50 PM, Lyle, David
      wrote:<br>
    </div>
    <blockquote cite="mid:D03605BC.1E904%25david.lyle@hp.com"
      type="cite">
      <pre wrap="">I want to clarify this. Jshint is not a requirement. It is not in
requirements.txt or test-requirements.txt nor is it a hard system
requirement.

Jshint is treated as an optional tool that can either be installed via tox
in the jshint testenv which uses npm to pull it down, or by manual
install. This allows for a standardized method of checking JavaScript for
Horizon developers as a convenience. But there is no hard requirement that
the package be present or used. Nor is jshint required to generate
anything in the code base or the packages that distros will deliver.

I believe this is a non-issue.

David

On 9/10/14, 11:35 AM, "Aaron Sahlin" <a class="moz-txt-link-rfc2396E" href="mailto:asahlin@linux.vnet.ibm.com"><asahlin@linux.vnet.ibm.com></a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">What you are finding is the same as I found, which raised my concern.

Thanks for the pointer to <a class="moz-txt-link-abbreviated" href="mailto:legal-discuss@lists.openstack.org">legal-discuss@lists.openstack.org</a>, I will post
the question there (let the lawyers figure it out).




On 9/10/2014 12:16 PM, Solly Ross wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">----- Original Message -----
</pre>
          <blockquote type="cite">
            <pre wrap="">From: "Jeremy Stanley" <a class="moz-txt-link-rfc2396E" href="mailto:fungi@yuggoth.org"><fungi@yuggoth.org></a>
To: "OpenStack Development Mailing List (not for usage questions)"
<a class="moz-txt-link-rfc2396E" href="mailto:openstack-dev@lists.openstack.org"><openstack-dev@lists.openstack.org></a>
Sent: Wednesday, September 10, 2014 1:10:18 PM
Subject: Re: [openstack-dev] [Horizon] Licensing issue with using
JSHint in build

On 2014-09-10 13:00:29 -0400 (-0400), Solly Ross wrote:
</pre>
            <blockquote type="cite">
              <pre wrap="">JSHint *isn't* Douglas Crockford. It was written by someone who
(understandably) thought Douglas Crockford had some good ideas,
but was overzealous.
</pre>
            </blockquote>
            <pre wrap="">[...]

Overzealous enough to copy his code.
</pre>
          </blockquote>
          <pre wrap="">?? This sentence doesn't make much sense.  I meant to say that
Douglas Crockford was overzealous (which he is, IMO).

</pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">The license is as such:
<a class="moz-txt-link-freetext" href="https://github.com/jshint/jshint/blob/master/LICENSE">https://github.com/jshint/jshint/blob/master/LICENSE</a>
</pre>
            </blockquote>
            <pre wrap="">Ahem. <a class="moz-txt-link-freetext" href="https://github.com/jshint/jshint/blob/master/src/jshint.js#L19">https://github.com/jshint/jshint/blob/master/src/jshint.js#L19</a>
</pre>
          </blockquote>
          <pre wrap="">Fair enough.  I stand corrected.  I didn't catch that.
The general license, however, is as stated.

</pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">You are thinking of JSLint, which is written by Douglas Crockford.
</pre>
            </blockquote>
            <pre wrap="">JSHint is a derivative project of JSLint. Sorry to burst your
bubble.
</pre>
          </blockquote>
          <pre wrap="">To be fair, it's been undergoing *major* revisions lately, making it
resemble
JSHint less and less in terms of what it checks for.  Having used it in
the
past, functionality wise it's very different.  While it maintains some
backwards
compatibility, it has added in new checks, doesn't complain about
nearly the number
of things that JSLint complains about (for good reasons).

</pre>
          <blockquote type="cite">
            <pre wrap="">--
Jeremy Stanley

_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>

</pre>
          </blockquote>
          <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>

</pre>
        </blockquote>
        <pre wrap="">


_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
      </blockquote>
      <pre wrap="">

_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>

</pre>
    </blockquote>
    <br>
  </body>
</html>