"Using the native github capabilitry of svn mirroring for pubsvn": I tried, but so far there was little use for it.
In short:
. ppl can already connect to github using svn without passing by pubsvn
. the "svn access" capability of github is limited, not all svn commands work as they should
. which makes it a hassle to do an svn sync of github to pubsvnfor later exposing that svn repo in ro mode as it was done before (mirroring the ezp svn repo): there would be no complete history / blame support, etc...
. there are other tools that mirror a git repo into an svn one, but I did not consider spending time on testing them - after all we want all devs to use git in the first place, right? ;-) Also an "exact" replica might not even be doable because of differences in the underlying systems...
Principal Consultant International Business
Member of the Community Project Board
"Using the native github capabilitry of svn mirroring for pubsvn": I tried, but so far there was little use for it.
In short:
. ppl can already connect to github using svn without passing by pubsvn
. the "svn access" capability of github is limited, not all svn commands work as they should
"
Hi Gaetano,
Do you know which SVN commands are not working with this setup ? If these are rarely used ones, we may want to use github's native functionality for this, this will dramatically reduce the amount of setup & maintenance work.
Cheers,
--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board
@nico: I do not have the exact list of commands that do not work - I just tried using tortoisesvn to browse the svn 'native' version of github and it was simply not good enough for real work.
I agree that pointing end users to github's native svn interface will save time and money.
I do not see a lot of added value in setting up an svn mirror. Is it just for the sake of having the old svn urls working again? Any svn die-hard can use github's version.
Otoh real added value can be found in setting up multiple code browsing and cross-referencing tools: every dev probably has his favorite one, and some might be better than others at parsing php. An interesting new entry on the list of candidates: opengrok - http://hub.opensolaris.org/bin/view/Project+opengrok/WebHome. It needs a jvm to run :-( and is based on exhuberant ctags for language parsing. It supports git natively.
Principal Consultant International Business
Member of the Community Project Board