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 8F98ABA07 for ; Tue, 10 Jan 2012 07:05:42 +0000 (UTC) Received: (qmail 55761 invoked by uid 500); 10 Jan 2012 07:05:40 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 55507 invoked by uid 500); 10 Jan 2012 07:05:21 -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 55467 invoked by uid 99); 10 Jan 2012 07:05:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jan 2012 07:05:15 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [62.179.121.33] (HELO fep13.mx.upcmail.net) (62.179.121.33) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jan 2012 07:05:10 +0000 Received: from edge01.upcmail.net ([192.168.13.236]) by viefep13-int.chello.at (InterMail vM.8.01.05.04 201-2260-151-105-20111014) with ESMTP id <20120110070445.TZLL19694.viefep13-int.chello.at@edge01.upcmail.net> for ; Tue, 10 Jan 2012 08:04:45 +0100 Received: from bart.at.home ([80.108.142.211]) by edge01.upcmail.net with edge id Kj4l1i00f4Zs40G01j4lXq; Tue, 10 Jan 2012 08:04:45 +0100 X-SourceIP: 80.108.142.211 Received: from virasnotebook.at.mobile (unknown [10.8.0.6]) by bart.at.home (Postfix) with ESMTP id 1C26F1B7E for ; Tue, 10 Jan 2012 08:04:45 +0100 (CET) Message-ID: <4F0BE319.8080703@users.sourceforge.net> Date: Tue, 10 Jan 2012 08:04:57 +0100 From: Viras User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: callback-dev@incubator.apache.org Subject: Re: Commit and contribution workflows (Was: Cordova-Android now up-to-date in the ASF Git Repo) References: <4F04A096.7010108@users.sourceforge.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit No need to worry - I just wanted to make sure that I understand the workflow correctly! Best, Wolfgang Am 09.01.2012 19:53, schrieb Simon MacDonald: > We are trying to figure it all out. Commit to the github site for now > and we can push to the Apache site. Please bear with us as we continue > to have growing pains. > > Simon Mac Donald > http://hi.im/simonmacdonald > > > > On Wed, Jan 4, 2012 at 1:55 PM, Viras wrote: >> Hi, >> >> 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 >> repositories? >> >> Best, >> Wolfgang >> >> 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 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 >>> >> >> -- >> GOFG - Get On Fat Guy >> http://www.gofg.at/ - powered by PhoneGap > -- GOFG - Get On Fat Guy http://www.gofg.at/ - powered by PhoneGap