Hi Adrian, Thanks for the answer. Your link didn't work, but I found it here: http://permalink.gmane.org/gmane.comp.php.oxid.general/1697
Here's the excerpt: > Hello Adrian, > > do you know the word "You can't catch two birds with one stone"? :-)) > > Basically, OXID projects is a totally different topic to moving the core to > GitHub. Anyway, we already have that in our back heads. Maybe a good first > step would be to use GitHub as a mirror instead of the public SVN where we > mirror the development SVN now on a nightly basis: > http://svn.oxid-esales.com/ > > But also this step needs evaluation, thinking about the processes and some > effort within the infrastructure. That's why I can't promise any time frame > for that. > > Thanks for your idea anyway :-) > > Marco What a shame. I think OXID are missing out on a lot of 'free development' from the community. It doesn't even need to be GitHub. A standalone git server (just git, not github) over HTTP would do just fine. I assume that would get around any licensing issues. They could use public branches for CE and private clones for PE/EE. @Marco what do you think? Have there been any further developments on this? Dave Am 16.07.12 16:56, schrieb Adrian Kirchner: > Hi Dave, > > I asked for Github migration in april this year and I think Marcos > answer is still the last official answer to this topic: > http://www.mail-archive.com/[email protected]/msg01602.html > > > > Best regards > > Adrian > _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
