incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Om <bigosma...@gmail.com>
Subject Re: [VOTE] Release InstallApacheFlex 1.0 - RC5
Date Wed, 26 Sep 2012 19:45:49 GMT
On Wed, Sep 26, 2012 at 12:38 PM, Alex Harui <aharui@adobe.com> wrote:

>
> > -----Original Message-----
> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> > Sent: Wednesday, September 26, 2012 12:21 PM
> > To: flex-dev@incubator.apache.org
> > Subject: Re: [VOTE] Release InstallApacheFlex 1.0 - RC5
> >
> > While I'm happy with the much needed +1's, I do think that for due
> diligence this
> > observation by Alex needs some attention:
> >
> > > should be easier in the future, but I think we need to get this right.
> > > I think there is a legal issue here.  I'm not clear that Adobe would
> > > be happy to have the AIR SDK downloaded without some acceptance of the
> > licensing.
> >
> > This is a different argument than Betrand's; a reconsideration may be in
> order?
> >
> > EdB
> Let me add here my experience.  Recently, Adobe shutdown most of
> opensource.adobe.com and moved everything to the Open@Adobe
> SourceForge wiki.  That wiki did not allow for interaction, so I had to
> create
> a custom SWF UI to present the licensing before downloading Adobe Flex
> because
> Adobe legal really wanted folks to actively accept the license.  I had to
> resort to
> having the wiki redirect to the SWF UI on my blog in order to have legal
> sign off.
>
> On the current Adobe AIR SDK download site it tells you that by hitting
> the button
> to download you accept the Adobe license.
>
> I think (with my Adobe hat on), that we need to make it clear that the AIR
> SDK is
> under an Adobe license.  I think that Apache would want us to do that as
> well.
>
>
I understand the issue.  When I started out with the AIR app, I just copied
what the .bat file that Carol had written was doing.  I went back to see
those scripts and realized that it has changed completely.

I think the best way to handle this is to add all the required list of
binaries in the 2nd screen and enable the "Install" button only after the
user explicitly agrees.  I will play with the UI and resize the app as
needed so that there are no scrollbars in that screen.

Would this change be sufficient for a release?

Thanks,
Om

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message