Apache Flume is other project that is now on GIT: http://flume.apache.org/source.html
Here they started to see how to move http://apache.markmail.org/thread/fkkraooktzxelbr2 And they finaly get it so it's possbile! :) 2012/11/21 Carlos Rovira <carlos.rov...@codeoscopic.com> > Hi, > > although I, as all, would like the complete solution GIT-GITHUB, I'm with > you that better to win the first battle : switch from SVN to read/write > GIT. That's the basic idea and reduction of the task. > > @Omar, about Python, I'll try to search the way to workaround that since > I, as you are not a Python guy. Moreover, my way of thinking is that we are > here to code and make Flex evolve, and IMO if Apache has a Infra team we > should ask for help (and help them to get the switch done), but a > requeriment of "a pyhton guy to get the task done" should not be binding to > make this movement happen. We all have to take into account that we, in the > end does not have grants or privileges on the apache hardware. We are only > users, and as committers we can help to test and get the task done, but I > don't think we could get far beyond without a real commitment by someone > behind the infra's side. > > I think this is more a task to learn a lot how infra works, how they > expect, how are the real possibilities here (although that point I think we > already know a lot yet), and ask for help to make the switch, having > patience, and make a close monitoring to help this happen. > > So, wish me luck! :) > > > > > 2012/11/21 Omar Gonzalez <omarg.develo...@gmail.com> > >> On Wed, Nov 21, 2012 at 1:03 PM, Justin Mclean <jus...@classsoftware.com >> >wrote: >> >> > Hi, >> > >> > Would Is it easier to make progress if we remove github from the >> equation >> > for now and revisit? (And just keep the githib mirror as we do now) The >> > vote if I recall was to use git not github. >> > >> > Thanks, >> > Justin >> >> >> The mirrors to GitHub were really just an interim solution while we got a >> read/write Apache hosted Git repository. >> >> I would be perfectly happy with killing the GitHub mirrors if it meant we >> got a read/write Apache hosted Git repository. >> >> It would facilitate managing the Git patches as it would remove the step >> of >> having to deal with Pull Requests submitted via GitHub. >> >> I think its more important to have the read/write Git than it is to also >> have a GitHub mirror and support Pull Requests from GitHub. Even thought >> Pull Requests and Forking on GitHub would greatly improve workflows, >> specifically handling code reviews for code patches. We can do that in >> JIRA, but it wouldn't be as efficient as GitHub due to the lack of being >> able to comment on specific lines of code right in the repository browser >> viewer. Not to mention the ease with which you can integrate Pull Requests >> via the GitHub GUI. >> >> -omar >> > > > > -- > Carlos Rovira > Director de Tecnología > M: +34 607 22 60 05 > F: +34 912 35 57 77 > http://www.codeoscopic.com > http://www.directwriter.es > http://www.avant2.es > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
