that is pretty cool! might set this up for myself for backup dev env
On Tue, Jun 19, 2012 at 2:13 PM, Shazron <[email protected]> wrote: > 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 <[email protected]> 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 <[email protected]> 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 >>> <[email protected]> wrote: >>>> On 19 June 2012 14:19, Brian LeRoux <[email protected]> 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 >>>>> <[email protected]> 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
