On Tue, Aug 14, 2012 at 11:17 AM, Alex Harui <aha...@adobe.com> wrote:
> > > > On 8/14/12 11:05 AM, "Gordon Smith" <gosm...@adobe.com> wrote: > > > I'd like to start a discussion of where Falcon will live in the Apache > > repository. > > > > The initial donation will be an Eclipse project and Ant scripts for > building > > Falcon itself. Later we will donate another Eclipse project and Ant > scripts > > for testing Falcon > > > > Although it is Java code, I don't think it should go into trunk/modules > with > > the older compiler. It would be confusing to have a bunch of > subdirectories in > > trunk/modules, some of which are for the old compiler and some of which > are > > for the new compiler. So I propose that the two Falcon projects live > inside > > trunk/falcon. > > > > Like the old compiler, Falcon is tied closely to the Flex framework > because of > > the semantics of MXML. Therefore, I think Falcon belongs initially > "inside" > > Flex, like the old compiler was inside Flex. Eventually, it would be > > interesting to try break many of these dependencies and let Falcon > become its > > own project independent of the framework, but I see that as longer-term > > evolution. > > > > - Gordon > > > FWIW, keep in mind we also expect TLF to get VP signature this week as well > and BlazeDS is in progress. IMO, All three are standalone entities and > should have top-level project status. I don't know how hard it is to move > the current trunk into an directory called sdk, but that would be my first > choice as in, when you go here: > https://svn.apache.org/repos/asf/incubator/flex/ Well, if we were using Git, we could just move it, commit and be done. (Sorry, I had to! hehe, I'm just teasing here) > > > You currently see: > branches > external > import2 > site > tags > trunk > utilities > whiteboard > > And I would like us to have: > blazeds > external > falcon > import2 > site > tlf > sdk > branches <-- these 3 are moved down from the top level > tags > trunk > utilities > whiteboard > > I'm not sure now is the right time to be moving trunk so I'd be willing to > live with some inconsistency right now and just have > blazeds > branches > external > falcon > import2 > site > tags > tlf > trunk <-- this is the current top-level trunk > utilities > whiteboard > > Thoughts? > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > I would opt for the second choice, leave trunk along and add /falcon etc. -omar
