When I was working on TLF and Flex SDK it took about 3 days to a week to get the "sources" setup. I documented all the steps in the wiki and have went back to them ~3 times to get things setup again. It shouldn't be that hard.
I could download and setup a new Flex SDK binary for Flash Builder easily enough with the SDK but I still don't know how to contribute into the main Flex branch. The thought of putting the SDK on GitHub and requesting a local library seems like clear blue skys compared to the options we have now. And it may be that I feel like all the legal garbage about binaries and source and so on on Apache have hindered nearly all our progress. If we can't get a better setup going for maven or ant (where there are 10 different download locations) let's put it all up on Github and ask for permission to include what we need (maven may solve this). Or send a request to notify, "We need this binary and plan to put it up. If this is not ok reply in the next week." There's too many restrictions to get anything done. If Apache has too many restrictions for setup then let's move it. On Fri, Nov 6, 2015 at 9:14 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 11/6/15, 2:06 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: > > >I don't think there should be a problem with this. Unless there are some > >technical issues with your restructuring proposal, we all should be able > >to > >come to a consensus and move ahead. > > > >I believe the best time to do this would be - right after the FlexJS 0.5 > >release. > > Well, there’s also restructuring going on inside frameworks/projects as we > do the back port from JS to AS, so I’d prefer that folks pitch in to help > finish that, then we execute on the restructuring. > > But I would like to see a proposal for the restructuring now. Or did I > miss it somewhere? > > Thanks, > -Alex > >
