Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CANyrgve1s-fKFDrAxCE1EoD8bF1wB8y0nGFXGm4Vki9tnmsYcQ@mail.gmail.com>
References: 
 <CAAF1JdhOcL5SqnFfibPPBMM2pRu9c_yh+jG_JfafVCOKeajf4Q@mail.gmail.com>
	<CAEWfVJ=7sSu_V3rzftJ0j-suqEJnnH3p7-x7rEWeo9VO+nNsmA@mail.gmail.com>
	<52EF6B1C.2080505@salzburgresearch.at>
	<CANyrgve1s-fKFDrAxCE1EoD8bF1wB8y0nGFXGm4Vki9tnmsYcQ@mail.gmail.com>
Date: Mon, 3 Feb 2014 10:34:38 -0800
Message-ID: 
 <CA+RK=_AX4aJhkdStAwy3q0sJfGV1iZ6_zDJ2eYCthJeq-VX04A@mail.gmail.com>
Subject: Re: best development methodology for Apache git?
From: Andrew Purtell <apurtell@apache.org>
To: "general@incubator.apache.org" <general@incubator.apache.org>
Content-Type: multipart/alternative; boundary=089e0141a092b1e93004f184c6ca

--089e0141a092b1e93004f184c6ca
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <jfarrell@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 ha=
ve
> access to see the status of this. Also since these projects are not worki=
ng
> directly against the primary repository it is up to them to ensure that
> committers are the only ones submitting code to the primary repository an=
d
> then syncing that code at some point over to the ASF repositories in orde=
r
> to make a release.
>
> If we are not providing the right tooling for projects and they are seeki=
ng
> 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=E1ndez <
> 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 forme=
r
> >>> 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=E1ndez
> > Senior Researcher
> > Knowledge and Media Technologies
> > Salzburg Research Forschungsgesellschaft mbH
> > Jakob-Haringer-Stra=DFe 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<javasc=
ript:;>
> > For additional commands, e-mail: general-help@incubator.apache.org<java=
script:;>
> >
> >
>


--=20
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

--089e0141a092b1e93004f184c6ca--