[TYPO3-dev] Plan to migrate extensions from SVN to GIT ?

[Steffen Gebert]

Hi,

thanks for your initiative!

 > I believe it has little to do with forge server as git
 > repositories would be hosted on git server (obviously) and we don't
 > necessarily have to integrate it on forge right away.

Sorry, offering git in a large scale requires automation for me - this 
esp. includes forge. I know that you're talking of mirrors only. But I 
don't want to put so much time in that thing, when lots of other 
important things are open. And man-power is definitely a limiting factor 
(so thanks again for offering your help!)

 > 3. cron job on git.typo3.org to synchronize (one way only)

IMHO git.typo3.org should only host repositories that are not just 
mirrors. Thing is also that git.t3o is run by Gerrit, which would make 
the system a bit more complex.
Having it as an own server for really mirroring SVN extensions sounds 
IMHO better.

It's personal opinion, we would have to discuss this in the Server Team 
and I'm open for more community feedback. If there is interest, we can 
of course offer you the server infrastructure.

Kind regards
Steffen

-- 
Steffen Gebert
TYPO3 v4 Core Team Member
TYPO3 Server Administration Team Member

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

On 20.12.11 03:53, Adrien Crivelli wrote:
> Hi
>
> I am not in such a hurry for git and you seem interested in having
> (readonly) git mirrors for svn extensions. So I was wondering if I could
> help with that. I believe it has little to do with forge server as git
> repositories would be hosted on git server (obviously) and we don't
> necessarily have to integrate it on forge right away.
>
> I think we would have three cases:
>
>     - svn only: for low-interest/deprecated extensions, so we don't clutter
>     git server with old things (nothing to do)
>     - svn + readonly git
>     - git only: if extension team wants to (nothing to do)
>
> So what we would need to do is
>
>     1. define a list of extension to mirror
>     2. setup git-svn clones on git.typo3.org
>     3. cron job on git.typo3.org to synchronize (one way only)
>
> Basically it is something that I (and probably other people) will need to
> have in a few weeks (months?). So instead of doing that for myself only (on
> my own server), I would be willing to do that for everybody (on
> git.typo3.org).
>
> What do you think ? Do we really have to wait for forge hardware upgrade ?
>
> Regards,
>
> Adrien
>
>
>
> On 8 December 2011 19:09, Steffen Gebert<steffen.gebert at typo3.org>  wrote:
>
>> Hi,
>>
>>
>>   Is there any plan to migrate all existing extensions from SVN to GIT ?
>>>
>> well, I would say there is of course the idea, to do that. Not to force
>> people immediately, but at least to offer both VCS for some period.
>>
>> ATM migrations to Git have to be done manually. This has to be automatized
>> and also when creating a new project, people have to be able to choose
>> between SVN and Git for forge projects.
>>
>> However, before we (Server Admin Team) change anything in forge, we wanted
>> to migrate it to a way faster server first. This move has to take place
>> this year. So let's see, what next year brings.
>>
>> Having all extensions mirrored in Git would be also a nice idea.. however,
>> I don't know if it leads to additional confusion.
>>
>> So for the moment, I see no other option than creating an own mirror -
>> either on an own git server or on github.
>>
>> Kind regards
>> Steffen
>>
>> --
>> Steffen Gebert
>> TYPO3 v4 Core Team Member
>> TYPO3 Server Administration Team Member
>>
>> TYPO3 .... inspiring people to share!
>> Get involved: http://typo3.org
>>
>> ______________________________**_________________
>> TYPO3-dev mailing list
>> TYPO3-dev at lists.typo3.org
>> http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-dev<http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev>
>>