Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
From: Christofer Dutz <christofer.dutz@c-ware.de>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Subject: AW: Current FlexJS license/notice issues
Thread-Topic: Current FlexJS license/notice issues
Thread-Index: AQHSEs7LLLu02b9LpEqRJPQfSm/wkKCB8FQAgAAPpYCAAKWegIAAXbQAgAB3FwCAAAPuAIAAkcAAgBHv0wCAAC6NgIAAEt6AgADDSQCAAE/0AIAABnkAgAADBoCAAAPLAIAABAyAgACUUgCAAAEA1A==
Date: Tue, 4 Oct 2016 07:25:11 +0000
Message-ID: <HE1PR0501MB2428271952D3278B12950944A2C50@HE1PR0501MB2428.eurprd05.prod.outlook.com>
References: <D2D49717-18BB-4F32-8E02-E8C89D76C529@classsoftware.com>
 <D40622D7.75A35%aharui@adobe.com>
 <8F3E5A47-1C28-45E4-A424-C9B9DC3CDDB7@classsoftware.com>
 <D406AF21.75B17%aharui@adobe.com>
 <D71A8BB5-0D64-495E-887C-8358643C4E48@classsoftware.com>
 <D407736A.75C85%aharui@adobe.com>
 <AE3F8024-0A15-4C8F-BF5E-68F96FECF64A@classsoftware.com>
 <D407F14D.75CED%aharui@adobe.com>
 <3620F33B-99F6-4E0D-82E3-03515CD692B3@classsoftware.com>
 <D41723CE.76A75%aharui@adobe.com>
 <95A0EDF2-BCDE-4CE6-B111-35EDA5747FEA@classsoftware.com>
 <D417D1A1.76B0B%aharui@adobe.com>
 <1B5FE461-773B-433A-8690-BD5CEF85E542@classsoftware.com>
 <D4181FF9.76BE8%aharui@adobe.com>
 <4904AC89-3EAA-4388-ADD5-1EBA6B1AB8F2@classsoftware.com>
 <D4182449.76BF7%aharui@adobe.com>
 <77AA6357-8837-4540-9ED1-7E52BDD8DB8A@classsoftware.com>,<D418A186.76CC7%aharui@adobe.com>
In-Reply-To: <D418A186.76CC7%aharui@adobe.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
received-spf: None (protection.outlook.com: c-ware.de does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_HE1PR0501MB2428271952D3278B12950944A2C50HE1PR0501MB2428_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2016 07:25:11.4676
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d387546-1437-4b89-846c-691d64a7e74d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0501MB2428
archived-at: Tue, 04 Oct 2016 07:25:25 -0000

--_000_HE1PR0501MB2428271952D3278B12950944A2C50HE1PR0501MB2428_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

+1 to let Justin proceed as he suggested.


Chris

________________________________
Von: Alex Harui <aharui@adobe.com>
Gesendet: Dienstag, 4. Oktober 2016 09:21:22
An: dev@flex.apache.org
Betreff: Re: Current FlexJS license/notice issues


On 10/3/16, 3:30 PM, "Justin Mclean" <justin@classsoftware.com> wrote:

>Hi,
>
>> But if you are going to do something, it should be what is recommended
>
>I am doing what is recommend by policy and consensus on legal discuss.

Roy says we can distribute the work if there are missing headers so there
must not be a policy violation involved.

>
>> Did you contact the upstreams?
>
>As I have stated I will yes and I will be doing that with my Flex PMC hat
>on.

I've been unclear on what your first step is going to be.  Sounds like we
agree that the first step is to contact the upstreams.


Are other PMC members ok with approaching the upstreams as a PMC?  Do
other PMC members prefer to use "trust" and "intent" and not bother 3rd
parties on these details?   Maybe I'm in the minority these days.  It
would certainly end the debate if the upstreams added headers, but I don't
know if we want our project to have the reputation for being the stickler
for these details.

Thoughts?
-Alex


--_000_HE1PR0501MB2428271952D3278B12950944A2C50HE1PR0501MB2428_--