+1 for a general move to git, even if it is done one-by-one by lazy consensus.
I guess on moving, INFRA do not need to remove the old mirrored repository in GitHub? (It should be mirrored form the same location). Otherwise we need to be worried about open pull requests, link to forks, etc. We can start with VFS, then perhaps IO and Collections? On 25 May 2016 at 12:09, Benedikt Ritter <[email protected]> wrote: > Gary Gregory <[email protected]> schrieb am Di., 24. Mai 2016 um > 23:03 Uhr: > >> I think we have to do 1-by-1 with infra anyway but I'd prefer to do it all. >> My guess from recollections from previous email threads is that folks would >> rather do this 1-by-1. You could start a [POLL] thread. >> > > Since we still have the "every component may do stuff as it sees fit" we > should move components 1-by-1. > > In the past we have did votes by lazy consensus for moving components to > git. > > Benedikt > > >> >> Gary >> >> On Tue, May 24, 2016 at 1:48 PM, <[email protected]> wrote: >> >> > I would nominate VFS to move to git, the question is do we keep want to >> do >> > that one by one? >> > >> > Gruss >> > Bernd >> > >> > -- >> > http://bernd.eckenfels.net >> > >> > -----Original Message----- >> > From: Gary Gregory <[email protected]> >> > To: Commons Developers List <[email protected]> >> > Cc: [email protected], Commons Users List <[email protected]> >> > Sent: Di., 24 Mai 2016 22:36 >> > Subject: Re: [ANNOUNCE] Apache Commons git repositories now writable for >> > all ASF committers >> > >> > The more this goes on the more I wish we'd switch all Commons components >> to >> > git lock stock and two smoking barrels. >> > >> > Gary >> > On May 24, 2016 12:43 PM, <[email protected]> wrote: >> > >> > > Hello Jochen, >> > > >> > > I think the announcement is refering to the Apache hosted Git >> (writeable) >> > > repositories (https://git-wip-us.apache.org/) - not the apache >> > > organisation on github or the public git mirror ( >> https://git.apache.org >> > ). >> > > Those are always read-only mirrors. (Note that most commons projects >> are >> > > still in SVN, which means there is no writeable git master repo for >> them >> > > either) >> > > >> > > Gruss >> > > Bernd >> > > >> > > -- >> > > http://bernd.eckenfels.net >> > > >> > > -----Original Message----- >> > > From: Jochen Wiedmann <[email protected]> >> > > To: Commons Developers List <[email protected]> >> > > Cc: Commons Users List <[email protected]>, "[email protected] >> " >> > < >> > > [email protected]> >> > > Sent: Di., 24 Mai 2016 12:24 >> > > Subject: Re: [ANNOUNCE] Apache Commons git repositories now writable >> for >> > > all ASF committers >> > > >> > > On Sat, May 21, 2016 at 5:13 PM, Benedikt Ritter <[email protected]> >> > > wrote: >> > > > Hello, >> > > > >> > > > a while back, the Apache Commons project decided to grant write >> access >> > to >> > > > all ASF committers [1]. While setting this up for our SVN >> repositories >> > > was >> > > > easy, we had some problems to grant the necessary karma to all ASF >> > > > committers for our git repositories. This problem has now been fixed >> > [2]. >> > > > All ASF committers should now be able to commit to our git >> repositories >> > > as >> > > > well. This includes the repositories of the following components: >> > > > >> > > > - Apache Commons Lang >> > > > - Apache Commons Math >> > > > - Apache Commons Compress >> > > > - Apache Commons SCXML >> > > > >> > > > If you experience any issues, please report them on >> > > [email protected]. >> > > > >> > > > Have fun, >> > > > Benedikt, on behalf of the Apache Commons community >> > > > >> > > > [1] https://s.apache.org/RKWl >> > > > [2] https://issues.apache.org/jira/browse/INFRA-10636 >> > > >> > > Doesn't work for my Github User (jochenw): >> > > >> > > $ git push >> > > Username for 'https://github.com': >> > > Password for 'https://[email protected]': >> > > remote: Permission to apache/commons-fileupload.git denied to jochenw. >> > > fatal: unable to access >> > > 'https://github.com/apache/commons-fileupload.git/': The requested URL >> > > returned error: 403 >> > > >> > > >> > > -- >> > > The next time you hear: "Don't reinvent the wheel!" >> > > >> > > >> > > >> > >> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> -- Stian Soiland-Reyes Apache Commons, Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
