You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Enis Soztutar <en...@gmail.com> on 2010/09/30 14:02:05 UTC

Podling to use native git

Hi,

In the preparation phase for the recent Gora podling, I realized that the
code needs be restructured to subversion layout. However, most of the
developers here prefer the git way and will never use subversion except for
committing the patches. So, I want to ask :

- Does any other podling use git-only workflow. If so, did your project uses
svn trunk/tags/branches layout?
- I know that there was some discussion at infra-dev about native git
repositories. Can we volunteer to be one?
- The main Apache repository is subversion. But can we somehow skip it and
directly use git.apache.org?

Of course some of these questions should be asked at infra-dev, but I wanted
to know if anyone has any XP with this.

Thanks,
Enis

Re: Podling to use native git

Posted by Upayavira <uv...@odoko.co.uk>.
On Thu, 2010-09-30 at 15:02 +0300, Enis Soztutar wrote: 
> Hi,
> 
> In the preparation phase for the recent Gora podling, I realized that the
> code needs be restructured to subversion layout. However, most of the
> developers here prefer the git way and will never use subversion except for
> committing the patches. So, I want to ask :
> 
> - Does any other podling use git-only workflow. If so, did your project uses
> svn trunk/tags/branches layout?
> - I know that there was some discussion at infra-dev about native git
> repositories. Can we volunteer to be one?
> - The main Apache repository is subversion. But can we somehow skip it and
> directly use git.apache.org?
> 
> Of course some of these questions should be asked at infra-dev, but I wanted
> to know if anyone has any XP with this.

Right now, Apache does not support native git repositories. SVN or SVN
with git-svn are your choices.

There are discussions ongoing to explore what might be involved to bring
git to the ASF as a principal repository, but there's going to be a lot
of work to do there, and it is not going to be immediate. 

Upayavira



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Podling to use native git

Posted by Enis Soztutar <en...@gmail.com>.
Hi,

On Fri, Oct 1, 2010 at 12:23 PM, Bertrand Delacretaz <bdelacretaz@apache.org
> wrote:

> Hi,
>
> On Thu, Sep 30, 2010 at 2:02 PM, Enis Soztutar <en...@gmail.com>
> wrote:
> > ..In the preparation phase for the recent Gora podling, I realized that
> the
> > code needs be restructured to subversion layout. However, most of the
> > developers here prefer the git way and will never use subversion except
> for
> > committing the patches...
>
> Just a word of caution regarding incubation: if this means this
> podling's developers will work outside of Apache and just drop code in
> svn from time to time, Apache might not be the right place for your
> guys at this time. Things have to happen on your dev list and in svn
> if you want to be part of Apache, in order for a community to form
> around those channels.
>

Thanks for bringing that up. But of course it would not be the case. As
stated at our proposal,
we very much believe in the Apache way of development. Actually, all of the
initial committers
are ASF committers for other projects. So no worry there.

Enis


>
> We've had some projects realize way too late that the Apache way of
> working was not for them - if that's the case for you guys, better
> fail early.
>
> Volunteering to help improve things is great, of course. I just wanted
> to point out that the above statement sounds alarming to me.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Podling to use native git

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Guys,

As the project's champion I'll work with the rest of the mentors and PPMC members to make sure we are moving forward in the Apache Way.

Cheers,
Chris



On 10/1/10 2:23 AM, "Bertrand Delacretaz" <bd...@apache.org> wrote:

Hi,

On Thu, Sep 30, 2010 at 2:02 PM, Enis Soztutar <en...@gmail.com> wrote:
> ..In the preparation phase for the recent Gora podling, I realized that the
> code needs be restructured to subversion layout. However, most of the
> developers here prefer the git way and will never use subversion except for
> committing the patches...

Just a word of caution regarding incubation: if this means this
podling's developers will work outside of Apache and just drop code in
svn from time to time, Apache might not be the right place for your
guys at this time. Things have to happen on your dev list and in svn
if you want to be part of Apache, in order for a community to form
around those channels.

We've had some projects realize way too late that the Apache way of
working was not for them - if that's the case for you guys, better
fail early.

Volunteering to help improve things is great, of course. I just wanted
to point out that the above statement sounds alarming to me.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org




++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: Podling to use native git

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,

On Thu, Sep 30, 2010 at 2:02 PM, Enis Soztutar <en...@gmail.com> wrote:
> ..In the preparation phase for the recent Gora podling, I realized that the
> code needs be restructured to subversion layout. However, most of the
> developers here prefer the git way and will never use subversion except for
> committing the patches...

Just a word of caution regarding incubation: if this means this
podling's developers will work outside of Apache and just drop code in
svn from time to time, Apache might not be the right place for your
guys at this time. Things have to happen on your dev list and in svn
if you want to be part of Apache, in order for a community to form
around those channels.

We've had some projects realize way too late that the Apache way of
working was not for them - if that's the case for you guys, better
fail early.

