Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 65.55.169.72 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Subject: Re: Squiggly dictionaries license 
Thread-Topic: Squiggly dictionaries license 
Thread-Index: 
 AQHPyCKbSNnqiHHnQkqgJ2YULmmV/ZvwuTUAgADXf4CAAAs/AIAAf8+A///7MoCAAHi7AP//vI+AgADCeQCAGQ9oAIAAMjeAgAQveID//6mqgA==
Date: Wed, 24 Sep 2014 16:49:56 +0000
Message-ID: <D0484076.324BB%aharui@adobe.com>
References: <5F419A34-1DE4-434A-AE32-2F661EA81097@classsoftware.com>
 <D02DE3F3.30C1F%aharui@adobe.com>
 <FEEE52C2-5368-434A-BB91-0262784E5596@classsoftware.com>
 <D02E9E33.30DCE%aharui@adobe.com>
 <3AA78E1E-90AD-46F6-B357-BAD043C2964D@classsoftware.com>
 <D02F0A16.30E7D%aharui@adobe.com>
 <45F7CAEA-3A07-44D4-BDB4-7A0332A35258@classsoftware.com>
 <D02F35C9.30ECB%aharui@adobe.com>
 <A5D5A7D5-BDED-429E-AB43-DC65D88F8483@classsoftware.com>
 <215B9651-9AF4-49D5-944A-B6D37D38B3FE@classsoftware.com>
 <D0450898.321BF%aharui@adobe.com>
 <C31F6AC7-BA1F-479F-B76B-118E1D6FA165@classsoftware.com>
In-Reply-To: <C31F6AC7-BA1F-479F-B76B-118E1D6FA165@classsoftware.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.4.4.140807
Content-Type: text/plain; charset="us-ascii"
Content-ID: <394DD1E0C2A1094696F9E3A180EE0FF3@namprd02.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I looked again this morning.  Is there something I was supposed to get
from that?  I did not see anything that would make me think the current
text in flex-utilities/Squiggly/LICENSE is correct.  IMO, there are two
choices:

1) go against the folks who prefer short licenses and include the entire
Hunspell README in the LICENSE.
2) Use a simple pointer without copyright or excerpt from the README as
described in the how-to such as:

This product bundles SCOWL and Friends dictionaries, which are available
under a
"BSD/MIT-like" license.  For details, see
dictionaries/en_US/README_en_US.txt or dictionaries/en_GB/README_en_GB.txt.


Either one is fine with me. Open Office definitely leads the way in long
licenses.  I think what we have right now is at best misleading as one
could be fooled into thinking the excerpt is the complete license.  I know
you have additional text above saying to look for more details, but I
don't understand why we wouldn't want to use the template.  Every time we
try to create our own wording we run the risk of doing it wrong, and the
response on legal-discuss did not say the current text is correct.

-Alex

On 9/24/14 7:58 AM, "Justin Mclean" <justin@classsoftware.com> wrote:

>Hi,
>
>Did you actually look at the links/reachearch or what currently in Git?
>In particular look at the aggregated files from Open Office.
>
>Does what we currently have meet the minimum legal requirements? And if
>it doesn't exactly what requirement are we not meeting?
>
>Thanks
>Justin