+1  Thanks for the heads up.  We will do whatever we need to to help with
the transition.

On Sun, Dec 9, 2018 at 11:03 AM Otto Fowler <ottobackwa...@gmail.com> wrote:

> +1
> We will need jiras and PR’s for updating our scripts post move however.
> On December 9, 2018 at 06:32:44, Roy Lenferink (rlenfer...@apache.org)
> wrote:
> Hi folks,
> Checking the mail-archives I noticed the message below missed the
> dev@metron
> list [1].
> Does anyone have a problem with starting the process to migrate the
> existing Metron
> git-wip-us repos [2][3] to gitbox?
> This means integrated access and easy PRs on the repos (write access
> to the GitHub repos).
> I can't imagine anyone will say no, but we need to "document support
> for the decision" from a mailing list post, so, here it is.
> If there are no objections after 72 hours, I will create a ticket with
> INFRA for moving
> over the metron repositories to GitBox.
> - Roy
> [1]
> http://mail-archives.apache.org/mod_mbox/metron-dev/201812.mbox/browser
> [2] https://git-wip-us.apache.org/repos/asf?p=metron.git
> [3] https://git-wip-us.apache.org/repos/asf?p=metron-bro-plugin-kafka.git
> ---------- Forwarded message ---------
> From: Daniel Gruno <humbed...@apache.org>
> Date: vr 7 dec. 2018 om 17:53
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: us...@infra.apache.org <us...@infra.apache.org>
> 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 :-).

Reply via email to