Hi Alex, when we get the official repo in Apache we'd not need to have github, but if you use it or not it would not be important. Git is "distributed" so unlike SVN you always have a "distributed" full repo. The one at apache will be the so called "origin" and well all flows will converge, but the one in my local machine will be another full repo (when is full synced) and the fork at github as well be valid...
But...although we don't need github, I must say that many people would like to use due to it's "pull request" feature, that , as other said is not in git and only available in github. Pull request is what make github so social, since nobody has any responsabilities. you only develop and share through pull request and if you (PPMC with full write access to the forked official repo) like the pull request you can integrate into the official repo. Github makes that extremely easy and funny and for that reason is why it's model is a big success in open source and all people wants to use it. 2012/8/20 Alex Harui <aha...@adobe.com> > Hi Carlos, > > Pardon my ignorance here, but I'm assuming that the main Apache Flex Git > repo will be at some apache.org URL. If that's the case, why would we > need > to continue to mirror the repo to GitHub? And why would we need GitHub > accounts to do our daily work on the Apache Flex repo? > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > -- 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
