Here you are:
https://issues.apache.org/jira/browse/INFRA-17446 Andor On 12/14/18 07:11, Fangmin Lv wrote: > +1 for proactive move. Is there a Jira to track this? > > Best, > Fangmin > > On Thu, Dec 13, 2018 at 6:41 PM Norbert Kalmar <nkal...@cloudera.com.invalid> > wrote: > >> +1 (non-binding) for early voluntarily move. >> I will update the pom files, there is a PR on the POM's anyway, and they >> are WIP. >> >> Regards, >> Norbert >> >> On Thu, Dec 13, 2018 at 5:34 AM Michael Han <h...@apache.org> wrote: >> >>> +1 on voluntarily request to move. >>> >>> On Wed, Dec 12, 2018 at 11:36 AM Patrick Hunt <phu...@gmail.com> wrote: >>> >>>> Probably minor, but note there are some website pages that will also >> need >>>> to be updated: >>>> e.g. https://zookeeper.apache.org/git.html >>>> >>>> Patrick >>>> >>>> On Wed, Dec 12, 2018 at 10:58 AM Enrico Olivelli <eolive...@gmail.com> >>>> wrote: >>>> >>>>> +1 for moving to github now >>>>> >>>>> Enrico >>>>> >>>>> Il mer 12 dic 2018, 19:49 Tamas Penzes <tam...@cloudera.com.invalid> >>> ha >>>>> scritto: >>>>> >>>>>> Hi Patrick, >>>>>> >>>>>> Yes we have to upgrade the main pom.xml, just as the website and >> the >>>>>> documentation. >>>>>> Do we have to change git urls in old documentations as well? >> (People >>>>> might >>>>>> read them.) >>>>>> >>>>>> Thanks, Tamaas >>>>>> >>>>>> On Wed, Dec 12, 2018, 18:31 Patrick Hunt <ph...@apache.org wrote: >>>>>> >>>>>>> Proactive sounds good to me. Can we schedule something outside >> the >>>>>>> holidays? >>>>>>> >>>>>>> Aside from Jenkins is there anything else we need to worry about? >>>> e.g. >>>>> I >>>>>>> see a reference in pom.xml >>>>>>> >>>>>>> pom.xml >>>>>>> 63: <developerConnection>scm:git: >>>>>>> https://git-wip-us.apache.org/repos/asf/zookeeper.git >>>>>>> </developerConnection> >>>>>>> 64: <url> >>> https://git-wip-us.apache.org/repos/asf?p=zookeeper.git >>>>>> </url> >>>>>>> What's the impact wrt github.com and the Apache org? Will this >>>> enable >>>>>> use >>>>>>> to become admins at the same time? (greater control over the >>>>> issues/prs, >>>>>>> etc...) >>>>>>> >>>>>>> Patrick >>>>>>> >>>>>>> On Wed, Dec 12, 2018 at 9:07 AM Andor Molnar <an...@apache.org> >>>> wrote: >>>>>>>> Hi dev team, >>>>>>>> >>>>>>>> Have you seen this? >>>>>>>> >>>>>>>> >> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories >>>>>>>> < >>>>>>>> >> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories >>>>>>>> I think we should volunteer for a coordinated migration of >>>> ZooKeeper, >>>>>>>> although the project is not too big, so the impact of a forced >>>>> process >>>>>>>> probably wouldn’t be so much. >>>>>>>> >>>>>>>> There’re some benefits though: >>>>>>>> - We could move to GitBox earlier rather than later, so we >> could >>>> take >>>>>>>> advantage of GitHub write access for example, >>>>>>>> - Migration needs a write-lock in place during the process, so >> we >>>> can >>>>>>>> avoid some unfortunate surprises, >>>>>>>> - git-wip-us.apache.org <http://git-wip-us.apache.org/> will >>> have >>>>>> CNAMEs >>>>>>>> to gitbox, so it’ll be operational for some time, but the >>> read-only >>>>>>>> git.apache.org <http://git.apache.org/> will go away (not sure >>>> about >>>>>> the >>>>>>>> timing though), that we use in some of our Jenkins builds. It >>> would >>>>> be >>>>>>>> better to migrate Jenkins configs in a coordinated fashion >> rather >>>>> than >>>>>>> when >>>>>>>> the house is burning. >>>>>>>> >>>>>>>> There’re a bunch of unkowns in each project, hence Infra guys >>>>> recommend >>>>>>>> the coordinated way, but we need an agreement in the community, >>> so >>>>>> please >>>>>>>> share your thoughts. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Andor >>>>>>>> >>>>>>>> >>>>>>>> >>>>> -- >>>>> >>>>> >>>>> -- Enrico Olivelli >>>>>
