Re: [imaging] Moved to git. (Was: Re: [RESULT][VOTE][LAZY] Move commons-imaging to git)

Hi Rob, Thank you for moving the bits! :-) Gary On Wed, May 24, 2017 at 12:19 PM, Rob Tompkins wrote: > All, > > I have moved the code (branches and tags) into the newly created > repository, and I have opened the following ticket with infra ( > https://issues.apache.org/jira/browse/INFRA-1422

[imaging] Moved to git. (Was: Re: [RESULT][VOTE][LAZY] Move commons-imaging to git)

All, I have moved the code (branches and tags) into the newly created repository, and I have opened the following ticket with infra (https://issues.apache.org/jira/browse/INFRA-14227 ) to have the mirrors re-pointed. Let me know if anyone sees

Re: [RESULT][VOTE][LAZY] Move commons-imaging to git

> On May 24, 2017, at 11:22 AM, Emmanuel Bourg wrote: > > Le 24/05/2017 à 17:18, Emmanuel Bourg a écrit : > >>> I suppose I’ll need PMC member help here as well. Would someone be able to >>> create a git repo for commons-imaging? I have everything cloned properly >>> from the git mirror as Em

Re: [RESULT][VOTE][LAZY] Move commons-imaging to git

Le 24/05/2017 à 17:18, Emmanuel Bourg a écrit : >> I suppose I’ll need PMC member help here as well. Would someone be able to >> create a git repo for commons-imaging? I have everything cloned properly >> from the git mirror as Emmanuel suggested, so I’m ready to begin here. I >> just need the

Re: [RESULT][VOTE][LAZY] Move commons-imaging to git

Le 24/05/2017 à 17:04, Rob Tompkins a écrit : > I suppose I’ll need PMC member help here as well. Would someone be able to > create a git repo for commons-imaging? I have everything cloned properly from > the git mirror as Emmanuel suggested, so I’m ready to begin here. I just need > the repo c

Re: [RESULT][VOTE][LAZY] Move commons-imaging to git

> On May 22, 2017, at 11:37 AM, Emmanuel Bourg wrote: > > Le 22/05/2017 à 14:10, Rob Tompkins a écrit : > >> Having not gone through this process before, what must I do to accomplish >> the task. My first thought is to open a jira with INFRA and go from there. >> But, I recall hearing from fo

Re: [RESULT][VOTE][LAZY] Move commons-imaging to git

Le 22/05/2017 à 14:10, Rob Tompkins a écrit : > Having not gone through this process before, what must I do to accomplish the > task. My first thought is to open a jira with INFRA and go from there. But, I > recall hearing from folks that one must be a PMC member to accomplish this > task, so I

[RESULT][VOTE][LAZY] Move commons-imaging to git

Hello all, This vote passes with the following (in order of appearance): Gary Gregory: +1 Amey Jadiye: +1 (non-binding) Damjan Jovanovic: +1 Dave Brosius: +1 With no down votes I will begin the process of migrating to git. Having not gone through this process before, what must I do to accomplis

Re: [VOTE][LAZY] Move commons-imaging to git

+1 On 05/19/2017 10:03 AM, Amey Jadiye wrote: +1 On May 18, 2017 10:52 PM, "Rob Tompkins" wrote: Hello all, I would like to propose that we move commons-imaging to git in hopes of doing that before the potential of releasing a 1.0. I figure that it would be an easier migration with only a

Re: [VOTE][LAZY] Move commons-imaging to git

+1 On Thu, May 18, 2017 at 7:22 PM, Rob Tompkins wrote: > Hello all, > > I would like to propose that we move commons-imaging to git in hopes of > doing that before the potential of releasing a 1.0. I figure that it would > be an easier migration with only a trunk to manage in getting it over th

Re: [VOTE][LAZY] Move commons-imaging to git

+1 On May 18, 2017 10:52 PM, "Rob Tompkins" wrote: > Hello all, > > I would like to propose that we move commons-imaging to git in hopes of > doing that before the potential of releasing a 1.0. I figure that it would > be an easier migration with only a trunk to manage in getting it over there.

Re: [VOTE][LAZY] Move commons-imaging to git

+1 Gary On May 18, 2017 10:22 AM, "Rob Tompkins" wrote: > Hello all, > > I would like to propose that we move commons-imaging to git in hopes of > doing that before the potential of releasing a 1.0. I figure that it would > be an easier migration with only a trunk to manage in getting it over t

[VOTE][LAZY] Move commons-imaging to git

Hello all, I would like to propose that we move commons-imaging to git in hopes of doing that before the potential of releasing a 1.0. I figure that it would be an easier migration with only a trunk to manage in getting it over there. For this reason I’m calling a vote by lazy consensus for mov