Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of cyrill.zadra@gmail.com
 designates 209.85.216.54 as permitted sender)
Subject: Re: Make Git happen
References: 
 <CAEFz_vt4wy+XCqMv_rxdPyCs5YzM_XnR1AMO5oRbstZS=TpSFg@mail.gmail.com>
 <CCD2537E.48DB4%aharui@adobe.com>
 <CAKWVykVW1QpxzeYC5i_G8=eqMszu80WP8iQ8QeJi6dv=hPBykQ@mail.gmail.com>
 <CACWtOtU290axZCTw4FQuM2KPrYpUccQnJoT7y2=pqtdaOgArEQ@mail.gmail.com>
From: Cyrill Zadra <cyrill.zadra@gmail.com>
Content-Type: multipart/alternative;
	boundary=Apple-Mail-9B90886C-B976-4F64-9F74-F4A3E7E8BA2D
In-Reply-To: 
 <CACWtOtU290axZCTw4FQuM2KPrYpUccQnJoT7y2=pqtdaOgArEQ@mail.gmail.com>
Message-Id: <E9B5F1AA-4209-4FBF-98B5-855B4AFFD43C@gmail.com>
Date: Wed, 21 Nov 2012 10:35:28 -0800
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)

--Apple-Mail-9B90886C-B976-4F64-9F74-F4A3E7E8BA2D
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

They have documented the workflow for contributers an committers in the wiki=
.=20

http://wiki.apache.org/cordova/ContributorWorkflow
http://wiki.apache.org/cordova/CommitterWorkflow

Cyrill


Am 21.11.2012 um 10:29 schrieb Nick Tsitlakidis <nickt@perfectedz.com>:

> If I'm not mistaken, Cordova (they also haven't graduated yet) is already
> using Git. Any thoughts on how they do it?
>=20
>=20
> On Wed, Nov 21, 2012 at 8:10 PM, Greg Reddin <gredbug@gmail.com> wrote:
>=20
>> On Wed, Nov 21, 2012 at 11:46 AM, Alex Harui <aharui@adobe.com> wrote:
>>=20
>>> I am new to Git/GitHub, but I am wondering whether Infra considered usin=
g
>>> its own GitHub (see [1]).
>>=20
>>=20
>> I know they looked into that and were in talks with GitHub for a while. I=

>> don't remember the details and probably couldn't share them on a public
>> list anyway, but for some reason that didn't work out.
>>=20
>>=20
>>> Another angle to explore is whether it would be ok from an Apache
>>> perspective to simply do our work on the public GitHub and only copy
>>> released sources back to either Apache SVN or some simpler Apache Git
>>> installation
>>=20
>>=20
>> I would have trouble with that approach and I suspect the board would too=
.
>> We want development to be open and transparent. The way we accomplish tha=
t
>> at Apache is for commit messages and code discussions to take place on th=
e
>> mailing list. In this way we know code is being developed in the open by
>> watching the mailing lists. I know it's a somewhat antiquated methodology=

>> in today's world, but it's the current implementation of the Apache Way.
>> Many Apache members understand the disadvantages and people do want to
>> change it. But they want to change it without sacrificing core tenets of
>> the Apache Way. So this is not easy and it won't happen overnight. But
>> there's good reasons IMO for us to stick with the program instead of tryi=
ng
>> to do an end-run around it.
>=20
>=20
>=20
> --=20
> Nick Tsitlakidis,
>=20
> CEO and Software Architect at Perfect Edge LTD.
> www.perfectedz.com

--Apple-Mail-9B90886C-B976-4F64-9F74-F4A3E7E8BA2D--