updates the LICENSE to include a proper header, a range of years for copyright...

[choskim]

Hello,
I'm a fan of Javascript Koans, and I noticed that the LICENSE needs to be updated.

[gregmalcolm]

I'm not sure putting a range on there is a good idea. It implies the license expires in 2015 unless we keep updating it.

[choskim]

Hi, Greg! From what I know, when there has been a material change to code, the copyright should include that year. If there has been consecutive years when material changes have been made, then a range can be provided. Here's an article that says something similar:

http://programmers.stackexchange.com/questions/210472/is-renewal-of-mit-license-needed-on-github-at-the-beginning-of-each-year

For an range of years being used in a popular library, here's the link to D3's MIT License:
https://github.com/mbostock/d3/blob/master/LICENSE

U.S. Copyright law states that a copyright will expire at the death of the copyright owner and an additional 70 years post death:

http://www.copyright.gov/help/faq/faq-duration.html

So updating the year will just give you more time for your copyright.

The main reason why I brought up this issue deals less with the copyright being extended for additional years. The main reason deals more with relaying the following message to potential users:

This repo is being constantly updated and the copyright is a great way for us to show it. Even if we don't make commits on a daily or monthly basis, updating the license every year shows that we at least look at the repo every year.

[gregmalcolm]

Fair enough, thanks! :)