[dev] Horde License File Shipping and Horde License Header Cleanup

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Ralf Lang <lang at b1-systems.de>:
>
>> Am Mittwoch, 31. August 2011, 10:57:30 schrieb Jan Schneider:
>>> Zitat von Ralf Lang <lang at b1-systems.de>:
>>>> Hi devs,
>>>>
>>>> I think the (several) threads and discussions on these two topics
>>>> have lead to
>>>> the following consensus:
>>>>
>>>> - The horde git packages (frameworks, apps and helpers) are meant to be
>>>> licensed as either BSD (2 clause?), LGPL-2.1, GPL-2.0 or Apache Software
>>>> License-derivate based on ASL 1.1. The Exception is Horde_Ldap which is
>>>> LGPL-3.0. Contradicting headers are just wrong or not precise.
>>>>
>>>> - It is ok to ship the license files with framework packages.
>>>>
>>>> Based on this I'd like to change the following items:
>>>>
>>>> - Add/update the license file in the packages
>>>> - Make the license statements in package.xml more precise
>>>> - Change links pointing to external license files into links to horde.org
>>>> - Change file headers along with the links.
>>>>
>>>> I will not touch anything that looks like owned by other
>>>> persons/entities. These need discussion/clarification.
>>>>
>>>> Did I get things right?
>>>> This summary is a request for you to approve/reject.
>>>
>>> +1
>>>
>>> And while you are touching the file headers anyway, you could at the
>>> same time change the Copyright owner from "Horde Project" to "Horde
>>> LLC".
>>>
>>> Jan.
>>
>> OK. Do you want a changelog entry once a component is through  
>> checking/fixing?
>
> Not necessary.

Agree with everything.  Changelog is not necessary since this is  
cleanup, not a substantive change to the license.  Also, I would think  
that BSD 2-clause is preferable to the 3-clause.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]