You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jay D. McHugh" <ja...@gmail.com> on 2011/12/02 20:14:52 UTC
Re: Fwd: Accepting proposals regarding early git adoption
Is the idea for this to abandon SVN and move completely over to git?
Or is it just to add git as a way for folks to manage their local copies
of the source?
Jay
On 11/29/2011 03:22 PM, Kevan Miller wrote:
> Forwarding (with permission), in case there's interest within Geronimo community.
>
> --kevan
>
> Begin forwarded message:
>
>> From: Joe Schaefer<jo...@yahoo.com>
>> Subject: Accepting proposals regarding early git adoption
>> Date: November 28, 2011 8:28:17 AM EST
>> To: Apache Infrastructure<in...@apache.org>
>> Reply-To: Joe Schaefer<jo...@yahoo.com>
>>
>> While many of you are aware of the ongoing "experiment/alpha test"
>> with git hosting for CouchDB, you may not be aware of the recent
>> members@ discussion about git @ Apache, the result of which is to
>> solicit proposals here for projects interested in adopting git now,
>> rather than after the testing phase is over.
>>
>> Any such projects you participate in should write a brief and civil
>> proposal as to why we should select you for further git testing.
>> Proposals should include statements of interest in assisting with
>> the git hosting codebase and associated jira issues from named
>> individuals on the project.
>>
>> We'll allow the remainder of the week to collect proposals before
>> deciding on who gets to go next.
>>
>
Re: Accepting proposals regarding early git adoption
Posted by Mark Struberg <st...@yahoo.de>.
oops, accidentially pressed the send way too early ^^
should have been: "I agree with David..."
I'm an old git fan myself as many know, and we well also use GIT for DeltaSpike.
But for such modular systems like Geronimo SVN is still a much better fit imo.
LieGrue,
strub
----- Original Message -----
> From: Mark Struberg <st...@yahoo.de>
> To: "dev@geronimo.apache.org" <de...@geronimo.apache.org>
> Cc:
> Sent: Saturday, December 3, 2011 1:32 PM
> Subject: Re: Accepting proposals regarding early git adoption
>
> David PLEASE DONT SPLIT ALL INTO SINGLE GIT REPOS!
>
>
> This is a HUGE nightmare to maintain!
>
> You will NOT be able to just treat this nicely!
>
> Please go over and first read what I wrote on the OpenEJB dev list and what we
> wrote together on
> http://wiki.apache.org/couchdb/Git_At_Apache_Guide
>
> and especally on
>
> http://wiki.apache.org/couchdb/SVNvsGIT
>
> Trust me, you don't want to inependently maintain 350 git repos!
>
> There will (to my knowledge) be NO sane way to check out the project in one go
> anymore!
>
> You could certainly move all specs into one GIT repo, all of geronimo into
> another, etc but having too many independent repos is _really_ a nightmare for
> each developer!
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: David Jencks <da...@yahoo.com>
>> To: dev@geronimo.apache.org
>> Cc:
>> Sent: Friday, December 2, 2011 9:02 PM
>> Subject: Re: Accepting proposals regarding early git adoption
>>
>> Anyone can already use git locally, there are apache mirrors of most svn
>> projects and many project's committers expose a lot of work-in-progress
> on
>> github (e.g. karaf)
>>
>> See e.g. http://wiki.apache.org/general/GitAtApache
>>
>> This is asking for projects that would like to use git instead of svn for
> their
>> canonical apache repository. While I enthusiastically use git almost all
> the
>> time including for almost all my geronimo work I think geronimo is too
>> complicated to be a useful guinea pig for git at this point. I think it
> will
>> take a lot of thought and time to figure out how to divide up the geronimo
>> history into appropriately sized git projects. For instance:
>>
>> - each spec is separately releasable so it's a separate git project.
> Then
>> we need an aggretator project to build them all at once for convenience.
> Same
>> for bundles.
>> - the server code was originally under cvs at root and only later moved
> under
>> server. How will this history make it into git (this is probably solved
> already
>> but I haven't looked)
>>
>> thanks
>> david jencks
>>
>> On Dec 2, 2011, at 11:14 AM, Jay D. McHugh wrote:
>>
>>> Is the idea for this to abandon SVN and move completely over to git?
>>>
>>> Or is it just to add git as a way for folks to manage their local
> copies of
>> the source?
>>>
>>> Jay
>>>
>>> On 11/29/2011 03:22 PM, Kevan Miller wrote:
>>>> Forwarding (with permission), in case there's interest within
>> Geronimo community.
>>>>
>>>> --kevan
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: Joe Schaefer<jo...@yahoo.com>
>>>>> Subject: Accepting proposals regarding early git adoption
>>>>> Date: November 28, 2011 8:28:17 AM EST
>>>>> To: Apache Infrastructure<in...@apache.org>
>>>>> Reply-To: Joe Schaefer<jo...@yahoo.com>
>>>>>
>>>>> While many of you are aware of the ongoing
> "experiment/alpha
>> test"
>>>>> with git hosting for CouchDB, you may not be aware of the
> recent
>>>>> members@ discussion about git @ Apache, the result of which is
> to
>>>>> solicit proposals here for projects interested in adopting git
> now,
>>>>> rather than after the testing phase is over.
>>>>>
>>>>> Any such projects you participate in should write a brief and
> civil
>>>>> proposal as to why we should select you for further git
> testing.
>>>>> Proposals should include statements of interest in assisting
> with
>>>>> the git hosting codebase and associated jira issues from named
>>>>> individuals on the project.
>>>>>
>>>>> We'll allow the remainder of the week to collect proposals
>
>> before
>>>>> deciding on who gets to go next.
>>>>>
>>>>
>>
>
Re: Accepting proposals regarding early git adoption
Posted by Mark Struberg <st...@yahoo.de>.
Hi David!
Glad to discuss this and update my knowledge with your help!
I've tried to use git-submodules back a few years (sub 1.6). Back then it was pretty unusable.
Maybe something has changed which went under my radar, but imo the restrictions (from the back of my head) which we must check if they still apply are:
1.) each git-submodule is still an own GIT repo. There is imo no move possible out of the submodules without loosing history
2.) each git-submodule is still an own GIT repo. Maybe this got added lately, but they imo don't share git-remotes. All this needs to maintained manually. Is there a way now to update all the remotes for all contained git-submodules in 1 step?
3.) nested git-submodules are NOT nested on the disk in the object store! They are imo in fact independent GIT repos and there is just a kind of 'symlink' (gitlink resp via the .gitsubmodules: "the submodule support just stores the submodule repository location and
commit ID") to include them 'inplace'.
4.) you can clone/checkout 'nested' git-submodules since (1.6.4 or even later?) automatically, but you cannot push isn't?. This might have been fixed?
Also see here:
> git submodule add ~/git/$i $i
> NOTE: Do not use local URLs here if you plan to publish your superproject!
The reason is that you need to use a full git-remote URL here if you publish this. Now let's consider forking. As far as I've tested out, all the submodules _still_ point (git-remote origin) to the original repo ^^ Can you please verify that nowadays? This was quite a while back when I tried it.
I now found a hint that this maybe work now (though didn't test it myself):
> git clone --recursive URL
5.) The .gitsubmodules file is part or the working set (similar to .gitignore). Thus changing it (for adopting the remote URL) will change the sha1.
6.) by using git-submodules you are basically almost always working with a detached HEAD. Working with detached HEADs is pretty hard to get for git newbies.
7.) git-submodules makes working with branches sometimes pretty ugly. Because any directory content might not get updated.
Just create a sample project and try to work with it.
Or try to split Geronimo into smaller pieces with git-submodules and work with it. Would love to see that a few of those questions are non-issues today!
LieGrue,
strub
----- Original Message -----
> From: David Jencks <da...@yahoo.com>
> To: dev@geronimo.apache.org
> Cc:
> Sent: Saturday, December 3, 2011 7:07 PM
> Subject: Re: Accepting proposals regarding early git adoption
>
> Hi Mark,
>
> Your couchdb links don't seem to me to argue for or against what I was
> suggesting, other than pointing out that unless git project == releasable
> subproject you'll have an impedance mismatch, which is what I was trying to
> point out and avoid.
>
> The git docs http://book.git-scm.com/5_submodules.html certainly seem to
> indicate that my suggestion should work fine and when I suggested it on the
> aries list David Bosschart mentioned that JBoss has been using submodules in
> this way for a long time with great success.
>
> What's your evidence that submodules won't work for this?
>
Re: Accepting proposals regarding early git adoption
Posted by David Jencks <da...@yahoo.com>.
Hi Mark,
Your couchdb links don't seem to me to argue for or against what I was suggesting, other than pointing out that unless git project == releasable subproject you'll have an impedance mismatch, which is what I was trying to point out and avoid.
The git docs http://book.git-scm.com/5_submodules.html certainly seem to indicate that my suggestion should work fine and when I suggested it on the aries list David Bosschart mentioned that JBoss has been using submodules in this way for a long time with great success.
What's your evidence that submodules won't work for this?
thanks
david jencks
On Dec 3, 2011, at 4:32 AM, Mark Struberg wrote:
> David PLEASE DONT SPLIT ALL INTO SINGLE GIT REPOS!
>
>
> This is a HUGE nightmare to maintain!
>
> You will NOT be able to just treat this nicely!
>
> Please go over and first read what I wrote on the OpenEJB dev list and what we wrote together on
> http://wiki.apache.org/couchdb/Git_At_Apache_Guide
>
> and especally on
>
> http://wiki.apache.org/couchdb/SVNvsGIT
>
> Trust me, you don't want to inependently maintain 350 git repos!
>
> There will (to my knowledge) be NO sane way to check out the project in one go anymore!
>
> You could certainly move all specs into one GIT repo, all of geronimo into another, etc but having too many independent repos is _really_ a nightmare for each developer!
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: David Jencks <da...@yahoo.com>
>> To: dev@geronimo.apache.org
>> Cc:
>> Sent: Friday, December 2, 2011 9:02 PM
>> Subject: Re: Accepting proposals regarding early git adoption
>>
>> Anyone can already use git locally, there are apache mirrors of most svn
>> projects and many project's committers expose a lot of work-in-progress on
>> github (e.g. karaf)
>>
>> See e.g. http://wiki.apache.org/general/GitAtApache
>>
>> This is asking for projects that would like to use git instead of svn for their
>> canonical apache repository. While I enthusiastically use git almost all the
>> time including for almost all my geronimo work I think geronimo is too
>> complicated to be a useful guinea pig for git at this point. I think it will
>> take a lot of thought and time to figure out how to divide up the geronimo
>> history into appropriately sized git projects. For instance:
>>
>> - each spec is separately releasable so it's a separate git project. Then
>> we need an aggretator project to build them all at once for convenience. Same
>> for bundles.
>> - the server code was originally under cvs at root and only later moved under
>> server. How will this history make it into git (this is probably solved already
>> but I haven't looked)
>>
>> thanks
>> david jencks
>>
>> On Dec 2, 2011, at 11:14 AM, Jay D. McHugh wrote:
>>
>>> Is the idea for this to abandon SVN and move completely over to git?
>>>
>>> Or is it just to add git as a way for folks to manage their local copies of
>> the source?
>>>
>>> Jay
>>>
>>> On 11/29/2011 03:22 PM, Kevan Miller wrote:
>>>> Forwarding (with permission), in case there's interest within
>> Geronimo community.
>>>>
>>>> --kevan
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: Joe Schaefer<jo...@yahoo.com>
>>>>> Subject: Accepting proposals regarding early git adoption
>>>>> Date: November 28, 2011 8:28:17 AM EST
>>>>> To: Apache Infrastructure<in...@apache.org>
>>>>> Reply-To: Joe Schaefer<jo...@yahoo.com>
>>>>>
>>>>> While many of you are aware of the ongoing "experiment/alpha
>> test"
>>>>> with git hosting for CouchDB, you may not be aware of the recent
>>>>> members@ discussion about git @ Apache, the result of which is to
>>>>> solicit proposals here for projects interested in adopting git now,
>>>>> rather than after the testing phase is over.
>>>>>
>>>>> Any such projects you participate in should write a brief and civil
>>>>> proposal as to why we should select you for further git testing.
>>>>> Proposals should include statements of interest in assisting with
>>>>> the git hosting codebase and associated jira issues from named
>>>>> individuals on the project.
>>>>>
>>>>> We'll allow the remainder of the week to collect proposals
>> before
>>>>> deciding on who gets to go next.
>>>>>
>>>>
>>
Re: Accepting proposals regarding early git adoption
Posted by Mark Struberg <st...@yahoo.de>.
David PLEASE DONT SPLIT ALL INTO SINGLE GIT REPOS!
This is a HUGE nightmare to maintain!
You will NOT be able to just treat this nicely!
Please go over and first read what I wrote on the OpenEJB dev list and what we wrote together on
http://wiki.apache.org/couchdb/Git_At_Apache_Guide
and especally on
http://wiki.apache.org/couchdb/SVNvsGIT
Trust me, you don't want to inependently maintain 350 git repos!
There will (to my knowledge) be NO sane way to check out the project in one go anymore!
You could certainly move all specs into one GIT repo, all of geronimo into another, etc but having too many independent repos is _really_ a nightmare for each developer!
LieGrue,
strub
----- Original Message -----
> From: David Jencks <da...@yahoo.com>
> To: dev@geronimo.apache.org
> Cc:
> Sent: Friday, December 2, 2011 9:02 PM
> Subject: Re: Accepting proposals regarding early git adoption
>
> Anyone can already use git locally, there are apache mirrors of most svn
> projects and many project's committers expose a lot of work-in-progress on
> github (e.g. karaf)
>
> See e.g. http://wiki.apache.org/general/GitAtApache
>
> This is asking for projects that would like to use git instead of svn for their
> canonical apache repository. While I enthusiastically use git almost all the
> time including for almost all my geronimo work I think geronimo is too
> complicated to be a useful guinea pig for git at this point. I think it will
> take a lot of thought and time to figure out how to divide up the geronimo
> history into appropriately sized git projects. For instance:
>
> - each spec is separately releasable so it's a separate git project. Then
> we need an aggretator project to build them all at once for convenience. Same
> for bundles.
> - the server code was originally under cvs at root and only later moved under
> server. How will this history make it into git (this is probably solved already
> but I haven't looked)
>
> thanks
> david jencks
>
> On Dec 2, 2011, at 11:14 AM, Jay D. McHugh wrote:
>
>> Is the idea for this to abandon SVN and move completely over to git?
>>
>> Or is it just to add git as a way for folks to manage their local copies of
> the source?
>>
>> Jay
>>
>> On 11/29/2011 03:22 PM, Kevan Miller wrote:
>>> Forwarding (with permission), in case there's interest within
> Geronimo community.
>>>
>>> --kevan
>>>
>>> Begin forwarded message:
>>>
>>>> From: Joe Schaefer<jo...@yahoo.com>
>>>> Subject: Accepting proposals regarding early git adoption
>>>> Date: November 28, 2011 8:28:17 AM EST
>>>> To: Apache Infrastructure<in...@apache.org>
>>>> Reply-To: Joe Schaefer<jo...@yahoo.com>
>>>>
>>>> While many of you are aware of the ongoing "experiment/alpha
> test"
>>>> with git hosting for CouchDB, you may not be aware of the recent
>>>> members@ discussion about git @ Apache, the result of which is to
>>>> solicit proposals here for projects interested in adopting git now,
>>>> rather than after the testing phase is over.
>>>>
>>>> Any such projects you participate in should write a brief and civil
>>>> proposal as to why we should select you for further git testing.
>>>> Proposals should include statements of interest in assisting with
>>>> the git hosting codebase and associated jira issues from named
>>>> individuals on the project.
>>>>
>>>> We'll allow the remainder of the week to collect proposals
> before
>>>> deciding on who gets to go next.
>>>>
>>>
>
Re: Accepting proposals regarding early git adoption
Posted by David Jencks <da...@yahoo.com>.
Anyone can already use git locally, there are apache mirrors of most svn projects and many project's committers expose a lot of work-in-progress on github (e.g. karaf)
See e.g. http://wiki.apache.org/general/GitAtApache
This is asking for projects that would like to use git instead of svn for their canonical apache repository. While I enthusiastically use git almost all the time including for almost all my geronimo work I think geronimo is too complicated to be a useful guinea pig for git at this point. I think it will take a lot of thought and time to figure out how to divide up the geronimo history into appropriately sized git projects. For instance:
- each spec is separately releasable so it's a separate git project. Then we need an aggretator project to build them all at once for convenience. Same for bundles.
- the server code was originally under cvs at root and only later moved under server. How will this history make it into git (this is probably solved already but I haven't looked)
thanks
david jencks
On Dec 2, 2011, at 11:14 AM, Jay D. McHugh wrote:
> Is the idea for this to abandon SVN and move completely over to git?
>
> Or is it just to add git as a way for folks to manage their local copies of the source?
>
> Jay
>
> On 11/29/2011 03:22 PM, Kevan Miller wrote:
>> Forwarding (with permission), in case there's interest within Geronimo community.
>>
>> --kevan
>>
>> Begin forwarded message:
>>
>>> From: Joe Schaefer<jo...@yahoo.com>
>>> Subject: Accepting proposals regarding early git adoption
>>> Date: November 28, 2011 8:28:17 AM EST
>>> To: Apache Infrastructure<in...@apache.org>
>>> Reply-To: Joe Schaefer<jo...@yahoo.com>
>>>
>>> While many of you are aware of the ongoing "experiment/alpha test"
>>> with git hosting for CouchDB, you may not be aware of the recent
>>> members@ discussion about git @ Apache, the result of which is to
>>> solicit proposals here for projects interested in adopting git now,
>>> rather than after the testing phase is over.
>>>
>>> Any such projects you participate in should write a brief and civil
>>> proposal as to why we should select you for further git testing.
>>> Proposals should include statements of interest in assisting with
>>> the git hosting codebase and associated jira issues from named
>>> individuals on the project.
>>>
>>> We'll allow the remainder of the week to collect proposals before
>>> deciding on who gets to go next.
>>>
>>