Return-Path: X-Original-To: apmail-ant-dev-archive@www.apache.org Delivered-To: apmail-ant-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 416E31158C for ; Sun, 11 May 2014 20:11:48 +0000 (UTC) Received: (qmail 84234 invoked by uid 500); 11 May 2014 20:05:08 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 84163 invoked by uid 500); 11 May 2014 20:05:08 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 84152 invoked by uid 99); 11 May 2014 20:05:08 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 May 2014 20:05:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boards@gmail.com designates 209.85.214.178 as permitted sender) Received: from [209.85.214.178] (HELO mail-ob0-f178.google.com) (209.85.214.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 May 2014 20:05:04 +0000 Received: by mail-ob0-f178.google.com with SMTP id va2so7114308obc.37 for ; Sun, 11 May 2014 13:04:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=kLUj/XnL4UsMUUVbd/qUNHTy19J/iEEo0SgCW/Vm5zg=; b=P68bXur4yDVzmooAq0fRJah4AAs29qipn253/Xm4RwdjyxLugV6xOUlSJnpNfGUMpF Y1Stf6UHLBC1dF4zAgspO5+hrsjWQf5JocY5FRvKwgJGGxk2Qk41fVtL6lxG3QQXgkQ4 OCKQ0ms4HjAKigmXGjM+Yt5Ww3a0bX81QllzxiUN8DHzLghzIHBRLIRiMXw/pRkUx8Hq /W/VNLfy6xnlG8SzDcic0CthaKu8vLlPcotVemrpPDAizDqQd1Dhf5GVh7lSuF8k+Txn ZMoDvxbmtCLpM8AqPMba1O76A5Vt5xlQJhU88Lg/8QDuRypYTRiwJoG38HNp6ZVKY/n4 kdxA== MIME-Version: 1.0 X-Received: by 10.60.179.138 with SMTP id dg10mr28782633oec.13.1399838680780; Sun, 11 May 2014 13:04:40 -0700 (PDT) Received: by 10.76.72.68 with HTTP; Sun, 11 May 2014 13:04:40 -0700 (PDT) In-Reply-To: <000901cf69bd$9af5a900$d0e0fb00$@de> References: <0LnfuZ-1XMqFe0xRf-00hxem@mail.gmx.com> <463429EF-E41D-4950-BF64-197CE3103612@gmail.com> <9422680C-34B5-4603-8515-E2AF9D0840D5@gmail.com> <80819A93-2681-4402-8818-219D2100C045@hibnet.org> <87k39z5rtd.fsf@v35516.1blu.de> <575EF872-EBA4-4C04-81FB-49C4F294DEFC@gmx.de> <000901cf69bd$9af5a900$d0e0fb00$@de> Date: Sun, 11 May 2014 15:04:40 -0500 Message-ID: Subject: Re: Hoped for advantages of migrating to git From: Matt Sicker To: Ant Developers List Content-Type: multipart/alternative; boundary=047d7b86d7824f97a104f92557c2 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b86d7824f97a104f92557c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I think it would work better to just do development on ASF, but accept pull requests via GitHub somewhat manually. This is how it's done with Apache Camel: http://camel.apache.org/contributing.html So it's done manually. Plus, nobody can write to the ASF GitHub repos without pulling some strings in INFRA to do something about it, and I don't think they like that idea anyhow due to the bylaws regarding what was already said above. On 7 May 2014 01:28, Jan Mat=C3=A8rne (jhm) wrote: > As a ASF project we MUST have a repo in Apache land: > http://www.apache.org/dev/writable-git > "ASF releases must be cut from the canonical ASF Git repositories." > > The absolute minimum is therefore: > - working on somewhere else > - starting a release: > -- pull all changes to local > -- push to ASF-repo > -- create a branch/tag in the ASF repo for the release > -- do the release > > But personally I prefer having one "right" repo in the ASF I could trust. > Additional repos somewhere else (like on Github) could "just help". > > (If working with Git - would Gerrit a good candidate?) > > > Jan > > > > -----Urspr=C3=BCngliche Nachricht----- > > Von: Antoine Levy Lambert [mailto:antoine@gmx.de] > > Gesendet: Mittwoch, 7. Mai 2014 02:18 > > An: Ant Developers List > > Betreff: Re: Hoped for advantages of migrating to git > > > > Matt, Jesse, > > > > I think that both of you are basically saying that accepting pull > > requests entered in github is going to be more manual work, including > > more command line work, in the case of a migration to git-wip- > > us.apache.org as opposed to migrating to use only github. > > > > I don=E2=80=99t know whether an option of using only github and not the= ASF > > hosted git is acceptable for the ASF ? for the Ant committers ? > > > > Personally I am already glad to have seen support to migrate to git, > > and I would not want to push something more controversial. > > > > While github today is a very attractive platform, it could one day > > diverge from ASF policies or make other changes in their terms and > > conditions that we would dislike and not be able to influence. > > > > There is a file > > https://svn.apache.org/repos/private/committers/docs/github_team.txt > > which links the apache user ids of committers with their github ids, I > > wonder whether this linkage gives write access to the github mirrors of > > Apache projects ? > > > > Also, while researching this I found an interesting presentation by > > Jukka Zitting [1] and a mail message concerning Apache and Github [2] > > and also a wiki page from the Apache Cordova project [3] > > > > Best regards, > > > > Antoine > > > > > > [1] http://www.slideshare.net/jukka/apache-development-with-github-and- > > travis-ci > > [2] http://mail-archives.apache.org/mod_mbox/lucene- > > dev/201401.mbox/%3C596FFF55-6E33-4451-93D4-75ADD6CADCED@gmail.com%3E > > [3] http://wiki.apache.org/cordova/GitWorkflow > > > > > > > > On May 6, 2014, at 6:33 PM, Matt Sicker wrote: > > > > > I mean how do you accept pull requests? You wouldn't be able to do it > > > through GitHub. You'd have to manually pull the branch from GitHub > > > like the name "pull request" implies. If you could commit to GitHub, > > > then you could add a remote besides origin for GitHub, then pull from > > > the GitHub remote, then push to the ASF remote (origin). > > > > > > > > > On 6 May 2014 01:45, Stefan Bodewig wrote: > > > > > >> On 2014-05-06, Matt Sicker wrote: > > >> > > >>> Git allows you to do both. You can auto-merge from GH, but I'm not > > >>> sure how you can even get write access to ASF GH repos. > > >> > > >> You don't, you commit to the ASF repo and it gets mirrored. > > >> > > >> IIRC some projects have their own forks of the ASF mirror and accept > > >> pull request on this fork. They then merge changes from their fork > > >> to the ASF repo. > > >> > > >> I'm not conviced I'd want to work that way, applying PRs without the > > >> Web-UI on a local checkout of the ASF git repo works fine for me. > > >> > > >> Stefan > > >> > > >> -------------------------------------------------------------------- > > - > > >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For > > additional > > >> commands, e-mail: dev-help@ant.apache.org > > >> > > >> > > > > > > > > > -- > > > Matt Sicker > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org > > For additional commands, e-mail: dev-help@ant.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org > For additional commands, e-mail: dev-help@ant.apache.org > > --=20 Matt Sicker --047d7b86d7824f97a104f92557c2--