+1 Julien
> On Jun 17, 2017, at 15:08, Wes McKinney <[email protected]> wrote: > > None here. I think it's a good idea. > >> On Sat, Jun 17, 2017 at 3:37 PM Uwe L. Korn <[email protected]> wrote: >> >> Picking this up again, as we would like to create a secondary repository >> to build Python releases: https://issues.apache.org/jira/browse/ARROW-1116 >> I would really like to try out gitbox and this seems like a nice place to >> get more experiences with it. Is there any opposition to that? >> >>> Am 20.05.2017 um 15:52 schrieb Justin Erenkrantz <[email protected] >>> : >>> >>>> On Fri, May 19, 2017 at 6:59 PM, Jacques Nadeau <[email protected]> >> wrote: >>>> >>>> My main question would be: can we disable merges in the ui and only >>>> constraint to rebase/fast-forward merges? I've found on other GitHub >>>> projects that the default behavior of merge makes an unintelligible >>>> history. >>> >>> >>> Once the repository is created, we should be able to set it as: >>> >>> https://help.github.com/articles/configuring-pull-request-merges/ >>> >>> I'm guessing that we would want it to be "Allow Rebase Merging" only? >> That >>> seems reasonable to me. >>> >>> This *might* have to be configured by Infra if we're not given the >>> Owner/Maintainer privileges. From what I can tell, I don't believe that >>> regular Contributors (who can push changes) can modify this setting >>> themselves. (The infra team just confirmed that they can alter that >> value.) >>> >>> Cheers. -- justin >>
