You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Josh Thompson <jo...@ncsu.edu> on 2018/12/10 21:27:02 UTC
[DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
I know we're close to being able to cut a release, but this sounds like a
pretty seamless migration. It also gives us the benefit of being able to work
directly against GitHub, which would be a nice benefit. I'd like to go ahead
and submit a request to get us moved.
What do others think?
Josh
On Friday, December 7, 2018 11:52:36 AM EST Daniel Gruno wrote:
> [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 users@infra.apache.org, not your
> project's dev list :-).
--
-------------------------------
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at www.keyserver.net
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry - I forgot to follow up on this. We were moved a few days ago. To
switch the remote for your local repos from git-wip to gitbox, run the
following command. Replace <remote name> with the name you have for the git-
wip remote (might be origin, use "git remote -v" to look) and <userid> with
your ASF userid.
git remote set-url <remote name> https://<userid>@gitbox.apache.org/repos/asf/
vcl.git
You can also now work directly against GitHub if you enable 2 factor auth with
GitHub. Visit https://gitbox.apache.org/setup/ to set that up.
Josh
On Friday, December 14, 2018 12:12:51 PM EST Josh Thompson wrote:
> I just submitted the request to move to GitBox:
>
> https://issues.apache.org/jira/browse/INFRA-17445
>
> Josh
>
> On Monday, December 10, 2018 4:46:38 PM EST Mike Jennings wrote:
> > Let’s move
> >
> > On Mon, Dec 10, 2018 at 4:45 PM Aaron Peeler <aa...@ncsu.edu>
wrote:
> > > +1
> > >
> > > On Mon, Dec 10, 2018 at 4:27 PM Josh Thompson <jo...@ncsu.edu>
> > >
> > > wrote:
> > > > I know we're close to being able to cut a release, but this sounds
> > > > like
> > > > a
> > > > pretty seamless migration. It also gives us the benefit of being able
> > > > to
> > > > work
> > > > directly against GitHub, which would be a nice benefit. I'd like to
> > > > go
> > > > ahead
> > > > and submit a request to get us moved.
> > > >
> > > > What do others think?
> > > >
> > > > Josh
> > > >
> > > > On Friday, December 7, 2018 11:52:36 AM EST Daniel Gruno wrote:
> > > > > [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 users@infra.apache.org, not your
> > > > > project's dev list :-).
> > > >
> > > > --
> > > > -------------------------------
> > > > Josh Thompson
> > > > Systems Programmer
> > > > Virtual Computing Lab (VCL)
> > > > North Carolina State University
> > > >
> > > > Josh_Thompson@ncsu.edu
> > > > 919-515-5323
> > > >
> > > > my GPG/PGP key can be found at www.keyserver.net
> > > >
> > > > All electronic mail messages in connection with State business which
> > > > are sent to or received by this account are subject to the NC Public
> > > > Records Law and may be disclosed to third parties.
> > >
> > > --
> > > Aaron Peeler
> > > Manager, Platform Compute Services
> > > Office of Information Technology
> > > NC State University
> > >
> > > All electronic mail messages in connection with State business which are
> > > sent to or received by this account are subject to the NC Public Records
> > > Law and may be disclosed to third parties.
>
> --
> -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
>
> my GPG/PGP key can be found at pgp.mit.edu
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
- --
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQRMIdRtWXideTZDK31X8tBw1209AwUCXBvw6AAKCRBX8tBw1209
A2ptAJ9hmG9gWcIadrrFyj2JM9bW3ym0CACcDVjnv0gjU1uaPNIM53v1fbC2IE0=
=63pI
-----END PGP SIGNATURE-----
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just submitted the request to move to GitBox:
https://issues.apache.org/jira/browse/INFRA-17445
Josh
On Monday, December 10, 2018 4:46:38 PM EST Mike Jennings wrote:
> Let’s move
>
> On Mon, Dec 10, 2018 at 4:45 PM Aaron Peeler <aa...@ncsu.edu> wrote:
> > +1
> >
> > On Mon, Dec 10, 2018 at 4:27 PM Josh Thompson <jo...@ncsu.edu>
> >
> > wrote:
> > > I know we're close to being able to cut a release, but this sounds like
> > > a
> > > pretty seamless migration. It also gives us the benefit of being able
> > > to
> > > work
> > > directly against GitHub, which would be a nice benefit. I'd like to go
> > > ahead
> > > and submit a request to get us moved.
> > >
> > > What do others think?
> > >
> > > Josh
> > >
> > > On Friday, December 7, 2018 11:52:36 AM EST Daniel Gruno wrote:
> > > > [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 users@infra.apache.org, not your
> > > > project's dev list :-).
> > >
> > > --
> > > -------------------------------
> > > Josh Thompson
> > > Systems Programmer
> > > Virtual Computing Lab (VCL)
> > > North Carolina State University
> > >
> > > Josh_Thompson@ncsu.edu
> > > 919-515-5323
> > >
> > > my GPG/PGP key can be found at www.keyserver.net
> > >
> > > All electronic mail messages in connection with State business which
> > > are sent to or received by this account are subject to the NC Public
> > > Records Law and may be disclosed to third parties.
> >
> > --
> > Aaron Peeler
> > Manager, Platform Compute Services
> > Office of Information Technology
> > NC State University
> >
> > All electronic mail messages in connection with State business which are
> > sent to or received by this account are subject to the NC Public Records
> > Law and may be disclosed to third parties.
- --
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQRMIdRtWXideTZDK31X8tBw1209AwUCXBPkkwAKCRBX8tBw1209
A7LQAJ0bwfRnqEkRS33Wwyb0NvcbhZQG5ACbByg26aPh52UdwmsimudQAsg/cKM=
=MnfJ
-----END PGP SIGNATURE-----
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Mike Jennings <gm...@ncsu.edu>.
Let’s move
On Mon, Dec 10, 2018 at 4:45 PM Aaron Peeler <aa...@ncsu.edu> wrote:
> +1
>
> On Mon, Dec 10, 2018 at 4:27 PM Josh Thompson <jo...@ncsu.edu>
> wrote:
>
> > I know we're close to being able to cut a release, but this sounds like a
> > pretty seamless migration. It also gives us the benefit of being able to
> > work
> > directly against GitHub, which would be a nice benefit. I'd like to go
> > ahead
> > and submit a request to get us moved.
> >
> > What do others think?
> >
> > Josh
> >
> > On Friday, December 7, 2018 11:52:36 AM EST Daniel Gruno wrote:
> > > [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 users@infra.apache.org, not your
> > > project's dev list :-).
> >
> >
> > --
> > -------------------------------
> > Josh Thompson
> > Systems Programmer
> > Virtual Computing Lab (VCL)
> > North Carolina State University
> >
> > Josh_Thompson@ncsu.edu
> > 919-515-5323
> >
> > my GPG/PGP key can be found at www.keyserver.net
> >
> > All electronic mail messages in connection with State business which
> > are sent to or received by this account are subject to the NC Public
> > Records Law and may be disclosed to third parties.
>
>
>
> --
> Aaron Peeler
> Manager, Platform Compute Services
> Office of Information Technology
> NC State University
>
> All electronic mail messages in connection with State business which are
> sent to or received by this account are subject to the NC Public Records
> Law and may be disclosed to third parties.
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Aaron Peeler <aa...@ncsu.edu>.
+1
On Mon, Dec 10, 2018 at 4:27 PM Josh Thompson <jo...@ncsu.edu>
wrote:
> I know we're close to being able to cut a release, but this sounds like a
> pretty seamless migration. It also gives us the benefit of being able to
> work
> directly against GitHub, which would be a nice benefit. I'd like to go
> ahead
> and submit a request to get us moved.
>
> What do others think?
>
> Josh
>
> On Friday, December 7, 2018 11:52:36 AM EST Daniel Gruno wrote:
> > [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 users@infra.apache.org, not your
> > project's dev list :-).
>
>
> --
> -------------------------------
> Josh Thompson
> Systems Programmer
> Virtual Computing Lab (VCL)
> North Carolina State University
>
> Josh_Thompson@ncsu.edu
> 919-515-5323
>
> my GPG/PGP key can be found at www.keyserver.net
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
--
Aaron Peeler
Manager, Platform Compute Services
Office of Information Technology
NC State University
All electronic mail messages in connection with State business which are
sent to or received by this account are subject to the NC Public Records
Law and may be disclosed to third parties.