Let's be clear that Spoon's roadmaps and priorities are independent of the Flex project in the Apache incubator. Several committers to Flex are also Spoon members and they will coordinate with each other and hopefully make major contributions to the Flex project.
But if you are a committer and you want to check something in, you don't have to get Spoon involved, just do it. If folks don't like it, it will get vetoed. And as I said in my other post, I would discuss major changes on this list before committing it. If you are not yet a committer, wait until we get JIRA up then submit a patch, get folks to vote for your patch then get a committers attention to review and accept it. On 1/4/12 12:17 PM, "Fréderic Cox" <frede...@exuvis.com> wrote: > This makes sense to me if we can also vote on the features of Spoon to > influence priority > > On 04/01/12 21:08, "Jonathan Campos" <jonbcam...@gmail.com> wrote: > >> That is an exact question that I asked at the Flex Summit specifically for >> the group. >> >> Roy Fielding had a great analogy/answer. >> The main idea is that this is that we are throwing a party, not running a >> business with free labor. So people need to be energized about what they >> are doing, they aren't there to be given tasks. >> >> As such there is no roadmap. You may come up with a great idea and start >> working on it, then when other people see what you are doing they may >> join. >> Over time your idea snowballs and gets added in, but this doesn't mean >> that >> there is a formal roadmap for people to sit at and program away against. >> >> However this is where Spoon comes in. We do have plans and roadmaps of >> features we want to add. Some take time and require people. If you are >> interested in our roadmap (our party) you and anyone else is free to join. >> >> Make sense? >> >> J >> >> On Wed, Jan 4, 2012 at 1:58 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 >>>> >>>> >>> >> >> >> >> -- >> Jonathan Campos >> Dallas Flex User Group Manager >> http://www.d-flex.org/ >> blog: http://www.unitedmindset.com/jonbcampos >> twitter: http://www.twitter.com/jonbcampos > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
