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

Mon Jan 2 12:28:06 CET 2012

Dear Adrien,

 > When you say "automation", what are you thinking about ?
yes, on the surface it's just a checkbox (or maybe two select boxes):
[X] Git  [ ] Subversion
and
[X] Review workflow (Gerrit)  [ ] direct access

Below the surface the whole processes of creating the Git repository in 
Gerrit, setting up the access permissions there (reviews yes/no), 
creating a clone on forge, etc. have to be implemented.
This has to be triggered through redmine, not through as being logged in 
via SSH.

Peter Niederlag already told me that he wants to work on our Gerrit the 
next few weeks. This means a) updating to latest Gerrit version 2.2.x, 
which introduced a lot of changes (review data isn't in a database 
anymore, but directly in the git repository). This already means lot of 
adjustments to the script we currently have in use to create new git 
repositories. Step b) would then be to give forge users the ability to 
create and configure such git repos. As we finally moved forge last week 
to a new server (which was the most challenging project in the Server 
team this year), we are now finally at the point of time, when we can 
start thinking about doing more improvements to forge. So I guess/hope 
that a few interested people will start working the next weeks.

 > As for the server I thought git.typo3.org would be a nice choice to avoid
 > spreading resources (and freeze URL once and for all if extension 
team want
 > to permanently move to git later on).
Okay, it sounds nice. Also the idea of keeping the URL. But I'm unsure 
about putting another 500 - partly inactive projects - into Gerrit (but 
we have to, if we use git.typo3.org).
I would say, if you want to set it up and maintain a mirror for all svn 
repositories, we can provide you the resources (=server) and some help. 
But be warned: All extensions are in one repository. For git we would 
need one repository per extension.

Steffen

On 02.01.12 05:42, Adrien Crivelli wrote:
> Hello,
>
> When you say "automation", what are you thinking about ? Some kind of
> checkbox in http://forge.typo3.org/projects/extension-myextension/settingsto
> enable git mirror ? Or something else ?
>
> As for the server I thought git.typo3.org would be a nice choice to avoid
> spreading resources (and freeze URL once and for all if extension team want
> to permanently move to git later on). But I have no idea about gerrit and
> how it manages git. So I guess I'd follow your advice for that part.
>
>
> Happy new year,
>
> Adrien
>
> On 20 December 2011 16:57, Steffen Gebert<steffen.gebert at typo3.org>  wrote:
>
>> 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<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>
>>>> **<http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-dev<http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev>
>>>> **>
>>>>
>>>>
>>
>> ______________________________**_________________
>> 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>
>>

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