flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Reddin <gred...@gmail.com>
Subject Re: [POLL] Maven and Apache Flex
Date Mon, 03 Dec 2012 18:51:17 GMT
That's good to hear. Thanks for staying with it. 

Sent from my mobile device.

On Dec 3, 2012, at 12:07 PM, Alex Harui <aharui@adobe.com> wrote:

> Update:
> Adobe legal says we (probably Chris) can code up a mockup that runs against
> some dummy assets (as Chris suggested) in the open.  Then Legal can review
> the basic flow from that mockup and decide if it will be sufficient.
> -Alex
> On 11/29/12 11:28 PM, "christofer.dutz@c-ware.de"
> <christofer.dutz@c-ware.de> wrote:
>> Hi Greg,
>> we are not talking about the entire plugin ... just one fragment (assumably
>> not even 5% of the entire suite) that deals with downloading stuff from Adobe.
>> All the other parts of the plugin would be developed in the open :-)
>> Chris
>> ________________________________________
>> Von: Greg Reddin [gredbug@gmail.com]
>> Gesendet: Freitag, 30. November 2012 01:49
>> An: flex-dev@incubator.apache.org
>> Betreff: Re: [POLL] Maven and Apache Flex
>> Personally I don't see any way I can support being forced to develop this in
>> private. Apache doesn't work that way. I suppose if that's the only choice
>> they give us and Chris is willing to do it on his own he can submit it to us
>> as a patch but there's no guarantee it will be accepted. For myself I'd prefer
>> to manually download the artifacts than to accept an agreement like that.
>> At this point I don't guess I would veto a commit if this is what it comes to
>> but this is a horrible way to develop a plugin that is essential to many Flex
>> users. It should be developed in the open in a way that addresses everybody's
>> needs including Adobe's and the community's. This is a slap in the face to the
>> Apache Way.
>> Sent from my mobile device.
>> On Nov 29, 2012, at 5:01 PM, Alex Harui <aharui@adobe.com> wrote:
>>> Our legal team requested a few days to consider whether they really need
>>> this developed in private.  So if they come back that they want it to be
>>> private I will present this option.
>>> If you want to wait to get their answer that is fine, or you can start now
>>> but please do it in private.
>>> On 11/29/12 2:52 PM, "christofer.dutz@c-ware.de" <christofer.dutz@c-ware.de>
>>> wrote:
>>>> Another option would be to place dummy files on the Adobe download servers
>>>> (but allready with the real names) and to develop the mojo publically ...
>>>> soon as Adobe is sattisfied with the license accepting and downloading part,
>>>> they could replace the dummy files with real ones and we could concentrate
>>>> on
>>>> "mavenizing" the donload.
>>>> Chris
>>>> -----Urspr√ľngliche Nachricht-----
>>>> Von: Justin Mclean [mailto:justinmclean@gmail.com] Im Auftrag von Justin
>>>> Mclean
>>>> Gesendet: Donnerstag, 29. November 2012 23:43
>>>> An: flex-dev@incubator.apache.org
>>>> Betreff: Re: [POLL] Maven and Apache Flex
>>>> HI,
>>>>> One important thing, legal may want you to develop this plug-in
>>>>> without checking it into any public source code repository until they
>>>>> have a chance to see it work.
>>>> Can you give their reasons behind this?
>>>> Wouldn't it be better to have it worked on collaboratively in the open by
>>>> the
>>>> community?
>>>> Thanks,
>>>> Justin
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui

View raw message