Volunteering to help improve things is great, of course. I just wanted
to point out that the above statement sounds alarming to me.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Podling to use native git

Posted by Guillaume Nodet <gn...@gmail.com>.
On Fri, Oct 1, 2010 at 09:44, Gav... <ga...@16degrees.com.au> wrote:

>
>
> > -----Original Message-----
> > From: Guillaume Nodet [mailto:gnodet@gmail.com]
> > Sent: Friday, 1 October 2010 5:11 PM
> > To: general@incubator.apache.org
> > Subject: Re: Podling to use native git
> >
> > I do agree with you.   I don't really get this argument either.
> >
> > But in the meantime, you need to use an svn backend, and ask for a git
> > mirror.     You can then fork / merge at github the way you want, merge
> > back
> > into trunk and git svn dcommit from there.
> >
> > I think it's really worse, as branches aren't maintained anymore in the
> > apache svn area,
>
> What's wrong with 'git tag' ??
>

What I'm saying is that having to maintain some branches at github outside
of svn in git is not the best thing.   But that's really the only option we
have here.


>
>
> > but that's what we need to live with until git can be
> > properly supported at Apache.
>
> It will be a while.
>
>
> Gav...
>
> >
> > On Fri, Oct 1, 2010 at 08:49, Mark Struberg <st...@yahoo.de> wrote:
> >
> > > Hmm, to be honest, I don't see this argument. Because you can also
> > use a
> > > centralised model with GIT.
> > >
> > > Also, the main benefit of GIT is not only that you can do offline
> > commits,
> > > but mostly that it's sooo much easier to merge!
> > > I had a merge hell with my colleague in the company this week. He
> > kept a
> > > SVN feature branch for only one week and merging his feature branch
> > into the
> > > trunk (team with 10 developers) did cost us a whole day...
> > >
> > > The reason is that SVN applies an end to end diff while git aims to
> > merge
> > > by walking the commit tree of the branch and applying each commit
> > > separately.
> > >
> > > GIT even supports signing off commits. So each committer who pushes
> > to the
> > > central repo 'signs' that the contribution is ASL licensed.
> > >
> > > LieGrue,
> > > stru
> > >
> > > --- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:
> > >
> > > > From: Noel J. Bergman <no...@devtech.com>
> > > > Subject: RE: Podling to use native git
> > > > To: general@incubator.apache.org
> > > > Date: Thursday, September 30, 2010, 11:13 PM
> > > > > Does any other podling use
> > > > git-only workflow.
> > > >
> > > > No ASF project is permitted to use git-only.  And the
> > > > typical git workflow is part of the problem.  We
> > > > strongly believe in a single, central, repository as part of
> > > > the process of community building.  The git model is
> > > > better suited to disparate groups partially sharing a
> > > > codebase.
> > > >
> > > > Fundamentally, we WANT people working in a central, shared,
> > > > repository.
> > > >
> > > > If/when the ASF allows git as a technology, you can expect
> > > > that the workflow will be an ASF workflow.  And once
> > > > Greg gets offline commmit working with SVN, I suspect that
> > > > it will be harder to push for git.
> > > >
> > > >     --- Noel
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------------------
> > --
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

RE: Podling to use native git

Posted by "Gav..." <ga...@16degrees.com.au>.

> -----Original Message-----
> From: Guillaume Nodet [mailto:gnodet@gmail.com]
> Sent: Friday, 1 October 2010 5:11 PM
> To: general@incubator.apache.org
> Subject: Re: Podling to use native git
> 
> I do agree with you.   I don't really get this argument either.
> 
> But in the meantime, you need to use an svn backend, and ask for a git
> mirror.     You can then fork / merge at github the way you want, merge
> back
> into trunk and git svn dcommit from there.
> 
> I think it's really worse, as branches aren't maintained anymore in the
> apache svn area,

What's wrong with 'git tag' ??


> but that's what we need to live with until git can be
> properly supported at Apache.

It will be a while.


Gav...

> 
> On Fri, Oct 1, 2010 at 08:49, Mark Struberg <st...@yahoo.de> wrote:
> 
> > Hmm, to be honest, I don't see this argument. Because you can also
> use a
> > centralised model with GIT.
> >
> > Also, the main benefit of GIT is not only that you can do offline
> commits,
> > but mostly that it's sooo much easier to merge!
> > I had a merge hell with my colleague in the company this week. He
> kept a
> > SVN feature branch for only one week and merging his feature branch
> into the
> > trunk (team with 10 developers) did cost us a whole day...
> >
> > The reason is that SVN applies an end to end diff while git aims to
> merge
> > by walking the commit tree of the branch and applying each commit
> > separately.
> >
> > GIT even supports signing off commits. So each committer who pushes
> to the
> > central repo 'signs' that the contribution is ASL licensed.
> >
> > LieGrue,
> > stru
> >
> > --- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:
> >
> > > From: Noel J. Bergman <no...@devtech.com>
> > > Subject: RE: Podling to use native git
> > > To: general@incubator.apache.org
> > > Date: Thursday, September 30, 2010, 11:13 PM
> > > > Does any other podling use
> > > git-only workflow.
> > >
> > > No ASF project is permitted to use git-only.  And the
> > > typical git workflow is part of the problem.  We
> > > strongly believe in a single, central, repository as part of
> > > the process of community building.  The git model is
> > > better suited to disparate groups partially sharing a
> > > codebase.
> > >
> > > Fundamentally, we WANT people working in a central, shared,
> > > repository.
> > >
> > > If/when the ASF allows git as a technology, you can expect
> > > that the workflow will be an ASF workflow.  And once
> > > Greg gets offline commmit working with SVN, I suspect that
> > > it will be harder to push for git.
> > >
> > >     --- Noel
> > >
> > >
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
> 
> 
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Podling to use native git

