On Wed, Aug 15, 2012 at 4:47 AM, Bertrand Delacretaz <bdelacre...@apache.org > wrote:
> Hi Carlos, > > On Wed, Aug 15, 2012 at 11:01 AM, Carlos Rovira > <carlos.rov...@codeoscopic.com> wrote: > > ...the problem is not about tooling. Is about the things we plan to do. > The > > revision and transformation of the core at flex... > > I guess that's where the disconnect is, I hear you and others saying > "we plan to do big things" but I see just small things (besides code > donations) happen at [1]. You bring up a very good point. And this needs to be made clear to everyone. And that is, there are many of us waiting until the core foundation of this project is laid before jumping in. That is, the test suite and other donations that we have been waiting for from Adobe and the workflow model is setup. I'm not going to go in and modify the framework if I can't then test that my changes don't break things. I'm not going to spend a lot of time trying to setup a development environment until all the pieces are in place to do so. Until recently those pieces weren't in place. I'm also not going to want to help if the process and workflow is a nightmare. Think about this, the Flex SDK has been an open source project for a few years now. Because of the nature of the business we're in we have slices of time that we can commit (we meaning me). We need to be have a model and ecosystem that supports where we are able to make drive by commits. ... and what Omar just said about community and collaboration on GitHub.
