I agree with Peter. There needs to be some kind of structure so we don't en up with some kind of mishmash of features that dont work together. -Arthur
--- Arthur Lockman a.rthr.me @arthurlockman Sent from my iPhone On Jan 4, 2012, at 2:59 PM, Peter Elst <peter.e...@gmail.com> wrote: > Thats a good point I've not been clear on either - is roadmap discussed on > the mailinglist and voted on so there's a bit of structure to what type of > things get worked on rather than a random collection of bug fixes and > non-related features? > > - Peter > > > On Wed, Jan 4, 2012 at 7:17 PM, Jeffry Houser <jef...@dot-com-it.com> wrote: > >> >> Be sure to watch the "What it Means to be an Apache Project" from the >> Flex Summit, here: >> >> http://tv.adobe.com/show/flex-**community-summit-december-**2011/<http://tv.adobe.com/show/flex-community-summit-december-2011/> >> >> My understanding is that we do whatever we want. I don't know how that >> goes from "chaos" to "release" yet, though. >> >> >> On 1/4/2012 2:12 PM, Michael Schmalle wrote: >> >>> Hi All, >>> >>> I was just curious if there was any Apache Flex specific information >>> floating around about how duties might be divided on each others strength >>> in relation to our understanding of the SDK. >>> >>> I know there is the official committer information page that Alex >>> provided but has there been any discussion on how an initial committer can >>> prepare for whats to be expected in the Apache Flex project? >>> >>> Or is this just to soon to ask this question? >>> >>> Thanks, >>> Mike >>> >>> >>> >> >> -- >> Jeffry Houser >> Technical Entrepreneur >> 203-379-0773 >> -- >> http://www.flextras.com?c=104 >> UI Flex Components: Tested! Supported! Ready! >> -- >> http://www.theflexshow.com >> http://www.jeffryhouser.com >> http://www.asktheflexpert.com >> -- >> Part of the DotComIt Brain Trust >> >>