Posted by Guillaume Nodet <gn...@gmail.com>.
I do agree with you.   I don't really get this argument either.

But in the meantime, you need to use an svn backend, and ask for a git
mirror.     You can then fork / merge at github the way you want, merge back
into trunk and git svn dcommit from there.

I think it's really worse, as branches aren't maintained anymore in the
apache svn area, but that's what we need to live with until git can be
properly supported at Apache.

On Fri, Oct 1, 2010 at 08:49, Mark Struberg <st...@yahoo.de> wrote:

> Hmm, to be honest, I don't see this argument. Because you can also use a
> centralised model with GIT.
>
> Also, the main benefit of GIT is not only that you can do offline commits,
> but mostly that it's sooo much easier to merge!
> I had a merge hell with my colleague in the company this week. He kept a
> SVN feature branch for only one week and merging his feature branch into the
> trunk (team with 10 developers) did cost us a whole day...
>
> The reason is that SVN applies an end to end diff while git aims to merge
> by walking the commit tree of the branch and applying each commit
> separately.
>
> GIT even supports signing off commits. So each committer who pushes to the
> central repo 'signs' that the contribution is ASL licensed.
>
> LieGrue,
> stru
>
> --- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:
>
> > From: Noel J. Bergman <no...@devtech.com>
> > Subject: RE: Podling to use native git
> > To: general@incubator.apache.org
> > Date: Thursday, September 30, 2010, 11:13 PM
> > > Does any other podling use
> > git-only workflow.
> >
> > No ASF project is permitted to use git-only.  And the
> > typical git workflow is part of the problem.  We
> > strongly believe in a single, central, repository as part of
> > the process of community building.  The git model is
> > better suited to disparate groups partially sharing a
> > codebase.
> >
> > Fundamentally, we WANT people working in a central, shared,
> > repository.
> >
> > If/when the ASF allows git as a technology, you can expect
> > that the workflow will be an ASF workflow.  And once
> > Greg gets offline commmit working with SVN, I suspect that
> > it will be harder to push for git.
> >
> >     --- Noel
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

RE: Podling to use native git

Posted by Mark Struberg <st...@yahoo.de>.
Hmm, to be honest, I don't see this argument. Because you can also use a centralised model with GIT.

Also, the main benefit of GIT is not only that you can do offline commits, but mostly that it's sooo much easier to merge!
I had a merge hell with my colleague in the company this week. He kept a SVN feature branch for only one week and merging his feature branch into the trunk (team with 10 developers) did cost us a whole day...

The reason is that SVN applies an end to end diff while git aims to merge by walking the commit tree of the branch and applying each commit separately.

GIT even supports signing off commits. So each committer who pushes to the central repo 'signs' that the contribution is ASL licensed.

LieGrue,
stru

--- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:

> From: Noel J. Bergman <no...@devtech.com>
> Subject: RE: Podling to use native git
> To: general@incubator.apache.org
> Date: Thursday, September 30, 2010, 11:13 PM
> > Does any other podling use
> git-only workflow.
> 
> No ASF project is permitted to use git-only.  And the
> typical git workflow is part of the problem.  We
> strongly believe in a single, central, repository as part of
> the process of community building.  The git model is
> better suited to disparate groups partially sharing a
> codebase.
> 
> Fundamentally, we WANT people working in a central, shared,
> repository.
> 
> If/when the ASF allows git as a technology, you can expect
> that the workflow will be an ASF workflow.  And once
> Greg gets offline commmit working with SVN, I suspect that
> it will be harder to push for git.
> 
>     --- Noel
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


RE: Podling to use native git

Posted by "Noel J. Bergman" <no...@devtech.com>.
> Does any other podling use git-only workflow.

No ASF project is permitted to use git-only.  And the typical git workflow is part of the problem.  We strongly believe in a single, central, repository as part of the process of community building.  The git model is better suited to disparate groups partially sharing a codebase.

Fundamentally, we WANT people working in a central, shared, repository.

If/when the ASF allows git as a technology, you can expect that the workflow will be an ASF workflow.  And once Greg gets offline commmit working with SVN, I suspect that it will be harder to push for git.

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org