Some points to take into account: * Apache is prepared only to accept patches. People like me can't help nothing with infrastructure or GIT things until we don't reach the committer status.
* This project does not work like others because is half million files with lots of knowledge to know to get to be productive. Other projects barrier is lower since it only requieres a know a technology (i.e:java) and the goals are more moderated. * Here we have frameworks, compilers, and so on...without organization is impossible (is what Michael states that he alone can't do nothing). While apache way is for individuals to contribute individual things. * I'm with Michael that this is a ghost town since very few committers from the initial setup are active. Others although love flex are in actual wars with HTML5, so we shouldn't expect to see it come back. * Regarding SVN. We were working with SVN (not GIT) while submitting patches to mustella. Only we used github to share the patches/pull request. But something that could be more agile was a pain and make us to throw the towel....that is very - very - very - bad...can't express what kind of damage make to this project such procedure...the real thing is that we talked to come back as Git and Github was setup...but taking into account that Apache infra needs some python guy that's a dead lock. Erik, I'm a bit of frustrating, but in the end I'm solving my problems at my company level, so can't live with this situation. But is a shame that the apache community and the apache way is making this project a ghost town (IMHO), while if we work in a for in github this could be really going up. One thing is for sure...or this trend change, or flex will be dead in few months. 2012/10/18 Michael Schmalle <apa...@teotigraphix.com>: > Erik, > > Please man, I mean no disrespect in any of these emails to you it's a > frustration I have been holding onto for about 10 months now. > > The github reference was in relation to supporting a small, manageable open > source project in a github account. The point was a lot of those projects > are small and manageable. > > The flex project is huge and all interdependent. Yes, Apache says no road > maps but common, active contributors need to have conversations and create > dialog about future implementations. Maybe not when creating higherlevel > things but when we are talking about a compiler, I'm not just stepping into > the wild unkown without a "little" backup here, meaning a couple other > enthusiastic developers at my side. IE I'm not talking about making a > TabNavigator implementation in my whiteboard here. > > So to answer, I have no knowledge of how to get GIT running on Apache. > > Mike > > > > Quoting Erik de Bruin <e...@ixsoftware.nl>: > >>> Supporting some github project is definitely where I could "if you don't >>> like it, change it." >> >> >> Well, that is a good place to start! Apache Infra has indicated that >> they would help the project move to Git if the project 'donated' a few >> volunteers to help with the move and to support the new workflow after >> that. I'm sure the project would much appreciate it if you could be >> one of those volunteers. >> >> Thank you, >> >> EdB >> >> >> >> -- >> Ix Multimedia Software >> >> Jan Luykenstraat 27 >> 3521 VB Utrecht >> >> T. 06-51952295 >> I. www.ixsoftware.nl >> > > -- > Michael Schmalle - Teoti Graphix, LLC > http://www.teotigraphix.com > http://blog.teotigraphix.com > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 CODEOSCOPIC S.A. Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
