On Fri, Apr 27, 2012 at 2:40 PM, David Coleman <david_coleman_...@hotmail.com> wrote: >... If I read it correctly, this license provides the right to re-distribute >these binaries. And it also grants the right in (c) to *reproduce* them! >Seems to cover the scope of actions which this group wishes to take to me....
That might be correct but there's a number of places that mention "internal use", and Flex redistributing these files would not be internal use IMO, so it seems safer to avoid doing that. The key thing for an Apache project is that we don't want to put any restriction on users of our code beyond the Apache License. Having parts of a distribution that are for "internal use only" does not work. -Bertrand > > See excerpt below: > > Subject to the terms and conditions of this Agreement, Adobe grants You a > non-exclusive, nontransferable license to: (a) modify those Flex Framework > Binaries that have not been digitally signed (signed binaries are denoted by > an “.SWZ” extension); (b) internally use and reproduce the Flex Framework > Binaries (in modified or unmodified form) for the purpose of developing > Developer Programs, > > (c) internally use and reproduce the Flex Framework Binaries (in modified or > unmodified form) as part of Your internal website for the purpose of > compiling the Developer Programs, > > (d) copy and distribute the Flex Framework Binaries (in modified or > unmodified form) as compiled into Developer Programs; > > (e) copy and distribute, through multiple tiers of distribution, the Flex > Framework Binaries (in modified or unmodified form) with a Developer Program > for use at runtime of such Developer Program, and > > (f) copy and include the Flex Framework Binaries (in modified or unmodified > form) as part of Your public website for use at runtime by the Developer > Programs that are distributed from Your website(s). You may in no instance > modify Flex Framework Binaries that have been digitally signed. > > > > >> Date: Fri, 27 Apr 2012 12:31:48 +0000 >> From: j...@apache.org >> To: flex-dev@incubator.apache.org >> Subject: [jira] [Created] (FLEX-53) Clarify usage of playerglobal.swc and >> airglobal.swc >> >> Bertrand Delacretaz created FLEX-53: >> --------------------------------------- >> >> Summary: Clarify usage of playerglobal.swc and airglobal.swc >> Key: FLEX-53 >> URL: https://issues.apache.org/jira/browse/FLEX-53 >> Project: Apache Flex >> Issue Type: Task >> Components: Project Management >> Reporter: Bertrand Delacretaz >> Assignee: Carol Frampton >> >> >> As discussed in [1], Flex requires >> >> 1) playerglobal.swc to compile the majority of the Flex components >> 2) airglobal.swc to compile the Flex components targeted at AIR >> 3) many pieces of the AIR Integration kit which are need to do Flex mobile >> development >> >> We might need clarification for 3), but for now we need to find out how to >> use these files while abiding by their license requirements and complying >> with the ASF's restrictions on incompatible license >> (http://www.apache.org/legal/resolved.html). >> >> According to Alex in [1] those two files are covered by this license: >> http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf >> >> And it seems like they're only needed at build time, so users of Flex could >> get them independently. >> >> [1] http://markmail.org/thread/muckogic3f2zwd7o >> >> -- >> This message is automatically generated by JIRA. >> If you think it was sent incorrectly, please contact your JIRA >> administrators: >> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> >
