"... When I put the reference implementation onto the website, I needed to put a software license on it. I looked up all the licenses that are available, and there were a lot of them. I decided the one I liked the best was the MIT license, which was a notice that you would put on your source, and it would say: "you're allowed to use this for any purpose you want, just leave the notice in the source, and don't sue me." I love that license, it's really good.
... So I added one more line to my license, which was: "The Software shall be used for Good, not Evil." ..."
I was using JSMin (py) today ~ http://www.crockford.com/javascript/jsmin.html wondering why there was no installer and poking around I found this article. Seems the addition of additional line in the MIT license gives lawyers headaches.
Not just lawyers - anyone sensible. It's not open source any more - you can't restrict what open source is used for - and extremely vague.
DIY licenses are a bad idea. In this day and age you should probably pick between MIT, Apache, LGPL and GPL, and maybe something like the Affero GPL for open source, in order of how much they limit people using your code.
I was using JSMin (py) today ~ http://www.crockford.com/javascript/jsmin.html wondering why there was no installer and poking around I found this article. Seems the addition of additional line in the MIT license gives lawyers headaches.