Open Stack

JSHint *isn't* Douglas Crockford.  It was written by someone who (understandably)
thought Douglas Crockford had some good ideas, but was overzealous.  It does mostly the
same things, but is more lenient with regards to style elements.

The license is as such: https://github.com/jshint/jshint/blob/master/LICENSE

You are thinking of JSLint, which is written by Douglas Crockford.

----- Original Message -----
> From: "Aaron Sahlin" <asahlin at linux.vnet.ibm.com>
> To: openstack-dev at lists.openstack.org
> Sent: Wednesday, September 10, 2014 11:56:37 AM
> Subject: [openstack-dev] [Horizon] Licensing issue with using JSHint in build
> 
> I noticed that the build is using JSHint now, and before I consider
> syncing it with the proposed options from the JavaScript best practices
> (https://review.openstack.org/#/c/117595/), I wanted to double check and
> be sure Horizon got past the legal problem with the good/evil licensing.
> 
> Some background for those who are not aware.   JSHint was authored by
> Doug Crockford, and he added an extra line in the licensing, "The
> software shall be used for good, not evil".  The issue is in the
> definition of what is good and what is evil.   It is too subjective,
> what is evil differs from person to person therefore ends up being a
> liability and leaving users open to frivolous lawsuits.
> 
> Did Horizon get permission or find some way around the licensing issue?
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>