Issue filed, but please continue to +1 (or -1 if you must) to show broad support for this initiative.
https://issues.apache.org/jira/browse/INFRA-17376 ----- Original Message ----- > From: "Eiri" <e...@eiri.ca> > To: dev@couchdb.apache.org > Sent: Friday, December 7, 2018 1:00:47 PM > Subject: Re: [NOTICE] Mandatory relocation of Apache git repositories on > git-wip-us.apache.org > > +1 > > > > On Dec 7, 2018, at 12:58, Joan Touzet <woh...@apache.org> wrote: > > > > Requesting lazy consensus - does anyone have a problem with them > > starting the process to mass-migrate all of the remaining repos to > > gitbox? > > > > This means integrated access and easy PRs on repos like > > couchdb-admin, > > couchdb-ets-lru, etc. > > > > I can't imagine anyone will say no, but we need "documented support > > for the decision" from a mailing list post, so, here it is. > > > > -Joan > > ----- Forwarded Message ----- > > From: "Daniel Gruno" <humbed...@apache.org> > > To: us...@infra.apache.org > > Sent: Friday, December 7, 2018 11:52:36 AM > > Subject: [NOTICE] Mandatory relocation of Apache git repositories > > on git-wip-us.apache.org > > > > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US > > PLEASE > > DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] > > > > Hello Apache projects, > > > > I am writing to you because you may have git repositories on the > > git-wip-us server, which is slated to be decommissioned in the > > coming > > months. All repositories will be moved to the new gitbox service > > which > > includes direct write access on github as well as the standard ASF > > commit access via gitbox.apache.org. > > > > ## Why this move? ## > > The move comes as a result of retiring the git-wip service, as the > > hardware it runs on is longing for retirement. In lieu of this, we > > have decided to consolidate the two services (git-wip and gitbox), > > to > > ease the management of our repository systems and future-proof the > > underlying hardware. The move is fully automated, and ideally, > > nothing > > will change in your workflow other than added features and access > > to > > GitHub. > > > > ## Timeframe for relocation ## > > Initially, we are asking that projects voluntarily request to move > > their repositories to gitbox, hence this email. The voluntary > > timeframe is between now and January 9th 2019, during which > > projects > > are free to either move over to gitbox or stay put on git-wip. > > After > > this phase, we will be requiring the remaining projects to move > > within > > one month, after which we will move the remaining projects over. > > > > To have your project moved in this initial phase, you will need: > > > > - Consensus in the project (documented via the mailing list) > > - File a JIRA ticket with INFRA to voluntarily move your project > > repos > > over to gitbox (as stated, this is highly automated and will take > > between a minute and an hour, depending on the size and number of > > your repositories) > > > > To sum up the preliminary timeline; > > > > - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) > > relocation > > - January 9th -> February 6th: Mandated (coordinated) relocation > > - February 7th: All remaining repositories are mass migrated. > > > > This timeline may change to accommodate various scenarios. > > > > ## Using GitHub with ASF repositories ## > > When your project has moved, you are free to use either the ASF > > repository system (gitbox.apache.org) OR GitHub for your > > development > > and code pushes. To be able to use GitHub, please follow the primer > > at: https://reference.apache.org/committer/github > > > > > > We appreciate your understanding of this issue, and hope that your > > project can coordinate voluntarily moving your repositories in a > > timely manner. > > > > All settings, such as commit mail targets, issue linking, PR > > notification schemes etc will automatically be migrated to gitbox > > as > > well. > > > > With regards, Daniel on behalf of ASF Infra. > > > > PS:For inquiries, please reply to us...@infra.apache.org, not your > > project's dev list :-). > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > >
