If Spoon have organisation and/or heirarchy, and Apache accepts contribution from anyone, then it might be simple: the Spoon Foundation creates a Spoon Roadmap - what they hope to deliver to Flex and when. They can post it on their Spoon.as website. Those that want to be part of an organised/guided/led effort can join Spoon, contribute to their roadmap, and help to turn that roadmap into reality by contributing the code to Flex. Since Spoon exerts no authority or control over Apache Flex everyone remains happy and the "Apache way" has not been violated.
Those that want to stick to the standard Apache scratch your own itch philosophy can ignore Spoon and continue scratching. John 2012/8/2 Alex Harui <aha...@adobe.com>: > > > > On 8/2/12 12:26 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > >>>> Some direction (agreed upon >>>> by all the project leads, to be sure) will help get things off the >>>> ground, or at least move along at something more than a glacial >>>> pace... >>> But there are no project leads. Just a bunch of committers and lots of >>> other folks on the mailing list. >> >> I'm not being difficult, I'm just trying to understand the Apache way: >> aren't the PPMC (Podling Project Management Committee) not the >> 'project leads'? >> > I don't see the PMC as project leads. They have more of an administrative > responsibility than a technical one. See [1]. > > There is no hierarchy in the engineering. Nobody gets to tell anyone else > what to do. Committers can veto your work, but for technical reasons, not > because it wasn't on the roadmap or a high enough priority. > > [1] http://www.apache.org/dev/pmc.html > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
