On Sun, Apr 22, 2018 at 10:34 AM, Matt Benson <mben...@apache.org> wrote:
> Shall we call a second vote to move all components to gitbox, then? > That would be fine with me. My understanding of such a VOTE is that we would not saddle ourselves with a ton of work ASAP but indicates our intent and future plans. We would likely still migrate components one or a few at a time as volunteers have time. Gary > > Matt > > On Sun, Apr 22, 2018 at 11:31 AM, Gary Gregory <garydgreg...@gmail.com> > wrote: > > > On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger < > > oliver.he...@oliver-heger.de > > > wrote: > > > > > > > > > > > Am 21.04.2018 um 22:31 schrieb Matt Sicker: > > > > I opened an infra ticket [1] to find out our options here. My > preferred > > > > option would be to migrate all of Commons over to gitbox for > > consistency. > > > > > > Many thanks, Matt! > > > > > > I would be +1 for a mass conversion, too. I think, nobody has > objections > > > against Git any more. The reason why some components still use SVN is > > > just inertia. > > > > > > > Moving all to Git will also allow us to review and clean up our release > > procedure documentation. > > > > It just feels like A LOT of busy work because we have so many components. > > > > Gary > > > > > > > Oliver > > > > > > > > > > > [1]: https://issues.apache.org/jira/browse/INFRA-16413 > > > > > > > > On 21 April 2018 at 12:23, Matt Benson <mben...@apache.org> wrote: > > > > > > > >> On Sat, Apr 21, 2018, 11:20 AM Rob Tompkins <chtom...@gmail.com> > > wrote: > > > >> > > > >>> > > > >>> > > > >>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger < > > > >> oliver.he...@oliver-heger.de> > > > >>> wrote: > > > >>>> > > > >>>> > > > >>>> > > > >>>> Am 20.04.2018 um 19:08 schrieb Matt Sicker: > > > >>>>> Wow, us "legacy" projects really need to keep up to date with > these > > > >>>>> requirements. GitBox, no CMS (I think we're using svnpubsub > > > >> everywhere, > > > >>> but > > > >>>>> this could also use gitpubsub with an asf-site branch), etc. > > > >>>> > > > >>>> Would it reduce overhead if we converted multiple components at > > once? > > > >>>> > > > >>>> I would like to move with [configuration] to git, but have > hesitated > > > so > > > >>>> far because I do not know the process in detail and what the > effort > > > is. > > > >>> > > > >>> If we wanted to do a (mildly) mass effort, I would be on board with > > > >>> helping. > > > >>> > > > >>> > > > >> Noble as that is (no sarcasm intended), is there any reason that > > > migrating > > > >> components *en masse* would be easier or otherwise preferable to > doing > > > so > > > >> "piecemeal"? > > > >> > > > >> Matt > > > >> > > > >> > > > >> -Rob > > > >>> > > > >>>> > > > >>>> Oliver > > > >>>> > > > >>>>> > > > >>>>> On 20 April 2018 at 10:13, Matt Benson <gudnabr...@gmail.com> > > wrote: > > > >>>>> > > > >>>>>> As Emmanuel suggested, Daniel Gruno confirmed for me that > "git-wip > > > is > > > >>>>>> slowly being deprecated." So the answer to the question > initially > > > >>> posed by > > > >>>>>> Ralph would seem in fact to be gitbox. > > > >>>>>> > > > >>>>>> Thanks, > > > >>>>>> Matt > > > >>>>>> > > > >>>>>> On Thu, Apr 19, 2018 at 11:57 PM, Romain Manni-Bucau < > > > >>>>>> rmannibu...@gmail.com> > > > >>>>>> wrote: > > > >>>>>> > > > >>>>>>> Gitbox is easier to use with github which makes contribs > easier. > > > >>>>>> Otherwise > > > >>>>>>> you dont see much difference as a git user. > > > >>>>>>> > > > >>>>>>> Le 20 avr. 2018 00:16, "Emmanuel Bourg" <ebo...@apache.org> a > > > >> écrit : > > > >>>>>>> > > > >>>>>>>> Le 20/04/2018 à 00:12, sebb a écrit : > > > >>>>>>>>> I suggest asking Infra whether they are both going to be > > > supported > > > >>>>>>>> longer term. > > > >>>>>>>> > > > >>>>>>>> FWIW when I migrated JEXL I had no other choice than using > > Gitbox. > > > >>> I'm > > > >>>>>>>> not sure Infra still accepts new git-wip repositories. > > > >>>>>>>> > > > >>>>>>>> Emmanuel Bourg > > > >>>>>>>> > > > >>>>>>>> ------------------------------------------------------------ > > > >> --------- > > > >>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > >>>>>>>> For additional commands, e-mail: dev-h...@commons.apache.org > > > >>>>>>>> > > > >>>>>>>> > > > >>>>>>> > > > >>>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>> > > > >>>> ------------------------------------------------------------ > > --------- > > > >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > <mailto: > > > >>> dev-unsubscr...@commons.apache.org> > > > >>>> For additional commands, e-mail: dev-h...@commons.apache.org > > <mailto: > > > >>> dev-h...@commons.apache.org> > > > >>> > > > >> > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > >
