incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Viras <>
Subject Re: Commit and contribution workflows (Was: Cordova-Android now up-to-date in the ASF Git Repo)
Date Wed, 04 Jan 2012 18:55:18 GMT

thanks - so even when I signed a CLA I have to commit to github until
cordova lead decides to give me commit access to the git-wip-us


Am 04.01.2012 18:13, schrieb Jukka Zitting:
> Hi,
> On Wed, Jan 4, 2012 at 5:46 PM, Viras <> wrote:
>> just to clarify: should I commit to github or to some apache git repository?
> All Cordova committers should ideally push directly to the Cordova
> repositories at
> We can set up mirrors of those repositories on Github or elsewhere,
> but for finely grained audit logs for code provenance the repositories
> on Apache servers should be the primary push target. As soon as we are
> happy with the functionality of the git-wip-us repositories, the
> existing and spaces should be
> discontinued.
> Contributors that are not yet Cordova committers can push their
> changes to their personal clones on Github and send a pull request by
> email to callback-dev@ (to be renamed) or to the appropriate CB issue.
> The git-svn repositories mirrored at already support
> automatic forwarding of pull request notifications to the respective
> dev@ lists, so we could set up something similar also for Cordova if
> there's interest. And of course changes can also be submitted as
> normal patches even without any Git push/pull workflows.
> It would be great if the Cordova community came up with a wiki or web
> page that outlines the recommended contribution workflow.
> Once a contributor has submitted enough good patches, he or she should
> be granted Cordova committership and thus direct push access to the
> Cordova repositories on git-wip-us.
> BR,
> Jukka Zitting

GOFG - Get On Fat Guy - powered by PhoneGap

View raw message