Alex's comment about dedicated resources is an important one. Without a home to call our own, our toes will likely be stepped on and we are likely to step on the toes of others ( not an 'if' but a 'when' ). Can we really afford that at this point?
What I'm trying to say is that project velocity, resources, and resource restrictions are interdependent. If we hope to gain the momentum we so desperately want / need, dedicated resources may just be the push we need to kick this thing into a higher gear. Consider these two items... # dozens of companies around the globe are using customized Flex SDKs in production software # many of these companies compile the entire SDK from source So... is it any wonder that people are looking at Apache Flex and saying, "what's the hold-up guys?" To be fair, getting Flex to run under the Apache umbrella has grown arms and legs that few could imagine. I have a solution for the Jira dump... forget it... move on... I can almost guarantee that more than 60% of it is out-dated, 20% is irrelevant, 10% is ancient history, 9.9% are actually Flash bugs, .01% is applicable to Apache Flex .... and it will take FOREVER to troll through all the mire to get to that .01%. I have a solution for the build server... everyone drop everything you're doing, get a Mac Mini, throw it in a colo, and concentrate on building the SDK just like Adobe did it. Getting the first release out the door is of paramount importance... once we get to that point - we have 'forever' to renovate. Rick Winscot On Tuesday, June 5, 2012 at 12:54 PM, Alex Harui wrote: > > > > On 6/5/12 7:59 AM, "Bertrand Delacretaz" <bdelacre...@apache.org > (mailto:bdelacre...@apache.org)> wrote: > > > > Although the JIRA import problems need to be solved, I don't see what > > prevents people from using the existing instance at > > https://issues.apache.org/jira/browse/FLEX to go forward without > > having to wait for that. > > > > Folks are welcome to file new bugs there, but I thought we agreed we didn't > want duplicate issues to manage after the import happens. > > > > I assume issues created there can be linked to existing issues in the > > Adobe Flex JIRA if that's still up, and if that's not the case we can > > fairly easily host a static copy of that somewhere so that people can > > find the required information. > > > > Adobe JIRA is still up, but I am hearing that it won't be up forever. > > What does it take to host a static copy, and, if we can have a standalone > copy, why does it have to be static? I know it is a trade-off, but having > our own JIRA instance still seems to have more pro's than con's. The > likelihood of transferring instances between Flex and other Apache projects > seems minimal. > > Maybe every large project going into the incubator should be required to > contribute a server and disk space. Then it would be our own fault if we > run out of space doing CI builds, we can import SVN dumps whenever we want > to, and we can have our own JIRA. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
