You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by James Taylor <ja...@apache.org> on 2014/01/31 18:47:37 UTC
best development methodology for Apache git?
The Phoenix project has recently come into incubation from it's former life
as a Github project. I believe other projects have made this same
transition, so I'm looking to get some advice from them. What's the best
development methodology folks have found for collaborative development when
your source of truth is an Apache git repo? Something like the Github model
that combines a) the ability for managing branches and visually reviewing
patches and b) a means to gate commits against the single source of truth,
the git repo.
Gerrit meets this requirement and based on INFRA-2205 used to be setup. If
that's not an option, what have folks found that works well?
Thanks,
James
Fwd: Re: best development methodology for Apache git?
Posted by Marlon Pierce <ma...@iu.edu>.
Possibly interesting discussion on git from the incubator list--
-------- Original Message --------
Subject: Re: best development methodology for Apache git?
Date: Mon, 3 Feb 2014 09:39:12 -0500
From: Jake Farrell <jf...@apache.org>
Reply-To: general@incubator.apache.org, jfarrell@apache.org
To: general@incubator.apache.org <ge...@incubator.apache.org>
Hey Sergio
The Apache mirrors on Github are by request and run off from git.apache.org.
Anyone wanting to have a svn or git project mirrored needs to submit an
infra ticket and it can get setup.
As for the Github workflows that are starting to be used, I am not a
proponent of them. These workflows are not ideal as they repositories are
not under any Asf control and infra can not help if there are any issues,
its up to the project to take care of its own. Also with the JClouds and
now Usergrid projects using this flow adds a lot of overhead for
initial contributions as they have in the workflow the requirement to
ensure an ICLA are on file for the contributor. Most committers do not have
access to see the status of this. Also since these projects are not working
directly against the primary repository it is up to them to ensure that
committers are the only ones submitting code to the primary repository and
then syncing that code at some point over to the ASF repositories in order
to make a release.
If we are not providing the right tooling for projects and they are seeking
outside means then I would love to work and help make the correct tools
available to make workflows easier and ensure security and policies are
being met.
-Jake
On Mon, Feb 3, 2014 at 5:10 AM, Sergio Fernández <
sergio.fernandez@salzburgresearch.at> wrote:
> Hi,
>
> On 03/02/14 10:42, Bertrand Delacretaz wrote:
>
>> On Fri, Jan 31, 2014 at 6:47 PM, James Taylor <ja...@apache.org>
>> wrote:
>>
>>> The Phoenix project has recently come into incubation from it's former
>>> life
>>> as a Github project. I believe other projects have made this same
>>> transition, so I'm looking to get some advice from them...
>>>
>>
>> CouchDB has documented their Git workflow at
>> http://wiki.apache.org/couchdb/ContributorWorkflow
>>
>
> In Marmotta we adopted a Gitflow as workflow, you can find the
> documentation at the web site:
>
> http://marmotta.apache.org/development.html#Source_code
>
> But we'd be really interested on extend that to github-like pull requests,
> in order to make easier to get contributions from new people. I think
> that's what James is asking, and what jclouds has implemented somehow. But
> I miss some more details to actually know how they do it, specially taking
> into account that many repos at github are not properly synced.
>
> Cheers,
>
> --
> Sergio Fernández
> Senior Researcher
> Knowledge and Media Technologies
> Salzburg Research Forschungsgesellschaft mbH
> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> T: +43 662 2288 318 | M: +43 660 2747 925
> sergio.fernandez@salzburgresearch.at
> http://www.salzburgresearch.at
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: best development methodology for Apache git?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Tue, Feb 4, 2014 at 9:35 AM, Ignasi Barrera <ig...@gmail.com> wrote:
> ...We're working on it, our apologies for the confusion the old links may
> cause!...
Ok - it would be good add those new links and deprecation warning at
the top of the page that I mentioned!
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: best development methodology for Apache git?
Posted by Ignasi Barrera <ig...@gmail.com>.
Hi Bertrand,
Actually that link is deprecated. We point all contributors/commiters to
the following guides:
https://wiki.apache.org/jclouds/How%20to%20Contribute
https://wiki.apache.org/jclouds/Committers%20Guide
We have a re-branding of the site in progress, and all these obsolete links
are being fixed and all documentation is being made more accessible.
We're working on it, our apologies for the confusion the old links may
cause!
Ignasi
On 4 February 2014 09:08, Bertrand Delacretaz <bd...@apache.org>wrote:
> On Tue, Feb 4, 2014 at 8:13 AM, Ignasi Barrera <na...@apache.org> wrote:
> > ...Just wanted to clarify this, as I think this approach doesn't
> introduce
> > overhead to commiters/contributors and respects the ASF workflow...
>
> Thanks for this, IIUC this is described at
>
> http://jclouds.apache.org/documentation/devguides/contributing-to-jclouds/
>
> which looks quite good to me, as you indicate having your canonical
> repository on Apache infrastructure and cutting releases from that is
> a requirement.
>
> There's two things that could be added IMO:
>
> 1) Apache accepts only voluntary contributions, your PMC needs to be
> able to demonstrate that every contribution is intentional. For this
> it might be good to have a phrase like "by creating a pull request
> against our github repository you indicate your willingness to
> contribute your code to Apache jclouds" on that page and/or in the
> top-level README files of your modules.
>
> 2) Contributors should be made aware of
> http://www.apache.org/licenses/icla.txt and
> http://www.apache.org/licenses/cla-corporate.txt, and the PMC should
> ask for an iCLA for "substantial contributions", whatever that means.
> http://db.apache.org/derby/faq.html#derby_icla is a reasonable way to
> explain that IMO, I'd just add a mention of the CCLA which Apache does
> not require but which people who are employees often need.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: best development methodology for Apache git?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Feb 4, 2014 at 8:13 AM, Ignasi Barrera <na...@apache.org> wrote:
> ...Just wanted to clarify this, as I think this approach doesn't introduce
> overhead to commiters/contributors and respects the ASF workflow...
Thanks for this, IIUC this is described at
http://jclouds.apache.org/documentation/devguides/contributing-to-jclouds/
which looks quite good to me, as you indicate having your canonical
repository on Apache infrastructure and cutting releases from that is
a requirement.
There's two things that could be added IMO:
1) Apache accepts only voluntary contributions, your PMC needs to be
able to demonstrate that every contribution is intentional. For this
it might be good to have a phrase like "by creating a pull request
against our github repository you indicate your willingness to
contribute your code to Apache jclouds" on that page and/or in the
top-level README files of your modules.
2) Contributors should be made aware of
http://www.apache.org/licenses/icla.txt and
http://www.apache.org/licenses/cla-corporate.txt, and the PMC should
ask for an iCLA for "substantial contributions", whatever that means.
http://db.apache.org/derby/faq.html#derby_icla is a reasonable way to
explain that IMO, I'd just add a mention of the CCLA which Apache does
not require but which people who are employees often need.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: best development methodology for Apache git?
Posted by Ignasi Barrera <na...@apache.org>.
Just wanted to point out that in jclouds we only use GitHub for the code
reviews. We don't follow the entire pull request workflow and we actually
use the ASF repos as our primary source of code.
Contributors submit pull requests and code review happen in GitHub. Once
the patch is ready to be merged, the commiters push it to the ASF git repo.
We never push code anywhere but the ASF repos. Changes to the GitHub ones
get there only when mirrored by the mirror jobs.
Just wanted to clarify this, as I think this approach doesn't introduce
overhead to commiters/contributors and respects the ASF workflow. GitHub is
just the place where code reviews happen, and all the code is always pushed
to the ASF repos; they are the only source of truth and we only work
directly with them.
Ignasi
El 03/02/2014 19:34, "Andrew Purtell" <ap...@apache.org> escribió:
> On the question of tooling, that brings us back to James' inquiry about
> having infrastructure that can emulate the GitHub pull request workflow in
> house:
>
> > Something like the Github model that combines a) the ability for managing
> branches and visually reviewing patches and b) a means to gate commits
> against the single source of truth, the git repo. Gerrit meets this
> requirement and based on INFRA-2205 used to be setup.
>
> What Gerritt and GitHub pull requests have in common is contributors submit
> change requests as pushes of a new branch to a git remote (quite convenient
> and natural for a developer using git already locally), this branch can be
> updated incrementally during the review process, and there is a nice GUI
> for line by line code inspection, comment, and discussion, including email
> integration. (James' point "a")
>
> Gerritt can also support workflows where human reviewers and a QA bot can
> collaborate to gate the commit of a change candidate, where the actual
> commit to the project master branch is done by the review tool after
> established process requirements are all met. The Phoenix guys have
> indicated this idea is attractive to them. (James' point "b")
>
>
> On Monday, February 3, 2014, Jake Farrell <jf...@apache.org> wrote:
>
> > Hey Sergio
> > The Apache mirrors on Github are by request and run off from
> > git.apache.org.
> > Anyone wanting to have a svn or git project mirrored needs to submit an
> > infra ticket and it can get setup.
> >
> > As for the Github workflows that are starting to be used, I am not a
> > proponent of them. These workflows are not ideal as they repositories are
> > not under any Asf control and infra can not help if there are any issues,
> > its up to the project to take care of its own. Also with the JClouds and
> > now Usergrid projects using this flow adds a lot of overhead for
> > initial contributions as they have in the workflow the requirement to
> > ensure an ICLA are on file for the contributor. Most committers do not
> have
> > access to see the status of this. Also since these projects are not
> working
> > directly against the primary repository it is up to them to ensure that
> > committers are the only ones submitting code to the primary repository
> and
> > then syncing that code at some point over to the ASF repositories in
> order
> > to make a release.
> >
> > If we are not providing the right tooling for projects and they are
> seeking
> > outside means then I would love to work and help make the correct tools
> > available to make workflows easier and ensure security and policies are
> > being met.
> >
> > -Jake
> >
> >
> >
> >
> >
> > On Mon, Feb 3, 2014 at 5:10 AM, Sergio Fernández <
> > sergio.fernandez@salzburgresearch.at <javascript:;>> wrote:
> >
> > > Hi,
> > >
> > > On 03/02/14 10:42, Bertrand Delacretaz wrote:
> > >
> > >> On Fri, Jan 31, 2014 at 6:47 PM, James Taylor <jamestaylor@apache.org
> <javascript:;>
> > >
> > >> wrote:
> > >>
> > >>> The Phoenix project has recently come into incubation from it's
> former
> > >>> life
> > >>> as a Github project. I believe other projects have made this same
> > >>> transition, so I'm looking to get some advice from them...
> > >>>
> > >>
> > >> CouchDB has documented their Git workflow at
> > >> http://wiki.apache.org/couchdb/ContributorWorkflow
> > >>
> > >
> > > In Marmotta we adopted a Gitflow as workflow, you can find the
> > > documentation at the web site:
> > >
> > > http://marmotta.apache.org/development.html#Source_code
> > >
> > > But we'd be really interested on extend that to github-like pull
> > requests,
> > > in order to make easier to get contributions from new people. I think
> > > that's what James is asking, and what jclouds has implemented somehow.
> > But
> > > I miss some more details to actually know how they do it, specially
> > taking
> > > into account that many repos at github are not properly synced.
> > >
> > > Cheers,
> > >
> > > --
> > > Sergio Fernández
> > > Senior Researcher
> > > Knowledge and Media Technologies
> > > Salzburg Research Forschungsgesellschaft mbH
> > > Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> > > T: +43 662 2288 318 | M: +43 660 2747 925
> > > sergio.fernandez@salzburgresearch.at <javascript:;>
> > > http://www.salzburgresearch.at
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> <javascript:;>
> > > For additional commands, e-mail: general-help@incubator.apache.org
> <javascript:;>
> > >
> > >
> >
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
Re: best development methodology for Apache git?
Posted by Andrew Purtell <ap...@apache.org>.
On the question of tooling, that brings us back to James' inquiry about
having infrastructure that can emulate the GitHub pull request workflow in
house:
> Something like the Github model that combines a) the ability for managing
branches and visually reviewing patches and b) a means to gate commits
against the single source of truth, the git repo. Gerrit meets this
requirement and based on INFRA-2205 used to be setup.
What Gerritt and GitHub pull requests have in common is contributors submit
change requests as pushes of a new branch to a git remote (quite convenient
and natural for a developer using git already locally), this branch can be
updated incrementally during the review process, and there is a nice GUI
for line by line code inspection, comment, and discussion, including email
integration. (James' point "a")
Gerritt can also support workflows where human reviewers and a QA bot can
collaborate to gate the commit of a change candidate, where the actual
commit to the project master branch is done by the review tool after
established process requirements are all met. The Phoenix guys have
indicated this idea is attractive to them. (James' point "b")
On Monday, February 3, 2014, Jake Farrell <jf...@apache.org> wrote:
> Hey Sergio
> The Apache mirrors on Github are by request and run off from
> git.apache.org.
> Anyone wanting to have a svn or git project mirrored needs to submit an
> infra ticket and it can get setup.
>
> As for the Github workflows that are starting to be used, I am not a
> proponent of them. These workflows are not ideal as they repositories are
> not under any Asf control and infra can not help if there are any issues,
> its up to the project to take care of its own. Also with the JClouds and
> now Usergrid projects using this flow adds a lot of overhead for
> initial contributions as they have in the workflow the requirement to
> ensure an ICLA are on file for the contributor. Most committers do not have
> access to see the status of this. Also since these projects are not working
> directly against the primary repository it is up to them to ensure that
> committers are the only ones submitting code to the primary repository and
> then syncing that code at some point over to the ASF repositories in order
> to make a release.
>
> If we are not providing the right tooling for projects and they are seeking
> outside means then I would love to work and help make the correct tools
> available to make workflows easier and ensure security and policies are
> being met.
>
> -Jake
>
>
>
>
>
> On Mon, Feb 3, 2014 at 5:10 AM, Sergio Fernández <
> sergio.fernandez@salzburgresearch.at <javascript:;>> wrote:
>
> > Hi,
> >
> > On 03/02/14 10:42, Bertrand Delacretaz wrote:
> >
> >> On Fri, Jan 31, 2014 at 6:47 PM, James Taylor <jamestaylor@apache.org<javascript:;>
> >
> >> wrote:
> >>
> >>> The Phoenix project has recently come into incubation from it's former
> >>> life
> >>> as a Github project. I believe other projects have made this same
> >>> transition, so I'm looking to get some advice from them...
> >>>
> >>
> >> CouchDB has documented their Git workflow at
> >> http://wiki.apache.org/couchdb/ContributorWorkflow
> >>
> >
> > In Marmotta we adopted a Gitflow as workflow, you can find the
> > documentation at the web site:
> >
> > http://marmotta.apache.org/development.html#Source_code
> >
> > But we'd be really interested on extend that to github-like pull
> requests,
> > in order to make easier to get contributions from new people. I think
> > that's what James is asking, and what jclouds has implemented somehow.
> But
> > I miss some more details to actually know how they do it, specially
> taking
> > into account that many repos at github are not properly synced.
> >
> > Cheers,
> >
> > --
> > Sergio Fernández
> > Senior Researcher
> > Knowledge and Media Technologies
> > Salzburg Research Forschungsgesellschaft mbH
> > Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> > T: +43 662 2288 318 | M: +43 660 2747 925
> > sergio.fernandez@salzburgresearch.at <javascript:;>
> > http://www.salzburgresearch.at
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org<javascript:;>
> > For additional commands, e-mail: general-help@incubator.apache.org<javascript:;>
> >
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
FW: best development methodology for Apache git?
Posted by Ken Wallis <kw...@blackberry.com>.
Not sure if anyone else here still deals with the incubator mailing list
spamŠ ;)
Looks like more projects are looking for GitHub-like flows. Sounds like
Jake is part of the infra team, and looking for feedback?
Cheers.
--
Ken Wallis
Senior Product Manager - WebWorks
BlackBerry
650-620-2404
-----Original Message-----
From: Jake Farrell <jf...@apache.org>
Reply-To: "general@incubator.apache.org" <ge...@incubator.apache.org>,
"jfarrell@apache.org" <jf...@apache.org>
Date: Monday, February 3, 2014 at 6:39 AM
To: "general@incubator.apache.org" <ge...@incubator.apache.org>
Subject: Re: best development methodology for Apache git?
>Hey Sergio
>The Apache mirrors on Github are by request and run off from
>git.apache.org.
>Anyone wanting to have a svn or git project mirrored needs to submit an
>infra ticket and it can get setup.
>
>As for the Github workflows that are starting to be used, I am not a
>proponent of them. These workflows are not ideal as they repositories are
>not under any Asf control and infra can not help if there are any issues,
>its up to the project to take care of its own. Also with the JClouds and
>now Usergrid projects using this flow adds a lot of overhead for
>initial contributions as they have in the workflow the requirement to
>ensure an ICLA are on file for the contributor. Most committers do not
>have
>access to see the status of this. Also since these projects are not
>working
>directly against the primary repository it is up to them to ensure that
>committers are the only ones submitting code to the primary repository and
>then syncing that code at some point over to the ASF repositories in order
>to make a release.
>
>If we are not providing the right tooling for projects and they are
>seeking
>outside means then I would love to work and help make the correct tools
>available to make workflows easier and ensure security and policies are
>being met.
>
>-Jake
>
>
>
>
>
>On Mon, Feb 3, 2014 at 5:10 AM, Sergio Fernández <
>sergio.fernandez@salzburgresearch.at> wrote:
>
>> Hi,
>>
>> On 03/02/14 10:42, Bertrand Delacretaz wrote:
>>
>>> On Fri, Jan 31, 2014 at 6:47 PM, James Taylor <ja...@apache.org>
>>> wrote:
>>>
>>>> The Phoenix project has recently come into incubation from it's former
>>>> life
>>>> as a Github project. I believe other projects have made this same
>>>> transition, so I'm looking to get some advice from them...
>>>>
>>>
>>> CouchDB has documented their Git workflow at
>>> http://wiki.apache.org/couchdb/ContributorWorkflow
>>>
>>
>> In Marmotta we adopted a Gitflow as workflow, you can find the
>> documentation at the web site:
>>
>> http://marmotta.apache.org/development.html#Source_code
>>
>> But we'd be really interested on extend that to github-like pull
>>requests,
>> in order to make easier to get contributions from new people. I think
>> that's what James is asking, and what jclouds has implemented somehow.
>>But
>> I miss some more details to actually know how they do it, specially
>>taking
>> into account that many repos at github are not properly synced.
>>
>> Cheers,
>>
>> --
>> Sergio Fernández
>> Senior Researcher
>> Knowledge and Media Technologies
>> Salzburg Research Forschungsgesellschaft mbH
>> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
>> T: +43 662 2288 318 | M: +43 660 2747 925
>> sergio.fernandez@salzburgresearch.at
>> http://www.salzburgresearch.at
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: best development methodology for Apache git?
Posted by Jake Farrell <jf...@apache.org>.
Hey Sergio
The Apache mirrors on Github are by request and run off from git.apache.org.
Anyone wanting to have a svn or git project mirrored needs to submit an
infra ticket and it can get setup.
As for the Github workflows that are starting to be used, I am not a
proponent of them. These workflows are not ideal as they repositories are
not under any Asf control and infra can not help if there are any issues,
its up to the project to take care of its own. Also with the JClouds and
now Usergrid projects using this flow adds a lot of overhead for
initial contributions as they have in the workflow the requirement to
ensure an ICLA are on file for the contributor. Most committers do not have
access to see the status of this. Also since these projects are not working
directly against the primary repository it is up to them to ensure that
committers are the only ones submitting code to the primary repository and
then syncing that code at some point over to the ASF repositories in order
to make a release.
If we are not providing the right tooling for projects and they are seeking
outside means then I would love to work and help make the correct tools
available to make workflows easier and ensure security and policies are
being met.
-Jake
On Mon, Feb 3, 2014 at 5:10 AM, Sergio Fernández <
sergio.fernandez@salzburgresearch.at> wrote:
> Hi,
>
> On 03/02/14 10:42, Bertrand Delacretaz wrote:
>
>> On Fri, Jan 31, 2014 at 6:47 PM, James Taylor <ja...@apache.org>
>> wrote:
>>
>>> The Phoenix project has recently come into incubation from it's former
>>> life
>>> as a Github project. I believe other projects have made this same
>>> transition, so I'm looking to get some advice from them...
>>>
>>
>> CouchDB has documented their Git workflow at
>> http://wiki.apache.org/couchdb/ContributorWorkflow
>>
>
> In Marmotta we adopted a Gitflow as workflow, you can find the
> documentation at the web site:
>
> http://marmotta.apache.org/development.html#Source_code
>
> But we'd be really interested on extend that to github-like pull requests,
> in order to make easier to get contributions from new people. I think
> that's what James is asking, and what jclouds has implemented somehow. But
> I miss some more details to actually know how they do it, specially taking
> into account that many repos at github are not properly synced.
>
> Cheers,
>
> --
> Sergio Fernández
> Senior Researcher
> Knowledge and Media Technologies
> Salzburg Research Forschungsgesellschaft mbH
> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> T: +43 662 2288 318 | M: +43 660 2747 925
> sergio.fernandez@salzburgresearch.at
> http://www.salzburgresearch.at
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: best development methodology for Apache git?
Posted by Sergio Fernández <se...@salzburgresearch.at>.
Hi,
On 03/02/14 10:42, Bertrand Delacretaz wrote:
> On Fri, Jan 31, 2014 at 6:47 PM, James Taylor <ja...@apache.org> wrote:
>> The Phoenix project has recently come into incubation from it's former life
>> as a Github project. I believe other projects have made this same
>> transition, so I'm looking to get some advice from them...
>
> CouchDB has documented their Git workflow at
> http://wiki.apache.org/couchdb/ContributorWorkflow
In Marmotta we adopted a Gitflow as workflow, you can find the
documentation at the web site:
http://marmotta.apache.org/development.html#Source_code
But we'd be really interested on extend that to github-like pull
requests, in order to make easier to get contributions from new people.
I think that's what James is asking, and what jclouds has implemented
somehow. But I miss some more details to actually know how they do it,
specially taking into account that many repos at github are not properly
synced.
Cheers,
--
Sergio Fernández
Senior Researcher
Knowledge and Media Technologies
Salzburg Research Forschungsgesellschaft mbH
Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
T: +43 662 2288 318 | M: +43 660 2747 925
sergio.fernandez@salzburgresearch.at
http://www.salzburgresearch.at
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: best development methodology for Apache git?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Fri, Jan 31, 2014 at 6:47 PM, James Taylor <ja...@apache.org> wrote:
> The Phoenix project has recently come into incubation from it's former life
> as a Github project. I believe other projects have made this same
> transition, so I'm looking to get some advice from them...
CouchDB has documented their Git workflow at
http://wiki.apache.org/couchdb/ContributorWorkflow
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: best development methodology for Apache git?
Posted by Andrew Phillips <de...@yahoo.co.uk>.
> The Phoenix project has recently come into incubation from it's former
> life as a Github project. I believe other projects have made this same
> transition, so I'm looking to get some advice from them.
Over at Apache jclouds we're running a similar setup, with our main repos in ASF Git mirrored to GitHub for interaction with contributors. Feel free to ask on dev@j.a.o or hop onto #jclouds at Freenode for more details!
Regards
ap
On Friday, 31 January 2014, 12:47, James Taylor <ja...@apache.org> wrote:
The Phoenix project has recently come into incubation from it's former life
>as a Github project. I believe other projects have made this same
>transition, so I'm looking to get some advice from them. What's the best
>development methodology folks have found for collaborative development when
>your source of truth is an Apache git repo? Something like the Github model
>that combines a) the ability for managing branches and visually reviewing
>patches and b) a means to gate commits against the single source of truth,
>the git repo.
>
>Gerrit meets this requirement and based on INFRA-2205 used to be setup. If
>that's not an option, what have folks found that works well?
>
>Thanks,
>James
>
>
>