I'm comfortable with SVN too but support the move to Git / GitHub because it is an environment that makes work like this much more efficient. People can easily fork the project, make a change and get it to a working state. Then the main branch can easily patch those changes back in. It is also an active community. There are many people that can join in, see changes and discussions.
However, I don't know how much of GitHub's workflow we can integrate into an ASF project. On Mon, Aug 13, 2012 at 12:03 PM, Carlos Rovira < carlos.rov...@codeoscopic.com> wrote: > Igor, until now (flex < 4.8) I don' t see deep changes in flex core like > the ones people want to perform. Spark and other features were always > "additive". > > SVN works well with such projects. But we target now other kind of changes > in the core that never was done before in flex. > > So I would like to know how would you plan to modify a core piece like > UIComponent with near 15k code lines while other people make other changes > without a tool like GIT... > > > > El lunes, 13 de agosto de 2012, Igor Costa escribió: > > > Carlos > > > > "But the real problem for me is that we can't target the changes we plan > > without a tool like Git. Maybe people that does not know Git does not > > understand this, but we were not able to make such deep changes if we are > > using SVN." > > > > Flex SDK was built over 4 versions using SVN, Since Flex 3 we > open-sourced > > SDK. > > > > The only questionable thing for this entire thread is we must focus on > Flex > > project not in Infra. > > > > SVN or Git whatever, we have to keep focus on Flex evolves, otherwise > > community members will lose their interesting on the Apache Flex project. > > > > > > To make a final statement we have to open vote and finish up and move to > > the next episode. Mustella, Falcon, things that are important right now > for > > SDK. > > > > > > If SVN worked so well by until know, why make changes on winning team? > > > > > > Regards > > ---------------------------- > > Igor Costa > > www.igorcosta.com > > www.igorcosta.org > > > > > > On Mon, Aug 13, 2012 at 1:42 PM, Carlos Rovira < > > carlos.rov...@codeoscopic.com <javascript:;>> wrote: > > > > > IMHO, and taking into account that I'm only a not-binding vote... > > > > > > I don't see real arguments against Git and maybe as Omar says people > does > > > not want to figth with yet another SCM... > > > > > > But the real problem for me is that we can't target the changes we plan > > > without a tool like Git. Maybe people that does not know Git does not > > > understand this, but we were not able to make such deep changes if we > are > > > using SVN. > > > > > > That's the real problem, and that's what we end planing the use of > > > Git...this is not a techy discussion. We at work had to change two > months > > > ago due to hard refactors in our main product, and we changed because > SVN > > > was not letting us do such deep changes. > > > > > > So my vote will go for Git without doubt...if we don't use it, we > should > > > not be able to change things like UIComponent...hope people that does > not > > > want Git understand this. > > > > > > > > > > > > > > > > > > 2012/8/13 Omar Gonzalez <omarg.develo...@gmail.com <javascript:;>> > > > > > > > On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <cfram...@adobe.com > <javascript:;> > > > > > > > wrote: > > > > > > > > > A clarification question about Git: > > > > > > > > > > Would I lose the ability to look at the repro thru the web. I make > > use > > > of > > > > > https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more > > often > > > > then > > > > > I expected. > > > > > > > > > > Carol > > > > > > > > > > > > > > > > > > > > You can browse it through Git HTTP: > > http://git.apache.org/flex-site.git/ > > > > > > > > Or you can view it through GitHub: https://github.com/apache/flex > > > > > > > > -omar > > > > > > > > > > > > > > > > -- > > > Carlos Rovira > > > Director de Tecnología > > > M: +34 607 22 60 05 > > > F: +34 912 35 57 77 > > > <http://www.codeoscopic.com> > > > CODEOSCOPIC S.A. <http://www.codeoscopic.com> > > > Avd. del General Perón, 32 > > > Planta 10, Puertas P-Q > > > 28020 Madrid > > > > > > > > -- > Sent from Gmail Mobile >
