Ares 0.15 release

[Sean Kelly]

Don Clugston wrote:
> Bastiaan Veelo wrote:
>> Don Clugston wrote:
> 
>> I don't think you need the complete license text in every file. Raymond
>> and Raymond [2] tell us that "It is not necessary to include a copy of
>> the license in every source file, but it is a good idea for the header
>> comment to refer readers to the license file with a comment like this:
>> This program is open source.  For license terms, see the LICENSE file."
> 
> That's great news. I will do that from now on.

Same here.
> 
>>> What I'd really like to find is some kind of "non-infect" free 
>>> license for libraries. That is, you can do anything you like with 
>>> this code, except that if you redistribute the source code AS SOURCE 
>>> CODE, it must remain with the same license. So that if it's included 
>>> in a GPL project, that single file doesn't get GPLed, and if it's in 
>>> a commercial library where the source is sold, that single file 
>>> remains free.
>>> But since I don't know of any license that does that, any 
>>> unrestricted license (including public domain) will do.
>>
>> The MIT license [3] does this. The license itself consists of a single
>> sentence, followed by a disclaimer.
> 
> Thanks!

Very nice.  I'll be using this for the C headers in Ares.  And others on 
request, as it's easiest to simply use a single license for an entire 
project.


Sean