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 59759DAA7 for ; Tue, 19 Jun 2012 19:15:35 +0000 (UTC) Received: (qmail 53039 invoked by uid 500); 19 Jun 2012 19:09:03 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 46113 invoked by uid 500); 19 Jun 2012 19:08:47 -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 69103 invoked by uid 99); 19 Jun 2012 18:14:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2012 18:14:52 +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 (nike.apache.org: domain of shazron@gmail.com designates 209.85.161.175 as permitted sender) Received: from [209.85.161.175] (HELO mail-gg0-f175.google.com) (209.85.161.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2012 18:14:46 +0000 Received: by ggnp4 with SMTP id p4so4561549ggn.6 for ; Tue, 19 Jun 2012 11:14:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=2LZiHD1skfMow84KM5BRe1/0w+vWaThjTn4ZxmPTw9Q=; b=PTAhcs0USthqXsxYZ587Xfw1SeGOk/TGQXnft+fvv/KLbt8eEvU10uQuovnkavOdG7 sFGwkDsFCVTVLRLVdylPW8+TEcR/YBu7Z96IlZ+/TTteGA0P5p4qtkBW0pHnZHJGD8t1 POaZ2kJ8ujlIgeG0Lm5VnSNSnS7XUBpn6ELyeLLPNEQlETbGCSO3qBlsZ6U6RLeCT67W xF0IPMCFaT75RFICSVcN5N/IcfmppXaOFyGlHvfSSWhWgRfCPEc7Q8Zct6bNCSbisGTm 5r1fWufrfEiczA2FCTE1/bQB8vKmDP9iC31GwquOjEchKsrFKML3c3+j2rkUN5PjnXHw foDg== Received: by 10.60.6.225 with SMTP id e1mr20668646oea.71.1340129665550; Tue, 19 Jun 2012 11:14:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.128.105 with HTTP; Tue, 19 Jun 2012 11:13:45 -0700 (PDT) In-Reply-To: References: From: Shazron Date: Tue, 19 Jun 2012 11:13:45 -0700 Message-ID: Subject: Re: Git support To: callback-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 The repo finally finished cloning. I attached a screenshot of the merge request interface: http://cl.ly/HUGH Seems intuitive enough - the Request Merge button is grouped from the repo you cloned from, and the Source (your branch in your cloned repo) and Target (the cloned repo's branch) refers to the cloned+upstream repos which will be the typical use case. Github allows sending a pull request to any other "sibling" cloned repo in the network but I doubt that is useful. On Tue, Jun 19, 2012 at 10:43 AM, Shazron wrote: > The system looks good. I think the only concern that I would have is > integrating pull requests (Allura calls them merge requests) easily, > having it be as easy as Github - we want to make that as painless as > possible for contributors. > > I took a look at an example here: > http://sourceforge.net/p/allura/git/merge-requests/3/ > The contributor would have to have their forked repo hosted on our > system (and create a new account), just like Github's system. > > My fork of Allura has been stuck at "analyzing" (in the left sidebar) > for a while and I can't find where to send a merge request yet in the > UI from my forked repo, so I can't evaluate that yet, which I assume > in the left sidebar has a lot of functionality I am missing. > > > On Tue, Jun 19, 2012 at 6:45 AM, Brian LeRoux wrote: >> had it been an option at the time of our incubation I suspect we >> would've gone for this system for sure >> >> >> On Tue, Jun 19, 2012 at 9:34 AM, Ross Gardler >> wrote: >>> On 19 June 2012 14:19, Brian LeRoux wrote: >>>> wow, I really like the issue tracker (and gui in general actually). >>>> problem is we're just starting to get our groove here and fear another >>>> change would really tick off the community! >>> >>> Don't worry, as my mail said "I don't mean to imply that the ASF will >>> be adopting this as >>> infrastructure here, we are a long way from evaluating that.". This is >>> *not* being evaluated by the infra team you're not going to get booted >>> from the current system. >>> >>> I'm just curious about the potential. The Allura project is asking to >>> self host and thus I'm wondering if other projects not yet married to >>> infrastructure here might end up asking to use it. >>> >>> Ross >>> >>> Ross >>> >>>> >>>> cool proj tho. >>>> >>>> On Tue, Jun 19, 2012 at 9:02 AM, Ross Gardler >>>> wrote: >>>>> I just wanted to flag a new Incubator proposal I'm a part of that may, >>>>> or may not, help with the ASFs provision of Git support for projects >>>>> like yours. It's the code behind Sourceforge and, as such, provides >>>>> tight integration between the various tools. See >>>>> http://wiki.apache.org/incubator/AlluraProposal (feature set at >>>>> http://sourceforge.net/p/allura/wiki/Features/) >>>>> >>>>> One of the things that I would like your input on is whether or not >>>>> this toolset goes any way towards solving any of the remaining issues >>>>> you have with the ASFs support of Git workflows from your perspective >>>>> as a heavy user of Git and GitHub. >>>>> >>>>> Note, I don't mean to imply that the ASF will be adopting this as >>>>> infrastructure here, we are a long way from evaluating that. However, >>>>> some early feedback from this project would be helpful to me as a >>>>> mentor on the Allura project. >>>>> >>>>> Ross >>>>> >>>>> -- >>>>> Ross Gardler (@rgardler) >>>>> Programme Leader (Open Development) >>>>> OpenDirective http://opendirective.com >>> >>> >>> >>> -- >>> Ross Gardler (@rgardler) >>> Programme Leader (Open Development) >>> OpenDirective http://opendirective.com