Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E58A7B308 for ; Wed, 4 Jan 2012 17:13:57 +0000 (UTC) Received: (qmail 55674 invoked by uid 500); 4 Jan 2012 17:13:57 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 55648 invoked by uid 500); 4 Jan 2012 17:13:57 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 55640 invoked by uid 99); 4 Jan 2012 17:13:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 17:13:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-we0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 17:13:52 +0000 Received: by werm13 with SMTP id m13so9507121wer.6 for ; Wed, 04 Jan 2012 09:13:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=q7pkPalO6BEBDczHvXH+8HD/XE4jfxMy1usPgshO5fA=; b=IReIE1u6KY1EzbiyI+3CwfaoKT9I4TmxgTtEHyx010SnP8vQO5KCJmMqFvSBmfuSSr pY9OTfqsfLYi2YH0Fpq+7wPLctdAxxD5fhQtRD4YSl1XpOOcRa6S2lf7FiJBrH+BteFB 77V/ZweV/MUvqiRrKtH160oiDNo4SqZNKkrzU= Received: by 10.216.139.156 with SMTP id c28mr37194112wej.34.1325697211227; Wed, 04 Jan 2012 09:13:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.99.65 with HTTP; Wed, 4 Jan 2012 09:13:10 -0800 (PST) From: Jukka Zitting Date: Wed, 4 Jan 2012 18:13:10 +0100 Message-ID: Subject: Commit and contribution workflows (Was: Cordova-Android now up-to-date in the ASF Git Repo) To: callback-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 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 git-wip-us.apache.org. 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 github.com/callback and github.com/cordova 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 github.com/apache 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