They have documented the workflow for contributers an committers in the wiki.
http://wiki.apache.org/cordova/ContributorWorkflow http://wiki.apache.org/cordova/CommitterWorkflow Cyrill Am 21.11.2012 um 10:29 schrieb Nick Tsitlakidis <ni...@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? > > > On Wed, Nov 21, 2012 at 8:10 PM, Greg Reddin <gred...@gmail.com> wrote: > >> On Wed, Nov 21, 2012 at 11:46 AM, Alex Harui <aha...@adobe.com> wrote: >> >>> I am new to Git/GitHub, but I am wondering whether Infra considered using >>> its own GitHub (see [1]). >> >> >> 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. >> >> >>> 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 >> >> >> 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 that >> at Apache is for commit messages and code discussions to take place on the >> 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 trying >> to do an end-run around it. > > > > -- > Nick Tsitlakidis, > > CEO and Software Architect at Perfect Edge LTD. > www.perfectedz.com
