You are viewing a plain text version of this content. The canonical link for it is here.
Posted to odf-dev@incubator.apache.org by Daniel Gruno <hu...@apache.org> on 2018/12/07 16:52:36 UTC
[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 users@infra.apache.org, not your
project's dev list :-).
Re: [VOTE] Move Git repos from git-wip to gitbox
Posted by Woonsan Ko <wo...@apache.org>.
+1
Woonsan
On Mon, Dec 17, 2018 at 7:02 PM Daniel Dekany <dd...@apache.org> wrote:
>
> We should move the FreeMarker repos from git-wip to gitbox, as the
> mail quoted below says. As it's needed to demonstrate consensus (or
> else... it will be moved later regardless), I made this to be a vote.
> So especially PMC members, please reply!
>
> Do you agree that I will request all the FreeMarker repos that are on
> git-wip to be moved to gitbox in the coming days?
>
> My vote:
> +1
>
>
> Friday, December 7, 2018, 5:52:36 PM, 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 :-).
> >
> >
> >
>
> --
> Thanks,
> Daniel Dekany
>
Re: [VOTE] Move Git repos from git-wip to gitbox
Posted by Jacques Le Roux <ja...@les7arts.com>.
I agree, it's soon mandatory anyway
+1
Jacques
Le 18/12/2018 à 05:28, David E Jones a écrit :
> Seems odd to require a consensus vote if it is mandatory in a couple of
> months but sure, agreed.
>
> +1
>
> -David
>
>
> On Mon, Dec 17, 2018 at 2:02 AM Daniel Dekany <dd...@apache.org> wrote:
>
>> We should move the FreeMarker repos from git-wip to gitbox, as the
>> mail quoted below says. As it's needed to demonstrate consensus (or
>> else... it will be moved later regardless), I made this to be a vote.
>> So especially PMC members, please reply!
>>
>> Do you agree that I will request all the FreeMarker repos that are on
>> git-wip to be moved to gitbox in the coming days?
>>
>> My vote:
>> +1
>>
>>
>> Friday, December 7, 2018, 5:52:36 PM, 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 :-).
>>>
>>>
>>>
>> --
>> Thanks,
>> Daniel Dekany
>>
>>
Re: [VOTE] Move Git repos from git-wip to gitbox
Posted by David E Jones <de...@dejc.com>.
Seems odd to require a consensus vote if it is mandatory in a couple of
months but sure, agreed.
+1
-David
On Mon, Dec 17, 2018 at 2:02 AM Daniel Dekany <dd...@apache.org> wrote:
> We should move the FreeMarker repos from git-wip to gitbox, as the
> mail quoted below says. As it's needed to demonstrate consensus (or
> else... it will be moved later regardless), I made this to be a vote.
> So especially PMC members, please reply!
>
> Do you agree that I will request all the FreeMarker repos that are on
> git-wip to be moved to gitbox in the coming days?
>
> My vote:
> +1
>
>
> Friday, December 7, 2018, 5:52:36 PM, 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 :-).
> >
> >
> >
>
> --
> Thanks,
> Daniel Dekany
>
>
[VOTE] Move Git repos from git-wip to gitbox
Posted by Daniel Dekany <dd...@apache.org>.
We should move the FreeMarker repos from git-wip to gitbox, as the
mail quoted below says. As it's needed to demonstrate consensus (or
else... it will be moved later regardless), I made this to be a vote.
So especially PMC members, please reply!
Do you agree that I will request all the FreeMarker repos that are on
git-wip to be moved to gitbox in the coming days?
My vote:
+1
Friday, December 7, 2018, 5:52:36 PM, 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 :-).
>
>
>
--
Thanks,
Daniel Dekany
Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by Felix Cheung <fe...@hotmail.com>.
+1
Then let’s go ahead with this. I’m going to keep this open over the weekend and then open an INFRA ticket unless anyone has a concern.
________________________________
From: Prabhjyot Singh <pr...@apache.org>
Sent: Tuesday, December 11, 2018 9:22 AM
To: dev
Subject: Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
+1 for earlier.
On Tue, 11 Dec 2018 at 22:46, Felix Cheung <fe...@hotmail.com>
wrote:
> Yes that’s all it takes to migrate.
>
> (And committers to setup gitbox link)
>
> Any more thoughts from the community?
>
>
> ________________________________
> From: Jongyoul Lee <jo...@gmail.com>
> Sent: Tuesday, December 11, 2018 1:38 AM
> To: dev
> Subject: Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
> repositories on git-wip-us.apache.org
>
> We could create a ticket for the infra only, correct?
>
> On Mon, Dec 10, 2018 at 12:45 PM Jeff Zhang <zj...@gmail.com> wrote:
>
> > Definitely +1 for earlier, anyone volunteer for this ?
> >
> >
> > Jongyoul Lee <jo...@gmail.com> 于2018年12月10日周一 上午11:34写道：
> >
> > > I don't think we have any special reason not to move there.
> > >
> > > +1 for earlier
> > >
> > > On Mon, Dec 10, 2018 at 3:56 AM Felix Cheung <fe...@apache.org>
> > > wrote:
> > >
> > > > Hi community,
> > > >
> > > > The move to gitbox is coming. This does not affect Contributors -
> > mostly
> > > > how PR is merged. We could choose to voluntarily move early, or wait
> > till
> > > > later.
> > > >
> > > > So to discuss, should we move early?
> > > >
> > > >
> > > > ---------- Forwarded message ---------
> > > > From: Daniel Gruno <hu...@apache.org>
> > > > Date: Fri, Dec 7, 2018 at 8:54 AM
> > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > > git-wip-us.apache.org
> > > > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > > project's dev list :-).
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > >
> > >
> > > --
> > > 이종열, Jongyoul Lee, 李宗烈
> > > http://madeng.net
> > >
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>
--
Warm Regards,
Prabhjyot Singh
Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by Prabhjyot Singh <pr...@apache.org>.
+1 for earlier.
On Tue, 11 Dec 2018 at 22:46, Felix Cheung <fe...@hotmail.com>
wrote:
> Yes that’s all it takes to migrate.
>
> (And committers to setup gitbox link)
>
> Any more thoughts from the community?
>
>
> ________________________________
> From: Jongyoul Lee <jo...@gmail.com>
> Sent: Tuesday, December 11, 2018 1:38 AM
> To: dev
> Subject: Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
> repositories on git-wip-us.apache.org
>
> We could create a ticket for the infra only, correct?
>
> On Mon, Dec 10, 2018 at 12:45 PM Jeff Zhang <zj...@gmail.com> wrote:
>
> > Definitely +1 for earlier, anyone volunteer for this ?
> >
> >
> > Jongyoul Lee <jo...@gmail.com> 于2018年12月10日周一 上午11:34写道：
> >
> > > I don't think we have any special reason not to move there.
> > >
> > > +1 for earlier
> > >
> > > On Mon, Dec 10, 2018 at 3:56 AM Felix Cheung <fe...@apache.org>
> > > wrote:
> > >
> > > > Hi community,
> > > >
> > > > The move to gitbox is coming. This does not affect Contributors -
> > mostly
> > > > how PR is merged. We could choose to voluntarily move early, or wait
> > till
> > > > later.
> > > >
> > > > So to discuss, should we move early?
> > > >
> > > >
> > > > ---------- Forwarded message ---------
> > > > From: Daniel Gruno <hu...@apache.org>
> > > > Date: Fri, Dec 7, 2018 at 8:54 AM
> > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > > git-wip-us.apache.org
> > > > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > > project's dev list :-).
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > >
> > >
> > > --
> > > 이종열, Jongyoul Lee, 李宗烈
> > > http://madeng.net
> > >
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>
--
Warm Regards,
Prabhjyot Singh
Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by Felix Cheung <fe...@hotmail.com>.
Yes that’s all it takes to migrate.
(And committers to setup gitbox link)
Any more thoughts from the community?
________________________________
From: Jongyoul Lee <jo...@gmail.com>
Sent: Tuesday, December 11, 2018 1:38 AM
To: dev
Subject: Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
We could create a ticket for the infra only, correct?
On Mon, Dec 10, 2018 at 12:45 PM Jeff Zhang <zj...@gmail.com> wrote:
> Definitely +1 for earlier, anyone volunteer for this ?
>
>
> Jongyoul Lee <jo...@gmail.com> 于2018年12月10日周一 上午11:34写道：
>
> > I don't think we have any special reason not to move there.
> >
> > +1 for earlier
> >
> > On Mon, Dec 10, 2018 at 3:56 AM Felix Cheung <fe...@apache.org>
> > wrote:
> >
> > > Hi community,
> > >
> > > The move to gitbox is coming. This does not affect Contributors -
> mostly
> > > how PR is merged. We could choose to voluntarily move early, or wait
> till
> > > later.
> > >
> > > So to discuss, should we move early?
> > >
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <hu...@apache.org>
> > > Date: Fri, Dec 7, 2018 at 8:54 AM
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > git-wip-us.apache.org
> > > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > project's dev list :-).
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by Jongyoul Lee <jo...@gmail.com>.
We could create a ticket for the infra only, correct?
On Mon, Dec 10, 2018 at 12:45 PM Jeff Zhang <zj...@gmail.com> wrote:
> Definitely +1 for earlier, anyone volunteer for this ?
>
>
> Jongyoul Lee <jo...@gmail.com> 于2018年12月10日周一 上午11:34写道：
>
> > I don't think we have any special reason not to move there.
> >
> > +1 for earlier
> >
> > On Mon, Dec 10, 2018 at 3:56 AM Felix Cheung <fe...@apache.org>
> > wrote:
> >
> > > Hi community,
> > >
> > > The move to gitbox is coming. This does not affect Contributors -
> mostly
> > > how PR is merged. We could choose to voluntarily move early, or wait
> till
> > > later.
> > >
> > > So to discuss, should we move early?
> > >
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <hu...@apache.org>
> > > Date: Fri, Dec 7, 2018 at 8:54 AM
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > git-wip-us.apache.org
> > > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > project's dev list :-).
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by Jeff Zhang <zj...@gmail.com>.
Definitely +1 for earlier, anyone volunteer for this ?
Jongyoul Lee <jo...@gmail.com> 于2018年12月10日周一 上午11:34写道：
> I don't think we have any special reason not to move there.
>
> +1 for earlier
>
> On Mon, Dec 10, 2018 at 3:56 AM Felix Cheung <fe...@apache.org>
> wrote:
>
> > Hi community,
> >
> > The move to gitbox is coming. This does not affect Contributors - mostly
> > how PR is merged. We could choose to voluntarily move early, or wait till
> > later.
> >
> > So to discuss, should we move early?
> >
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <hu...@apache.org>
> > Date: Fri, Dec 7, 2018 at 8:54 AM
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org
> > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > project's dev list :-).
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>
--
Best Regards
Jeff Zhang
Re: [DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by Jongyoul Lee <jo...@gmail.com>.
I don't think we have any special reason not to move there.
+1 for earlier
On Mon, Dec 10, 2018 at 3:56 AM Felix Cheung <fe...@apache.org> wrote:
> Hi community,
>
> The move to gitbox is coming. This does not affect Contributors - mostly
> how PR is merged. We could choose to voluntarily move early, or wait till
> later.
>
> So to discuss, should we move early?
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 8:54 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
[DISCUSS] Fwd: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by Felix Cheung <fe...@apache.org>.
Hi community,
The move to gitbox is coming. This does not affect Contributors - mostly
how PR is merged. We could choose to voluntarily move early, or wait till
later.
So to discuss, should we move early?
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 8:54 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Steve Varnau <st...@esgyn.com>.
Yes, this does affect us. We discussed moving to gitbox some time ago, but at the time decided to wait until we graduated to TLP. But I don't think it was raised again since graduation.
The main impact is that the URL of the trafodion repo will change again. So anyone that has a workspace will need to update the references to point to the new location. I was thinking this would affect all developer work-spaces, but looking at it again, I think it only affects references to git-wip-us server (the apache repo). Anyone referring to the github read-only mirror would be unaffected. So, primarily committers are affected.
There is some bit of disruption. We just need to decide when we want to schedule it or wait for the mass migration.
There are definite benefits for the committers, since we would be able to use github interface to merge changes rather than the manual git command line that we use now. To use that benefit, the committers must take steps to link their apache and github IDs together, including using 2-factor authentication with github.
I have already linked my IDs. The github 2-factor authentication sounds like a pain, but after the initial set-up, is no problem at all. I only need to do extra authentication when using a new device to access github.
--Steve
> -----Original Message-----
> From: Pierre Smits <pi...@apache.org>
> Sent: Friday, December 7, 2018 11:51 PM
> To: dev@trafodion.apache.org
> Subject: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
>
> Hi All,
>
> I noticed the posting below. Does this affect us?
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion <https://trafodion.apache.org>, Vice President*
> *Apache Directory <https://directory.apache.org>, PMC Member*
> Apache Incubator <https://incubator.apache.org>, committer
> *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
> since 2008*
> Apache Steve <https://steve.apache.org>, committer
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 5:52 PM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Pierre Smits <pi...@apache.org>.
Hi All,
I noticed the posting below. Does this affect us?
Best regards,
Pierre Smits
*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
since 2008*
Apache Steve <https://steve.apache.org>, committer
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 5:52 PM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Dave <sn...@gmail.com>.
Requested the migration here:
https://issues.apache.org/jira/browse/INFRA-17451
- Dave
On Tue, Dec 11, 2018 at 2:58 PM Dave <sn...@gmail.com> wrote:
> I'd like to move Roller to the new *gitbox.apache.org
> <http://gitbox.apache.org>* service so that we have write access to our
> GitHub repo and can accept Pull Requests in the normal way. Please speak
> up if you have concerns or are opposed to this. I'll hold off on filing a
> JIRA ticket until this weekend.
>
> Thanks,
> Dave
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 11:53 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Dave <sn...@gmail.com>.
I'd like to move Roller to the new *gitbox.apache.org
<http://gitbox.apache.org>* service so that we have write access to our
GitHub repo and can accept Pull Requests in the normal way. Please speak
up if you have concerns or are opposed to this. I'll hold off on filing a
JIRA ticket until this weekend.
Thanks,
Dave
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 11:53 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Dmitriy Pavlov <dp...@apache.org>.
Folks, Incubator finished its migration to GitBox -
https://gitbox.apache.org/repos/asf?p=incubator.git
Because it seems majority don't care too much about migration I'm going to
consider this decision approved by silence and could be made by lazy
consensus in 72 hours.
вт, 11 дек. 2018 г. в 19:25, Alexey Goncharuk <al...@gmail.com>:
> Given that there is no option to stay on the old repository and
> mass-migration is scheduled for Feb, 7th, I think it is better to prepare
> and move the repository before the date.
>
> As far as I understand, from developers standpoint we only need to change
> the git remote entry. Petr, Sergey, can you asses what changes are need to
> be done in order to support this migration for TC and release procedure?
>
> вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dp...@apache.org>:
>
> > Hi All,
> >
> > The Apache Ignite still has a repository on git-wip-us for its code, as
> > well, for release.
> >
> > Does anyone have a problem with moving over the Ignite git-wip-us
> > repository to gitbox voluntarily? This means integrated access and easy
> PRs
> > (write access to the GitHub repo).
> >
> > We need to document support for the decision from a mailing list post, so
> > here it is.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dp...@apache.org>:
> >
> > > Hi Igniters,
> > >
> > > What do you think about the voluntary migration of project repositories
> > > from git-wip to GitBox? (See details in the forwarded email.)
> > >
> > > Redirection of emails originated by PR actions to notifications@ seems
> > to
> > > be almost finished, so email flood issue seems to be already solved for
> > dev@
> > > .
> > >
> > > It is up to us to decide if we would like to migrate sooner. Later all
> > > repositories will be migrated anyway.
> > >
> > > Affected repositories
> > > - Ignite Release
> > > - Ignite
> > >
> > > Please share your opinion.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <hu...@apache.org>
> > > Date: пт, 7 дек. 2018 г. в 19:52
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > git-wip-us.apache.org
> > > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > project's dev list :-).
> > >
> > >
> > >
> >
>
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Dmitriy Pavlov <dp...@apache.org>.
Done for the wiki, we need update site.
ср, 9 янв. 2019 г. в 12:28, Andrey Mashenkov <an...@gmail.com>:
> Hi Dmitry,
>
> Looks like repository has been transferred to GitBox,
> but for now we still have incorrect links on wiki and ignite web site.
>
> I've created a ticket [1]. Can someone fix this?
>
> https://issues.apache.org/jira/browse/IGNITE-10863
>
> On Sun, Dec 30, 2018 at 1:28 AM Dmitriy Pavlov <dp...@apache.org> wrote:
>
>> Hi Igniters,
>>
>> Thanks to Peter and Alexey for sharing their opinion.
>>
>> I've filed https://issues.apache.org/jira/browse/INFRA-17516 to migrate.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> чт, 13 дек. 2018 г. в 21:47, Peter Ivanov <pi...@gridgain.com>:
>>
>> > There will be no problem with TC, as we use GitHub as main VCS root,
>> using
>> > ASF only for release (which I will reconfigure during release builds
>> > refactoring and optimisations for AI 2.8).
>> >
>> >
>> > > On 11 Dec 2018, at 19:25, Alexey Goncharuk <
>> alexey.goncharuk@gmail.com>
>> > wrote:
>> > >
>> > > Given that there is no option to stay on the old repository and
>> > mass-migration is scheduled for Feb, 7th, I think it is better to
>> prepare
>> > and move the repository before the date.
>> > >
>> > > As far as I understand, from developers standpoint we only need to
>> > change the git remote entry. Petr, Sergey, can you asses what changes
>> are
>> > need to be done in order to support this migration for TC and release
>> > procedure?
>> > >
>> > > вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dpavlov@apache.org
>> <mailto:
>> > dpavlov@apache.org>>:
>> > > Hi All,
>> > >
>> > > The Apache Ignite still has a repository on git-wip-us for its code,
>> as
>> > > well, for release.
>> > >
>> > > Does anyone have a problem with moving over the Ignite git-wip-us
>> > > repository to gitbox voluntarily? This means integrated access and
>> easy
>> > PRs
>> > > (write access to the GitHub repo).
>> > >
>> > > We need to document support for the decision from a mailing list
>> post, so
>> > > here it is.
>> > >
>> > > Sincerely,
>> > > Dmitriy Pavlov
>> > >
>> > > сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org
>> <mailto:
>> > dpavlov@apache.org>>:
>> > >
>> > > > Hi Igniters,
>> > > >
>> > > > What do you think about the voluntary migration of project
>> repositories
>> > > > from git-wip to GitBox? (See details in the forwarded email.)
>> > > >
>> > > > Redirection of emails originated by PR actions to notifications@
>> > seems to
>> > > > be almost finished, so email flood issue seems to be already solved
>> > for dev@
>> > > > .
>> > > >
>> > > > It is up to us to decide if we would like to migrate sooner. Later
>> all
>> > > > repositories will be migrated anyway.
>> > > >
>> > > > Affected repositories
>> > > > - Ignite Release
>> > > > - Ignite
>> > > >
>> > > > Please share your opinion.
>> > > >
>> > > > Sincerely,
>> > > > Dmitriy Pavlov
>> > > >
>> > > > ---------- Forwarded message ---------
>> > > > From: Daniel Gruno <humbedooh@apache.org <mailto:
>> humbedooh@apache.org
>> > >>
>> > > > Date: пт, 7 дек. 2018 г. в 19:52
>> > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>> > > > git-wip-us.apache.org <http://git-wip-us.apache.org/>
>> > > > To: users@infra.apache.org <ma...@infra.apache.org> <
>> > users@infra.apache.org <ma...@infra.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 <http://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 <http://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 <
>> > 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 <mailto:
>> > users@infra.apache.org>, not your
>> > > > project's dev list :-).
>> > > >
>> > > >
>> > > >
>> >
>> >
>>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi Dmitry,
Looks like repository has been transferred to GitBox,
but for now we still have incorrect links on wiki and ignite web site.
I've created a ticket [1]. Can someone fix this?
https://issues.apache.org/jira/browse/IGNITE-10863
On Sun, Dec 30, 2018 at 1:28 AM Dmitriy Pavlov <dp...@apache.org> wrote:
> Hi Igniters,
>
> Thanks to Peter and Alexey for sharing their opinion.
>
> I've filed https://issues.apache.org/jira/browse/INFRA-17516 to migrate.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 13 дек. 2018 г. в 21:47, Peter Ivanov <pi...@gridgain.com>:
>
> > There will be no problem with TC, as we use GitHub as main VCS root,
> using
> > ASF only for release (which I will reconfigure during release builds
> > refactoring and optimisations for AI 2.8).
> >
> >
> > > On 11 Dec 2018, at 19:25, Alexey Goncharuk <alexey.goncharuk@gmail.com
> >
> > wrote:
> > >
> > > Given that there is no option to stay on the old repository and
> > mass-migration is scheduled for Feb, 7th, I think it is better to prepare
> > and move the repository before the date.
> > >
> > > As far as I understand, from developers standpoint we only need to
> > change the git remote entry. Petr, Sergey, can you asses what changes are
> > need to be done in order to support this migration for TC and release
> > procedure?
> > >
> > > вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dpavlov@apache.org
> <mailto:
> > dpavlov@apache.org>>:
> > > Hi All,
> > >
> > > The Apache Ignite still has a repository on git-wip-us for its code, as
> > > well, for release.
> > >
> > > Does anyone have a problem with moving over the Ignite git-wip-us
> > > repository to gitbox voluntarily? This means integrated access and easy
> > PRs
> > > (write access to the GitHub repo).
> > >
> > > We need to document support for the decision from a mailing list post,
> so
> > > here it is.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org
> <mailto:
> > dpavlov@apache.org>>:
> > >
> > > > Hi Igniters,
> > > >
> > > > What do you think about the voluntary migration of project
> repositories
> > > > from git-wip to GitBox? (See details in the forwarded email.)
> > > >
> > > > Redirection of emails originated by PR actions to notifications@
> > seems to
> > > > be almost finished, so email flood issue seems to be already solved
> > for dev@
> > > > .
> > > >
> > > > It is up to us to decide if we would like to migrate sooner. Later
> all
> > > > repositories will be migrated anyway.
> > > >
> > > > Affected repositories
> > > > - Ignite Release
> > > > - Ignite
> > > >
> > > > Please share your opinion.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > ---------- Forwarded message ---------
> > > > From: Daniel Gruno <humbedooh@apache.org <mailto:
> humbedooh@apache.org
> > >>
> > > > Date: пт, 7 дек. 2018 г. в 19:52
> > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > > git-wip-us.apache.org <http://git-wip-us.apache.org/>
> > > > To: users@infra.apache.org <ma...@infra.apache.org> <
> > users@infra.apache.org <ma...@infra.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 <http://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 <http://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 <
> > 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 <mailto:
> > users@infra.apache.org>, not your
> > > > project's dev list :-).
> > > >
> > > >
> > > >
> >
> >
>
--
Best regards,
Andrey V. Mashenkov
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Dmitriy Pavlov <dp...@apache.org>.
Hi Igniters,
the main Git repository for Apache Ignite and Ignite release have been
migrated to GitBox.
New Remotes:
https://gitbox.apache.org/repos/asf/ignite.git
https://gitbox.apache.org/repos/asf?p=ignite-release.git
Committers, please update your remotes.
Please share your vision if we can for now simply delete empty
https://git-wip-us.apache.org/repos/asf?p=ignite-doc.git
Sincerely,
Dmitriy Pavlov
вс, 30 дек. 2018 г. в 01:28, Dmitriy Pavlov <dp...@apache.org>:
> Hi Igniters,
>
> Thanks to Peter and Alexey for sharing their opinion.
>
> I've filed https://issues.apache.org/jira/browse/INFRA-17516 to migrate.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 13 дек. 2018 г. в 21:47, Peter Ivanov <pi...@gridgain.com>:
>
>> There will be no problem with TC, as we use GitHub as main VCS root,
>> using ASF only for release (which I will reconfigure during release builds
>> refactoring and optimisations for AI 2.8).
>>
>>
>> > On 11 Dec 2018, at 19:25, Alexey Goncharuk <al...@gmail.com>
>> wrote:
>> >
>> > Given that there is no option to stay on the old repository and
>> mass-migration is scheduled for Feb, 7th, I think it is better to prepare
>> and move the repository before the date.
>> >
>> > As far as I understand, from developers standpoint we only need to
>> change the git remote entry. Petr, Sergey, can you asses what changes are
>> need to be done in order to support this migration for TC and release
>> procedure?
>> >
>> > вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dpavlov@apache.org
>> <ma...@apache.org>>:
>> > Hi All,
>> >
>> > The Apache Ignite still has a repository on git-wip-us for its code, as
>> > well, for release.
>> >
>> > Does anyone have a problem with moving over the Ignite git-wip-us
>> > repository to gitbox voluntarily? This means integrated access and easy
>> PRs
>> > (write access to the GitHub repo).
>> >
>> > We need to document support for the decision from a mailing list post,
>> so
>> > here it is.
>> >
>> > Sincerely,
>> > Dmitriy Pavlov
>> >
>> > сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org <mailto:
>> dpavlov@apache.org>>:
>> >
>> > > Hi Igniters,
>> > >
>> > > What do you think about the voluntary migration of project
>> repositories
>> > > from git-wip to GitBox? (See details in the forwarded email.)
>> > >
>> > > Redirection of emails originated by PR actions to notifications@
>> seems to
>> > > be almost finished, so email flood issue seems to be already solved
>> for dev@
>> > > .
>> > >
>> > > It is up to us to decide if we would like to migrate sooner. Later all
>> > > repositories will be migrated anyway.
>> > >
>> > > Affected repositories
>> > > - Ignite Release
>> > > - Ignite
>> > >
>> > > Please share your opinion.
>> > >
>> > > Sincerely,
>> > > Dmitriy Pavlov
>> > >
>> > > ---------- Forwarded message ---------
>> > > From: Daniel Gruno <humbedooh@apache.org <mailto:humbedooh@apache.org
>> >>
>> > > Date: пт, 7 дек. 2018 г. в 19:52
>> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>> > > git-wip-us.apache.org <http://git-wip-us.apache.org/>
>> > > To: users@infra.apache.org <ma...@infra.apache.org> <
>> users@infra.apache.org <ma...@infra.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 <http://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 <http://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 <
>> 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 <mailto:
>> users@infra.apache.org>, not your
>> > > project's dev list :-).
>> > >
>> > >
>> > >
>>
>>
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Dmitriy Pavlov <dp...@apache.org>.
Hi Igniters,
Thanks to Peter and Alexey for sharing their opinion.
I've filed https://issues.apache.org/jira/browse/INFRA-17516 to migrate.
Sincerely,
Dmitriy Pavlov
чт, 13 дек. 2018 г. в 21:47, Peter Ivanov <pi...@gridgain.com>:
> There will be no problem with TC, as we use GitHub as main VCS root, using
> ASF only for release (which I will reconfigure during release builds
> refactoring and optimisations for AI 2.8).
>
>
> > On 11 Dec 2018, at 19:25, Alexey Goncharuk <al...@gmail.com>
> wrote:
> >
> > Given that there is no option to stay on the old repository and
> mass-migration is scheduled for Feb, 7th, I think it is better to prepare
> and move the repository before the date.
> >
> > As far as I understand, from developers standpoint we only need to
> change the git remote entry. Petr, Sergey, can you asses what changes are
> need to be done in order to support this migration for TC and release
> procedure?
> >
> > вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dpavlov@apache.org <mailto:
> dpavlov@apache.org>>:
> > Hi All,
> >
> > The Apache Ignite still has a repository on git-wip-us for its code, as
> > well, for release.
> >
> > Does anyone have a problem with moving over the Ignite git-wip-us
> > repository to gitbox voluntarily? This means integrated access and easy
> PRs
> > (write access to the GitHub repo).
> >
> > We need to document support for the decision from a mailing list post, so
> > here it is.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org <mailto:
> dpavlov@apache.org>>:
> >
> > > Hi Igniters,
> > >
> > > What do you think about the voluntary migration of project repositories
> > > from git-wip to GitBox? (See details in the forwarded email.)
> > >
> > > Redirection of emails originated by PR actions to notifications@
> seems to
> > > be almost finished, so email flood issue seems to be already solved
> for dev@
> > > .
> > >
> > > It is up to us to decide if we would like to migrate sooner. Later all
> > > repositories will be migrated anyway.
> > >
> > > Affected repositories
> > > - Ignite Release
> > > - Ignite
> > >
> > > Please share your opinion.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <humbedooh@apache.org <mailto:humbedooh@apache.org
> >>
> > > Date: пт, 7 дек. 2018 г. в 19:52
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > git-wip-us.apache.org <http://git-wip-us.apache.org/>
> > > To: users@infra.apache.org <ma...@infra.apache.org> <
> users@infra.apache.org <ma...@infra.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 <http://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 <http://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 <
> 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 <mailto:
> users@infra.apache.org>, not your
> > > project's dev list :-).
> > >
> > >
> > >
>
>
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Peter Ivanov <pi...@gridgain.com>.
There will be no problem with TC, as we use GitHub as main VCS root, using ASF only for release (which I will reconfigure during release builds refactoring and optimisations for AI 2.8).
> On 11 Dec 2018, at 19:25, Alexey Goncharuk <al...@gmail.com> wrote:
>
> Given that there is no option to stay on the old repository and mass-migration is scheduled for Feb, 7th, I think it is better to prepare and move the repository before the date.
>
> As far as I understand, from developers standpoint we only need to change the git remote entry. Petr, Sergey, can you asses what changes are need to be done in order to support this migration for TC and release procedure?
>
> вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dpavlov@apache.org <ma...@apache.org>>:
> Hi All,
>
> The Apache Ignite still has a repository on git-wip-us for its code, as
> well, for release.
>
> Does anyone have a problem with moving over the Ignite git-wip-us
> repository to gitbox voluntarily? This means integrated access and easy PRs
> (write access to the GitHub repo).
>
> We need to document support for the decision from a mailing list post, so
> here it is.
>
> Sincerely,
> Dmitriy Pavlov
>
> сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org <ma...@apache.org>>:
>
> > Hi Igniters,
> >
> > What do you think about the voluntary migration of project repositories
> > from git-wip to GitBox? (See details in the forwarded email.)
> >
> > Redirection of emails originated by PR actions to notifications@ seems to
> > be almost finished, so email flood issue seems to be already solved for dev@
> > .
> >
> > It is up to us to decide if we would like to migrate sooner. Later all
> > repositories will be migrated anyway.
> >
> > Affected repositories
> > - Ignite Release
> > - Ignite
> >
> > Please share your opinion.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <humbedooh@apache.org <ma...@apache.org>>
> > Date: пт, 7 дек. 2018 г. в 19:52
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org <http://git-wip-us.apache.org/>
> > To: users@infra.apache.org <ma...@infra.apache.org> <users@infra.apache.org <ma...@infra.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 <http://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 <http://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 <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 <ma...@infra.apache.org>, not your
> > project's dev list :-).
> >
> >
> >
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Alexey Goncharuk <al...@gmail.com>.
Given that there is no option to stay on the old repository and
mass-migration is scheduled for Feb, 7th, I think it is better to prepare
and move the repository before the date.
As far as I understand, from developers standpoint we only need to change
the git remote entry. Petr, Sergey, can you asses what changes are need to
be done in order to support this migration for TC and release procedure?
вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dp...@apache.org>:
> Hi All,
>
> The Apache Ignite still has a repository on git-wip-us for its code, as
> well, for release.
>
> Does anyone have a problem with moving over the Ignite git-wip-us
> repository to gitbox voluntarily? This means integrated access and easy PRs
> (write access to the GitHub repo).
>
> We need to document support for the decision from a mailing list post, so
> here it is.
>
> Sincerely,
> Dmitriy Pavlov
>
> сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dp...@apache.org>:
>
> > Hi Igniters,
> >
> > What do you think about the voluntary migration of project repositories
> > from git-wip to GitBox? (See details in the forwarded email.)
> >
> > Redirection of emails originated by PR actions to notifications@ seems
> to
> > be almost finished, so email flood issue seems to be already solved for
> dev@
> > .
> >
> > It is up to us to decide if we would like to migrate sooner. Later all
> > repositories will be migrated anyway.
> >
> > Affected repositories
> > - Ignite Release
> > - Ignite
> >
> > Please share your opinion.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <hu...@apache.org>
> > Date: пт, 7 дек. 2018 г. в 19:52
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org
> > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > project's dev list :-).
> >
> >
> >
>
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Dmitriy Pavlov <dp...@apache.org>.
Hi All,
The Apache Ignite still has a repository on git-wip-us for its code, as
well, for release.
Does anyone have a problem with moving over the Ignite git-wip-us
repository to gitbox voluntarily? This means integrated access and easy PRs
(write access to the GitHub repo).
We need to document support for the decision from a mailing list post, so
here it is.
Sincerely,
Dmitriy Pavlov
сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dp...@apache.org>:
> Hi Igniters,
>
> What do you think about the voluntary migration of project repositories
> from git-wip to GitBox? (See details in the forwarded email.)
>
> Redirection of emails originated by PR actions to notifications@ seems to
> be almost finished, so email flood issue seems to be already solved for dev@
> .
>
> It is up to us to decide if we would like to migrate sooner. Later all
> repositories will be migrated anyway.
>
> Affected repositories
> - Ignite Release
> - Ignite
>
> Please share your opinion.
>
> Sincerely,
> Dmitriy Pavlov
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: пт, 7 дек. 2018 г. в 19:52
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
[DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Dmitriy Pavlov <dp...@apache.org>.
Hi Igniters,
What do you think about the voluntary migration of project repositories
from git-wip to GitBox? (See details in the forwarded email.)
Redirection of emails originated by PR actions to notifications@ seems to
be almost finished, so email flood issue seems to be already solved for dev@
.
It is up to us to decide if we would like to migrate sooner. Later all
repositories will be migrated anyway.
Affected repositories
- Ignite Release
- Ignite
Please share your opinion.
Sincerely,
Dmitriy Pavlov
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: пт, 7 дек. 2018 г. в 19:52
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Francis Chuang <fr...@apache.org>.
I am also +1 on early move.
On 8/12/2018 5:51 am, Julian Hyde wrote:
> +1 on early move
>
> It should be low-impact; probably only committers are using git-wip-us.apache.org <http://git-wip-us.apache.org/> anyway, everyone else is using github.com/apache/calcite.
>
>> On Dec 7, 2018, at 10:41 AM, Kevin Risden <kr...@apache.org> wrote:
>>
>> I'm +1 in moving before being forced to. I know a few other projects have
>> moved and didn't seem to cause too much harm. Would be good to do between
>> releases :)
>>
>> Kevin Risden
>>
>>
>> On Fri, Dec 7, 2018 at 1:36 PM Michael Mior <mm...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> We have a decision to make regarding repository hosting. INFRA is retiring
>>> git-wip-us.apache.org which Calcite is currently using. We're going to
>>> have
>>> to move at some point in the next few months to gitbox.apache.org. The
>>> question is whether we volunteer to do so relatively soon before we'll be
>>> required to move. (More details in the message below.) My vote would be to
>>> volunteer and get the move over with once the latest release is complete.
>>> This move will have the nice advantage that we'll have write access to
>>> GitHub directly.
>>>
>>> Anyway, I'd suggest we come to a decision on our strategy relatively soon
>>> so we can start thinking about what might need to change and when. Thanks!
>>>
>>> --
>>> Michael Mior
>>> mmior@apache.org
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: Daniel Gruno <hu...@apache.org>
>>> Date: ven. 7 déc. 2018 à 11:54
>>> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>>> git-wip-us.apache.org
>>> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
>>> project's dev list :-).
>>>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Julian Hyde <jh...@apache.org>.
+1 on early move
It should be low-impact; probably only committers are using git-wip-us.apache.org <http://git-wip-us.apache.org/> anyway, everyone else is using github.com/apache/calcite.
> On Dec 7, 2018, at 10:41 AM, Kevin Risden <kr...@apache.org> wrote:
>
> I'm +1 in moving before being forced to. I know a few other projects have
> moved and didn't seem to cause too much harm. Would be good to do between
> releases :)
>
> Kevin Risden
>
>
> On Fri, Dec 7, 2018 at 1:36 PM Michael Mior <mm...@apache.org> wrote:
>
>> Hi all,
>>
>> We have a decision to make regarding repository hosting. INFRA is retiring
>> git-wip-us.apache.org which Calcite is currently using. We're going to
>> have
>> to move at some point in the next few months to gitbox.apache.org. The
>> question is whether we volunteer to do so relatively soon before we'll be
>> required to move. (More details in the message below.) My vote would be to
>> volunteer and get the move over with once the latest release is complete.
>> This move will have the nice advantage that we'll have write access to
>> GitHub directly.
>>
>> Anyway, I'd suggest we come to a decision on our strategy relatively soon
>> so we can start thinking about what might need to change and when. Thanks!
>>
>> --
>> Michael Mior
>> mmior@apache.org
>>
>>
>> ---------- Forwarded message ---------
>> From: Daniel Gruno <hu...@apache.org>
>> Date: ven. 7 déc. 2018 à 11:54
>> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>> git-wip-us.apache.org
>> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
>> project's dev list :-).
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Kevin Risden <kr...@apache.org>.
I'm +1 in moving before being forced to. I know a few other projects have
moved and didn't seem to cause too much harm. Would be good to do between
releases :)
Kevin Risden
On Fri, Dec 7, 2018 at 1:36 PM Michael Mior <mm...@apache.org> wrote:
> Hi all,
>
> We have a decision to make regarding repository hosting. INFRA is retiring
> git-wip-us.apache.org which Calcite is currently using. We're going to
> have
> to move at some point in the next few months to gitbox.apache.org. The
> question is whether we volunteer to do so relatively soon before we'll be
> required to move. (More details in the message below.) My vote would be to
> volunteer and get the move over with once the latest release is complete.
> This move will have the nice advantage that we'll have write access to
> GitHub directly.
>
> Anyway, I'd suggest we come to a decision on our strategy relatively soon
> so we can start thinking about what might need to change and when. Thanks!
>
> --
> Michael Mior
> mmior@apache.org
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: ven. 7 déc. 2018 à 11:54
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Michael Mior <mm...@apache.org>.
Hi all,
We have a decision to make regarding repository hosting. INFRA is retiring
git-wip-us.apache.org which Calcite is currently using. We're going to have
to move at some point in the next few months to gitbox.apache.org. The
question is whether we volunteer to do so relatively soon before we'll be
required to move. (More details in the message below.) My vote would be to
volunteer and get the move over with once the latest release is complete.
This move will have the nice advantage that we'll have write access to
GitHub directly.
Anyway, I'd suggest we come to a decision on our strategy relatively soon
so we can start thinking about what might need to change and when. Thanks!
--
Michael Mior
mmior@apache.org
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: ven. 7 déc. 2018 à 11:54
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Christopher <ct...@apache.org>.
On Fri, Dec 7, 2018 at 12:29 PM Ismael Juma <is...@juma.me.uk> wrote:
>
> Hi Daniel,
>
> We moved to Gitbox a while back for kafka and kafka-site. Which repository is still using git-wip-us.apache.org?
>
> Ismael
None of yours. The message was sent to every PMC.
I believe https://git1-us-west.apache.org/repos/asf has a list of
affected repos still on git-wip.
>
> On Fri, Dec 7, 2018 at 8:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Ismael Juma <is...@juma.me.uk>.
Thanks Daniel and Christopher! My bad for missing the header. :)
Ismael
On Fri, Dec 7, 2018, 9:31 AM Daniel Gruno <humbedooh@apache.org wrote:
> On 12/7/18 6:28 PM, Ismael Juma wrote:
> > Hi Daniel,
> >
> > We moved to Gitbox a while back for kafka and kafka-site. Which
> > repository is still using git-wip-us.apache.org
> > <http://git-wip-us.apache.org>?
> >
> > Ismael
>
> Hi Ismael,
> You do not have any repositories that need to be moved, Kafka can safely
> disregard the email, as stated in the header :)
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Daniel Gruno <hu...@apache.org>.
On 12/7/18 6:28 PM, Ismael Juma wrote:
> Hi Daniel,
>
> We moved to Gitbox a while back for kafka and kafka-site. Which
> repository is still using git-wip-us.apache.org
> <http://git-wip-us.apache.org>?
>
> Ismael
Hi Ismael,
You do not have any repositories that need to be moved, Kafka can safely
disregard the email, as stated in the header :)
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Ismael Juma <is...@juma.me.uk>.
Hi Daniel,
We moved to Gitbox a while back for kafka and kafka-site. Which repository
is still using git-wip-us.apache.org?
Ismael
On Fri, Dec 7, 2018 at 8:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Dongjoon Hyun <do...@gmail.com>.
+1 for moving to new git infra.
Bests,
Dongjoon.
On Fri, Dec 7, 2018 at 12:53 PM shane knapp <sk...@berkeley.edu> wrote:
> no concerns, and this sounds great to me!
>
> On Fri, Dec 7, 2018 at 12:41 PM Sean Owen <sr...@apache.org> wrote:
>
>> See below: Apache projects are migrating to a new git infrastructure,
>> and are seeking projects to volunteer to move earlier than later. I
>> believe Spark should volunteer.
>>
>> This should mostly affect committers, who would need to point to the
>> new remote. It could affect downstream consumers of the Apache github
>> repo in the same way.
>>
>> This change will let committers do things like close pull requests and
>> merge directly from the Github UI, if desired. We won't abandon our
>> merge script yet though, as it can do things like update JIRA and
>> cherry-picks for us.
>>
>> It also opens up the possibility of using Github Issues instead of
>> JIRA, but that is something to consider for later.
>>
>> Any concerns about volunteering for the move? (We'll have to eventually.)
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Daniel Gruno <hu...@apache.org>
>> Date: Fri, Dec 7, 2018 at 10:53 AM
>> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>> git-wip-us.apache.org
>> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
>> project's dev list :-).
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe e-mail: dev-unsubscribe@spark.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe e-mail: dev-unsubscribe@spark.apache.org
>>
>>
>
> --
> Shane Knapp
> UC Berkeley EECS Research / RISELab Staff Technical Lead
> https://rise.cs.berkeley.edu
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by shane knapp <sk...@berkeley.edu>.
no concerns, and this sounds great to me!
On Fri, Dec 7, 2018 at 12:41 PM Sean Owen <sr...@apache.org> wrote:
> See below: Apache projects are migrating to a new git infrastructure,
> and are seeking projects to volunteer to move earlier than later. I
> believe Spark should volunteer.
>
> This should mostly affect committers, who would need to point to the
> new remote. It could affect downstream consumers of the Apache github
> repo in the same way.
>
> This change will let committers do things like close pull requests and
> merge directly from the Github UI, if desired. We won't abandon our
> merge script yet though, as it can do things like update JIRA and
> cherry-picks for us.
>
> It also opens up the possibility of using Github Issues instead of
> JIRA, but that is something to consider for later.
>
> Any concerns about volunteering for the move? (We'll have to eventually.)
>
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 10:53 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe e-mail: dev-unsubscribe@spark.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe e-mail: dev-unsubscribe@spark.apache.org
>
>
--
Shane Knapp
UC Berkeley EECS Research / RISELab Staff Technical Lead
https://rise.cs.berkeley.edu
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Sean Owen <sr...@apache.org>.
See below: Apache projects are migrating to a new git infrastructure,
and are seeking projects to volunteer to move earlier than later. I
believe Spark should volunteer.
This should mostly affect committers, who would need to point to the
new remote. It could affect downstream consumers of the Apache github
repo in the same way.
This change will let committers do things like close pull requests and
merge directly from the Github UI, if desired. We won't abandon our
merge script yet though, as it can do things like update JIRA and
cherry-picks for us.
It also opens up the possibility of using Github Issues instead of
JIRA, but that is something to consider for later.
Any concerns about volunteering for the move? (We'll have to eventually.)
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 10:53 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscribe@spark.apache.org
---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscribe@spark.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by David Smiley <da...@gmail.com>.
Let’s get migrated voluntarily after 7.6 this month?
On Fri, Dec 7, 2018 at 6:07 PM Steve Rowe <sa...@gmail.com> wrote:
>
>
> Begin forwarded message:
>
> *From: *Daniel Gruno <hu...@apache.org>
> *Subject: **[NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org <http://git-wip-us.apache.org>*
> *Date: *December 7, 2018 at 11:52:36 AM EST
> *To: *"users@infra.apache.org" <us...@infra.apache.org>
> *Reply-To: *"users@infra.apache.org" <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> --
Lucene/Solr Search Committer (PMC), Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Steve Rowe <sa...@gmail.com>.
> Begin forwarded message:
>
> From: Daniel Gruno <hu...@apache.org>
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
> Date: December 7, 2018 at 11:52:36 AM EST
> To: "users@infra.apache.org" <us...@infra.apache.org>
> Reply-To: "users@infra.apache.org" <us...@infra.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 users@infra.apache.org, not your project's dev list :-).
>
>
RE: [NOTICE] Mandatory relocation of Apache git repositories
on git-wip-us.apache.org
Posted by Paul Angus <pa...@shapeblue.com>.
Hi Daniel,
Thanks for giving everyone the heads up.
How can we tell if we're using the git-wip-us server ?
We use https://gitbox.apache.org/repos/asf?p=cloudstack.git
They resolve to different IPs so I assume that git-wip-us isn’t an alias for gitbox.apache.org. Is that right?
Kind regards
Paul Angus
(Apache CloudStack Project)
paul.angus@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
-----Original Message-----
From: Daniel Gruno <hu...@apache.org>
Sent: 07 December 2018 16:53
To: users@infra.apache.org
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 users@infra.apache.org, not your project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Mario Colindres <ae...@gmail.com>.
I build placement,think this is a wonder place to build gold values only.
On Fri, Dec 7, 2018, 8:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Kasper Sørensen <i....@gmail.com>.
Yes that sounds good. I’ll start a vote after the 5.2.0 release.
Kasper Sørensen
> On Dec 10, 2018, at 08:41, Henry Saputra <he...@gmail.com> wrote:
>
> I think we need to get "consensus" for early on boarding: "Consensus in the
> project (documented via the mailing list)"
>
> Or we could sit tight and coming along as later batch.
>
> Thanks,
>
> - Henry
>
> On Sun, Dec 9, 2018 at 5:06 PM Kasper Sørensen <
> i.am.kasper.sorensen@gmail.com> wrote:
>
>> The way I read Daniel Gruno's mail, it doesn't sound like we have much
>> choice to even vote on it? :-) Or do you mean we should vote to do it
>> sooner than later?
>>
>> Den søn. 9. dec. 2018 kl. 11.03 skrev Henry Saputra <
>> henry.saputra@gmail.com
>>> :
>>
>>> Thanks, Kasper. I think we could just do VOTE to move to gitbox in
>> parallel
>>> along with release one.
>>>
>>> - Henry
>>>
>>> On Sat, Dec 8, 2018 at 10:37 PM Kasper Sørensen <
>>> i.am.kasper.sorensen@gmail.com> wrote:
>>>
>>>> Heads up everybody. The MetaModel repo is hosted on the git-wip-us
>>> server,
>>>> and as per the mail below it seems we need to move over to other
>> servers.
>>>>
>>>> I suggest we complete the current release VOTE before we do anything.
>>> But I
>>>> also don't see any reason to wait much longer than that. Most of our
>>>> committers use the github mirror AFAIK.
>>>>
>>>>
>>>> ---------- Forwarded message ---------
>>>> From: Daniel Gruno <hu...@apache.org>
>>>> Date: fre. 7. dec. 2018 kl. 08.53
>>>> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>>>> git-wip-us.apache.org
>>>> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
>>>> project's dev list :-).
>>>>
>>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Henry Saputra <he...@gmail.com>.
I think we need to get "consensus" for early on boarding: "Consensus in the
project (documented via the mailing list)"
Or we could sit tight and coming along as later batch.
Thanks,
- Henry
On Sun, Dec 9, 2018 at 5:06 PM Kasper Sørensen <
i.am.kasper.sorensen@gmail.com> wrote:
> The way I read Daniel Gruno's mail, it doesn't sound like we have much
> choice to even vote on it? :-) Or do you mean we should vote to do it
> sooner than later?
>
> Den søn. 9. dec. 2018 kl. 11.03 skrev Henry Saputra <
> henry.saputra@gmail.com
> >:
>
> > Thanks, Kasper. I think we could just do VOTE to move to gitbox in
> parallel
> > along with release one.
> >
> > - Henry
> >
> > On Sat, Dec 8, 2018 at 10:37 PM Kasper Sørensen <
> > i.am.kasper.sorensen@gmail.com> wrote:
> >
> > > Heads up everybody. The MetaModel repo is hosted on the git-wip-us
> > server,
> > > and as per the mail below it seems we need to move over to other
> servers.
> > >
> > > I suggest we complete the current release VOTE before we do anything.
> > But I
> > > also don't see any reason to wait much longer than that. Most of our
> > > committers use the github mirror AFAIK.
> > >
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <hu...@apache.org>
> > > Date: fre. 7. dec. 2018 kl. 08.53
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > git-wip-us.apache.org
> > > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > project's dev list :-).
> > >
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Kasper Sørensen <i....@gmail.com>.
The way I read Daniel Gruno's mail, it doesn't sound like we have much
choice to even vote on it? :-) Or do you mean we should vote to do it
sooner than later?
Den søn. 9. dec. 2018 kl. 11.03 skrev Henry Saputra <henry.saputra@gmail.com
>:
> Thanks, Kasper. I think we could just do VOTE to move to gitbox in parallel
> along with release one.
>
> - Henry
>
> On Sat, Dec 8, 2018 at 10:37 PM Kasper Sørensen <
> i.am.kasper.sorensen@gmail.com> wrote:
>
> > Heads up everybody. The MetaModel repo is hosted on the git-wip-us
> server,
> > and as per the mail below it seems we need to move over to other servers.
> >
> > I suggest we complete the current release VOTE before we do anything.
> But I
> > also don't see any reason to wait much longer than that. Most of our
> > committers use the github mirror AFAIK.
> >
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <hu...@apache.org>
> > Date: fre. 7. dec. 2018 kl. 08.53
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org
> > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > project's dev list :-).
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Henry Saputra <he...@gmail.com>.
Thanks, Kasper. I think we could just do VOTE to move to gitbox in parallel
along with release one.
- Henry
On Sat, Dec 8, 2018 at 10:37 PM Kasper Sørensen <
i.am.kasper.sorensen@gmail.com> wrote:
> Heads up everybody. The MetaModel repo is hosted on the git-wip-us server,
> and as per the mail below it seems we need to move over to other servers.
>
> I suggest we complete the current release VOTE before we do anything. But I
> also don't see any reason to wait much longer than that. Most of our
> committers use the github mirror AFAIK.
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: fre. 7. dec. 2018 kl. 08.53
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Kasper Sørensen <i....@gmail.com>.
Heads up everybody. The MetaModel repo is hosted on the git-wip-us server,
and as per the mail below it seems we need to move over to other servers.
I suggest we complete the current release VOTE before we do anything. But I
also don't see any reason to wait much longer than that. Most of our
committers use the github mirror AFAIK.
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: fre. 7. dec. 2018 kl. 08.53
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to
gitbox.apache.org
Posted by "Daniel.Sun" <su...@apache.org>.
so far so good
-----
Daniel Sun
Apache Groovy committer
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to
gitbox.apache.org
Posted by "Daniel.Sun" <su...@apache.org>.
Gotcha.
Cheers,
Daniel.Sun
-----
Daniel Sun
Apache Groovy committer
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Remko Popma <re...@gmail.com>.
+1
On Sun, Dec 9, 2018 at 6:54 AM Paul King <pa...@asert.com.au> wrote:
> As per DanielG's attached email, we need to move our remaining git-wip
> repos:
> Apache Groovy
> Repository name:Description:Last changed:Links:
> groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
> Groovy < 2 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
> Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
> View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
> groovy-examples.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
> Groovy examples 16 weeks ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log>
> | Tree View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
> groovy-release.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
> groovy 27 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log> | Tree
> View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
>
>
> The website related ones are already moved. It won't affect our workflow
> but folks will most likely need to re-clone their local repo clones as a
> one off activity since the urls will change.
>
> My vote: +1 (binding)
>
> Cheers, Paul.
>
> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>
>>
>>
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Guillaume Laforge <gl...@gmail.com>.
+1
On Sun, Dec 9, 2018 at 10:31 AM Cédric Champeau <cc...@apache.org>
wrote:
> +1 you can use git remote seturl to avoid cloning again.
>
> Le dim. 9 déc. 2018 à 05:52, John Wagenleitner <
> john.wagenleitner@gmail.com> a écrit :
>
>> +1
>>
>> On Sat, Dec 8, 2018, 1:54 PM Paul King <paulk@asert.com.au wrote:
>>
>>> As per DanielG's attached email, we need to move our remaining git-wip
>>> repos:
>>> Apache Groovy
>>> Repository name:Description:Last changed:Links:
>>> groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
>>> Groovy < 2 days ago Summary
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
>>> Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog>
>>> | Full Log
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
>>> View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
>>> groovy-examples.git
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
>>> Groovy examples 16 weeks ago Summary
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
>>> | Short Log
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
>>> | Full Log
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log>
>>> | Tree View
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
>>> groovy-release.git
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
>>> groovy 27 days ago Summary
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
>>> | Short Log
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
>>> | Full Log
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log>
>>> | Tree View
>>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
>>>
>>>
>>> The website related ones are already moved. It won't affect our workflow
>>> but folks will most likely need to re-clone their local repo clones as a
>>> one off activity since the urls will change.
>>>
>>> My vote: +1 (binding)
>>>
>>> Cheers, Paul.
>>>
>>> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org>
>>> 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 :-).
>>>>
>>>>
>>>>
--
Guillaume Laforge
Apache Groovy committer & PMC Vice-President
Developer Advocate @ Google Cloud Platform
Blog: http://glaforge.appspot.com/
Twitter: @glaforge <http://twitter.com/glaforge>
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Cédric Champeau <cc...@apache.org>.
+1 you can use git remote seturl to avoid cloning again.
Le dim. 9 déc. 2018 à 05:52, John Wagenleitner <jo...@gmail.com>
a écrit :
> +1
>
> On Sat, Dec 8, 2018, 1:54 PM Paul King <paulk@asert.com.au wrote:
>
>> As per DanielG's attached email, we need to move our remaining git-wip
>> repos:
>> Apache Groovy
>> Repository name:Description:Last changed:Links:
>> groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
>> Groovy < 2 days ago Summary
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
>> Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog>
>> | Full Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
>> View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
>> groovy-examples.git
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
>> Groovy examples 16 weeks ago Summary
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
>> | Short Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
>> | Full Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log>
>> | Tree View
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
>> groovy-release.git
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
>> groovy 27 days ago Summary
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
>> | Short Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
>> | Full Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log>
>> | Tree View
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
>>
>>
>> The website related ones are already moved. It won't affect our workflow
>> but folks will most likely need to re-clone their local repo clones as a
>> one off activity since the urls will change.
>>
>> My vote: +1 (binding)
>>
>> Cheers, Paul.
>>
>> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>>
>>>
>>>
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by John Wagenleitner <jo...@gmail.com>.
+1
On Sat, Dec 8, 2018, 1:54 PM Paul King <paulk@asert.com.au wrote:
> As per DanielG's attached email, we need to move our remaining git-wip
> repos:
> Apache Groovy
> Repository name:Description:Last changed:Links:
> groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
> Groovy < 2 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
> Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
> View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
> groovy-examples.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
> Groovy examples 16 weeks ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log>
> | Tree View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
> groovy-release.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
> groovy 27 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log> | Tree
> View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
>
>
> The website related ones are already moved. It won't affect our workflow
> but folks will most likely need to re-clone their local repo clones as a
> one off activity since the urls will change.
>
> My vote: +1 (binding)
>
> Cheers, Paul.
>
> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>
>>
>>
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Andres Almiray <aa...@gmail.com>.
+1
Sent from my primitive tricorder
> On Dec 9, 2018, at 02:04, Keegan Witt <ke...@gmail.com> wrote:
>
> +1
>
> Also, folks should just be able to do "git remote add" instead of re-cloning. Shouldn't be a big deal.
>
>> On Sat, Dec 8, 2018 at 4:54 PM Paul King <pa...@asert.com.au> wrote:
>> As per DanielG's attached email, we need to move our remaining git-wip repos:
>> Apache Groovy
>> Repository name: Description: Last changed: Links:
>> groovy.git Apache Groovy < 2 days ago Summary | Short Log | Full Log | Tree View
>> groovy-examples.git Apache Groovy examples 16 weeks ago Summary | Short Log | Full Log | Tree View
>> groovy-release.git Apache groovy 27 days ago Summary | Short Log | Full Log | Tree View
>>
>>
>> The website related ones are already moved. It won't affect our workflow but folks will most likely need to re-clone their local repo clones as a one off activity since the urls will change.
>>
>> My vote: +1 (binding)
>>
>> Cheers, Paul.
>>
>>> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>>
>>>
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Keegan Witt <ke...@gmail.com>.
+1
Also, folks should just be able to do "git remote add" instead of
re-cloning. Shouldn't be a big deal.
On Sat, Dec 8, 2018 at 4:54 PM Paul King <pa...@asert.com.au> wrote:
> As per DanielG's attached email, we need to move our remaining git-wip
> repos:
> Apache Groovy
> Repository name:Description:Last changed:Links:
> groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
> Groovy < 2 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
> Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
> View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
> groovy-examples.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
> Groovy examples 16 weeks ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log>
> | Tree View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
> groovy-release.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
> groovy 27 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log> | Tree
> View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
>
>
> The website related ones are already moved. It won't affect our workflow
> but folks will most likely need to re-clone their local repo clones as a
> one off activity since the urls will change.
>
> My vote: +1 (binding)
>
> Cheers, Paul.
>
> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>
>>
>>
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Paul King <pa...@asert.com.au>.
These have now been moved. If you are just submitting PR's via github,
there is nothing to do.
If you have origin set to some git-wip-us type address, you'll want to do
something like:
$ git remote set-url origin https://gitbox.apache.org/repos/asf/groovy.git
Cheers, Paul.
On Wed, Dec 12, 2018 at 8:26 AM Paul King <pa...@asert.com.au> wrote:
> The vote has passed with 5 binding +1 votes and 2 additional +1 votes.
> I'll put in the infra ticket(s) to have those repos moved.
>
> On Sun, Dec 9, 2018 at 7:54 AM Paul King <pa...@asert.com.au> wrote:
>
>> As per DanielG's attached email, we need to move our remaining git-wip
>> repos:
>> Apache Groovy
>> Repository name:Description:Last changed:Links:
>> groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
>> Groovy < 2 days ago Summary
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
>> Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog>
>> | Full Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
>> View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
>> groovy-examples.git
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
>> Groovy examples 16 weeks ago Summary
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
>> | Short Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
>> | Full Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log>
>> | Tree View
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
>> groovy-release.git
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
>> groovy 27 days ago Summary
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
>> | Short Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
>> | Full Log
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log>
>> | Tree View
>> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
>>
>>
>> The website related ones are already moved. It won't affect our workflow
>> but folks will most likely need to re-clone their local repo clones as a
>> one off activity since the urls will change.
>>
>> My vote: +1 (binding)
>>
>> Cheers, Paul.
>>
>> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>>
>>>
>>>
Re: [VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Paul King <pa...@asert.com.au>.
The vote has passed with 5 binding +1 votes and 2 additional +1 votes. I'll
put in the infra ticket(s) to have those repos moved.
On Sun, Dec 9, 2018 at 7:54 AM Paul King <pa...@asert.com.au> wrote:
> As per DanielG's attached email, we need to move our remaining git-wip
> repos:
> Apache Groovy
> Repository name:Description:Last changed:Links:
> groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
> Groovy < 2 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
> Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
> View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
> groovy-examples.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
> Groovy examples 16 weeks ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log>
> | Tree View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
> groovy-release.git
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
> groovy 27 days ago Summary
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
> | Short Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
> | Full Log
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log> | Tree
> View
> <https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
>
>
> The website related ones are already moved. It won't affect our workflow
> but folks will most likely need to re-clone their local repo clones as a
> one off activity since the urls will change.
>
> My vote: +1 (binding)
>
> Cheers, Paul.
>
> On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>>
>>
>>
[VOTE] Move the Groovy repositories on git-wip-us.apache.org to gitbox.apache.org
Posted by Paul King <pa...@asert.com.au>.
As per DanielG's attached email, we need to move our remaining git-wip
repos:
Apache Groovy
Repository name:Description:Last changed:Links:
groovy.git <https://git1-us-west.apache.org/repos/asf/?p=groovy.git> Apache
Groovy < 2 days ago Summary
<https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=summary> | Short
Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=shortlog> | Full
Log <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=log> | Tree
View <https://git1-us-west.apache.org/repos/asf/?p=groovy.git;a=tree>
groovy-examples.git
<https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git> Apache
Groovy examples 16 weeks ago Summary
<https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=summary>
| Short Log
<https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=shortlog>
| Full Log
<https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=log> | Tree
View
<https://git1-us-west.apache.org/repos/asf/?p=groovy-examples.git;a=tree>
groovy-release.git
<https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git> Apache
groovy 27 days ago Summary
<https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=summary>
| Short Log
<https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=shortlog>
| Full Log
<https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=log> | Tree
View
<https://git1-us-west.apache.org/repos/asf/?p=groovy-release.git;a=tree>
The website related ones are already moved. It won't affect our workflow
but folks will most likely need to re-clone their local repo clones as a
one off activity since the urls will change.
My vote: +1 (binding)
Cheers, Paul.
On Sat, Dec 8, 2018 at 2:53 AM Daniel Gruno <hu...@apache.org> 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 :-).
>
>
>
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.
[DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Josh Thompson <jo...@ncsu.edu>.
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: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Shawn McKinney <sm...@apache.org>.
> On Dec 9, 2018, at 11:08 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
> On 12/9/18 5:37 PM, Shawn McKinney wrote:
>>
>> In other words, does this change to combine the four into a single git project repo force us to also change the structure (and process) of the maven artifacts being built and released?
>
> I'd say yes.
>
> The four old repos including their pom.xml reside then in a subdirectory
> each within the new repo (say core, realm, rest, web), then a new
> parent/aggregator pom.xml is needed in the new repo. The individual poms
> can then be cleaned up, i.e. redundant information (scm,
> issueManagement, developers, common parts of build, etc) can be moved up
> to the new parent pom.
>
> What is also required is to think about the license/notice files, likely
> they also need to be moved up to the new root.
>
> All in all not too hard, but for sure it requires some time to tweak the
> build and release.
Agreed.
>
> On Dec 9, 2018, at 11:08 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
> There is no need to rush, if it fits better into your schedule next year
> then postpone it.
>
> And to be clear, I hope it doesn't seem I want to force you to merge the
> 4 repos, if you feel more comfortable please keep them separate :)
For the record, I’m in favor of combining the four so your comments are well received.
I’ll give it a few days, to think about. Thanks for weighing in.
—Shawn
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 12/9/18 5:37 PM, Shawn McKinney wrote:
>
>> On Dec 8, 2018, at 10:04 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> If time allows I'd suggest to follow the voluntary relocation.
>>
>> For Fortress, if you consider to merge the 4 repos into one, this would
>> be a good time now. Just create a new "directory-fortress" repo at
>> Gitbox [1] and merge the 4 into it, then request to delete the old
>> repos, so no relocation needed.
>
> Trying to figure out how much work this is, and does it fit into my schedule for the next few weeks...
>
> We’ll call your recommendation option one. A new repo gets created, say directory-fortress, that would contain the four packages merged. That all seems pretty straight-forward. What else must be done — would a new pom be needed to drive the build/release of the four packages of the combined repo?
>
> In other words, does this change to combine the four into a single git project repo force us to also change the structure (and process) of the maven artifacts being built and released?
I'd say yes.
The four old repos including their pom.xml reside then in a subdirectory
each within the new repo (say core, realm, rest, web), then a new
parent/aggregator pom.xml is needed in the new repo. The individual poms
can then be cleaned up, i.e. redundant information (scm,
issueManagement, developers, common parts of build, etc) can be moved up
to the new parent pom.
What is also required is to think about the license/notice files, likely
they also need to be moved up to the new root.
All in all not too hard, but for sure it requires some time to tweak the
build and release.
There is no need to rush, if it fits better into your schedule next year
then postpone it.
And to be clear, I hope it doesn't seem I want to force you to merge the
4 repos, if you feel more comfortable please keep them separate :)
Kind Regards,
Stefan
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Shawn McKinney <sm...@apache.org>.
> On Dec 8, 2018, at 10:04 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
> If time allows I'd suggest to follow the voluntary relocation.
>
> For Fortress, if you consider to merge the 4 repos into one, this would
> be a good time now. Just create a new "directory-fortress" repo at
> Gitbox [1] and merge the 4 into it, then request to delete the old
> repos, so no relocation needed.
Trying to figure out how much work this is, and does it fit into my schedule for the next few weeks...
We’ll call your recommendation option one. A new repo gets created, say directory-fortress, that would contain the four packages merged. That all seems pretty straight-forward. What else must be done — would a new pom be needed to drive the build/release of the four packages of the combined repo?
In other words, does this change to combine the four into a single git project repo force us to also change the structure (and process) of the maven artifacts being built and released?
Option two is to voluntarily relocate to gitbox, but not combine (yet).
Option three is to delay migration until Feb's mandatory relo, which buys time to do the combine.
Thanks
—Shawn
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 12/7/18 11:25 PM, Shawn McKinney wrote:
> Hello,
>
> Currently there are four fortress repos on git-wip-us affected by this change.
> https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
> https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
> https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
> https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git <https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git>
> Do we have others? Any recommendations here?
Kerby is also affected:
https://git-wip-us.apache.org/repos/asf/directory-kerby.git
See full list here (search for Directory):
https://git-wip-us.apache.org/repos/asf
If time allows I'd suggest to follow the voluntary relocation.
For Fortress, if you consider to merge the 4 repos into one, this would
be a good time now. Just create a new "directory-fortress" repo at
Gitbox [1] and merge the 4 into it, then request to delete the old
repos, so no relocation needed.
Kind Regards,
Stefan
[1] https://gitbox.apache.org/
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Shawn McKinney <sm...@apache.org>.
Hello,
Currently there are four fortress repos on git-wip-us affected by this change.
https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git <https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git>
Do we have others? Any recommendations here?
Shawn
> Begin forwarded message:
>
> From: Daniel Gruno <hu...@apache.org>
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
> Date: December 7, 2018 at 10:52:36 AM CST
> To: "users@infra.apache.org" <us...@infra.apache.org>
> Reply-To: dev@community.apache.org
> Reply-To: "users@infra.apache.org" <us...@infra.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 users@infra.apache.org, not your project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Evans Ye <ev...@apache.org>.
I'm +1 to this. Seems that the commit flow will be imporved.
Roman Shaposhnik <ro...@shaposhnik.org> 於 2018年12月11日 週二 上午10:26寫道：
> Guys, will it make sense for us to move voluntarily to beat the crowds
> and make sure that
> the service actually works for us?
>
> Thanks,
> Roman.
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 8:52 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Guys, will it make sense for us to move voluntarily to beat the crowds
and make sure that
the service actually works for us?
Thanks,
Roman.
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 8:52 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Nikhil Kak <nk...@pivotal.io>.
+1
Nikhil
On Tue, Jan 8, 2019 at 3:28 PM Jingyi Mei <jm...@pivotal.io> wrote:
> I'd like to call a vote on moving to gitbox. Here is my +1.
>
> Cheers,
> Jingyi
>
> On Mon, Dec 10, 2018 at 6:56 PM Rahul Iyer <ri...@apache.org> wrote:
>
> > +1 for the voluntary move. The earlier the better.
> >
> > On Mon, Dec 10, 2018 at 6:26 PM Roman Shaposhnik <ro...@shaposhnik.org>
> > wrote:
> >
> > > Guys, will it make sense for us to move voluntarily to beat the crowds
> > > and make sure that
> > > the service actually works for us?
> > >
> > > Thanks,
> > > Roman.
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <hu...@apache.org>
> > > Date: Fri, Dec 7, 2018 at 8:52 AM
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__git-2Dwip-2Dus.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=JjcDa7nM__bUvWTEgLMRB5UOel-dBeUN3HGlW3w45Gg&e=
> > > To: users@infra.apache.org <us...@infra.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
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> > .
> > >
> > > ## 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 (
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> )
> > OR GitHub for your development
> > > and code pushes. To be able to use GitHub, please follow the primer
> > > at:
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reference.apache.org_committer_github&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=bEFqjHbEykHOxBC3GeRp6CEKjK71TA9fDiy2vaaRlfc&e=
> > >
> > >
> > > 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 :-).
> > >
> >
>
--
Thanks,
Nikhil Kak
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Domino Valdano <dv...@pivotal.io>.
+1
On Wed, Jan 9, 2019 at 10:50 AM Orhan Kislal <ok...@pivotal.io> wrote:
> +1
>
> On Wed, Jan 9, 2019 at 9:44 PM Frank McQuillan <fm...@pivotal.io>
> wrote:
>
> > +1
> >
> > Frank
> >
> > On Tue, Jan 8, 2019 at 3:28 PM Jingyi Mei <jm...@pivotal.io> wrote:
> >
> > > I'd like to call a vote on moving to gitbox. Here is my +1.
> > >
> > > Cheers,
> > > Jingyi
> > >
> > > On Mon, Dec 10, 2018 at 6:56 PM Rahul Iyer <ri...@apache.org> wrote:
> > >
> > > > +1 for the voluntary move. The earlier the better.
> > > >
> > > > On Mon, Dec 10, 2018 at 6:26 PM Roman Shaposhnik <
> roman@shaposhnik.org
> > >
> > > > wrote:
> > > >
> > > > > Guys, will it make sense for us to move voluntarily to beat the
> > crowds
> > > > > and make sure that
> > > > > the service actually works for us?
> > > > >
> > > > > Thanks,
> > > > > Roman.
> > > > >
> > > > > ---------- Forwarded message ---------
> > > > > From: Daniel Gruno <hu...@apache.org>
> > > > > Date: Fri, Dec 7, 2018 at 8:52 AM
> > > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories
> on
> > > > >
> > > >
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__git-2Dwip-2Dus.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=JjcDa7nM__bUvWTEgLMRB5UOel-dBeUN3HGlW3w45Gg&e=
> > > > > To: users@infra.apache.org <us...@infra.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
> > > >
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> > > > .
> > > > >
> > > > > ## 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 (
> > > >
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> > > )
> > > > OR GitHub for your development
> > > > > and code pushes. To be able to use GitHub, please follow the primer
> > > > > at:
> > > >
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reference.apache.org_committer_github&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=bEFqjHbEykHOxBC3GeRp6CEKjK71TA9fDiy2vaaRlfc&e=
> > > > >
> > > > >
> > > > > 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 :-).
> > > > >
> > > >
> > >
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Orhan Kislal <ok...@pivotal.io>.
+1
On Wed, Jan 9, 2019 at 9:44 PM Frank McQuillan <fm...@pivotal.io>
wrote:
> +1
>
> Frank
>
> On Tue, Jan 8, 2019 at 3:28 PM Jingyi Mei <jm...@pivotal.io> wrote:
>
> > I'd like to call a vote on moving to gitbox. Here is my +1.
> >
> > Cheers,
> > Jingyi
> >
> > On Mon, Dec 10, 2018 at 6:56 PM Rahul Iyer <ri...@apache.org> wrote:
> >
> > > +1 for the voluntary move. The earlier the better.
> > >
> > > On Mon, Dec 10, 2018 at 6:26 PM Roman Shaposhnik <roman@shaposhnik.org
> >
> > > wrote:
> > >
> > > > Guys, will it make sense for us to move voluntarily to beat the
> crowds
> > > > and make sure that
> > > > the service actually works for us?
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > > > ---------- Forwarded message ---------
> > > > From: Daniel Gruno <hu...@apache.org>
> > > > Date: Fri, Dec 7, 2018 at 8:52 AM
> > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > >
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__git-2Dwip-2Dus.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=JjcDa7nM__bUvWTEgLMRB5UOel-dBeUN3HGlW3w45Gg&e=
> > > > To: users@infra.apache.org <us...@infra.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
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> > > .
> > > >
> > > > ## 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 (
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> > )
> > > OR GitHub for your development
> > > > and code pushes. To be able to use GitHub, please follow the primer
> > > > at:
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reference.apache.org_committer_github&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=bEFqjHbEykHOxBC3GeRp6CEKjK71TA9fDiy2vaaRlfc&e=
> > > >
> > > >
> > > > 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 :-).
> > > >
> > >
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Frank McQuillan <fm...@pivotal.io>.
+1
Frank
On Tue, Jan 8, 2019 at 3:28 PM Jingyi Mei <jm...@pivotal.io> wrote:
> I'd like to call a vote on moving to gitbox. Here is my +1.
>
> Cheers,
> Jingyi
>
> On Mon, Dec 10, 2018 at 6:56 PM Rahul Iyer <ri...@apache.org> wrote:
>
> > +1 for the voluntary move. The earlier the better.
> >
> > On Mon, Dec 10, 2018 at 6:26 PM Roman Shaposhnik <ro...@shaposhnik.org>
> > wrote:
> >
> > > Guys, will it make sense for us to move voluntarily to beat the crowds
> > > and make sure that
> > > the service actually works for us?
> > >
> > > Thanks,
> > > Roman.
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <hu...@apache.org>
> > > Date: Fri, Dec 7, 2018 at 8:52 AM
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__git-2Dwip-2Dus.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=JjcDa7nM__bUvWTEgLMRB5UOel-dBeUN3HGlW3w45Gg&e=
> > > To: users@infra.apache.org <us...@infra.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
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> > .
> > >
> > > ## 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 (
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> )
> > OR GitHub for your development
> > > and code pushes. To be able to use GitHub, please follow the primer
> > > at:
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reference.apache.org_committer_github&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=bEFqjHbEykHOxBC3GeRp6CEKjK71TA9fDiy2vaaRlfc&e=
> > >
> > >
> > > 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 :-).
> > >
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Jingyi Mei <jm...@pivotal.io>.
I'd like to call a vote on moving to gitbox. Here is my +1.
Cheers,
Jingyi
On Mon, Dec 10, 2018 at 6:56 PM Rahul Iyer <ri...@apache.org> wrote:
> +1 for the voluntary move. The earlier the better.
>
> On Mon, Dec 10, 2018 at 6:26 PM Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > Guys, will it make sense for us to move voluntarily to beat the crowds
> > and make sure that
> > the service actually works for us?
> >
> > Thanks,
> > Roman.
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <hu...@apache.org>
> > Date: Fri, Dec 7, 2018 at 8:52 AM
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__git-2Dwip-2Dus.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=JjcDa7nM__bUvWTEgLMRB5UOel-dBeUN3HGlW3w45Gg&e=
> > To: users@infra.apache.org <us...@infra.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
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=
> .
> >
> > ## 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 (
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gitbox.apache.org&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=DoBf_SA_M21rPexDj-DJYCOF8utMzq1wxwkFrhvbJGM&e=)
> OR GitHub for your development
> > and code pushes. To be able to use GitHub, please follow the primer
> > at:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reference.apache.org_committer_github&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=G-p7-dYqt5k81189BgC0jw&m=qW9Rb1N7AvTvAwQJ1pDpuxghulDeyoTERM46PAQ5Xqs&s=bEFqjHbEykHOxBC3GeRp6CEKjK71TA9fDiy2vaaRlfc&e=
> >
> >
> > 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 :-).
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Rahul Iyer <ri...@apache.org>.
+1 for the voluntary move. The earlier the better.
On Mon, Dec 10, 2018 at 6:26 PM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> Guys, will it make sense for us to move voluntarily to beat the crowds
> and make sure that
> the service actually works for us?
>
> Thanks,
> Roman.
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 8:52 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Guys, will it make sense for us to move voluntarily to beat the crowds
and make sure that
the service actually works for us?
Thanks,
Roman.
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 8:52 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Joan Touzet <wo...@apache.org>.
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" <ei...@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 <wo...@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" <hu...@apache.org>
> > To: users@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 users@infra.apache.org, not your
> > project's dev list :-).
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Eiri <ei...@eiri.ca>.
+1
> On Dec 7, 2018, at 12:58, Joan Touzet <wo...@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" <hu...@apache.org>
> To: users@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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Andy Wenk <an...@apache.org>.
+1
--
Andy Wenk
Hamburg - Germany
RockIt!
GPG public key:
http://pgp.mit.edu/pks/lookup?op=get&search=0x45D3565377F93D29
> On 7. Dec 2018, at 18:45, Paul Davis <pa...@gmail.com> wrote:
>
> +1
> On Fri, Dec 7, 2018 at 10:58 AM Joan Touzet <wo...@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" <hu...@apache.org>
>> To: users@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 users@infra.apache.org, not your
>> project's dev list :-).
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Paul Davis <pa...@gmail.com>.
+1
On Fri, Dec 7, 2018 at 10:58 AM Joan Touzet <wo...@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" <hu...@apache.org>
> To: users@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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Joan Touzet <wo...@apache.org>.
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" <hu...@apache.org>
To: users@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 users@infra.apache.org, not your
project's dev list :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Richard Downer <ri...@apache.org>.
Hi Geoff,
Moving to gitbox seems to be a no-brainer to me. It won't affect our
contributor's processes, and it makes our committer's processes easier.
+1 to making an active move to gitbox.
I'm personally not concerned by the date, but after Christmas and early in
the new year would be fine.
Richard.
On Fri, 7 Dec 2018 at 21:03, Geoff Macartney <ge...@gmail.com>
wrote:
> Hi Brooklyners,
>
> Looks like we'll have to move Brooklyn to gitbox. Any thoughts on when to
> do this? The voluntary timeframe is between now and January 9th 2019, and
> it might be convenient to get this done in the presumably slack period
> around Christmas.
>
> The process being
>
> - Consensus in the project (documented via the mailing list)
> - File a JIRA ticket with INFRA to voluntarily move your project repos over
> to gitbox
>
> shall we agree a timeframe in response to this email? I'll volunteer to
> raise the INFRA ticket for the move once we're agreed.
>
> Let me suggest the week beginning 31st December.
>
> Regards
> Geoff
>
>
> On Fri, 7 Dec 2018 at 16:54 Daniel Gruno <hu...@apache.org> 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 :-).
> >
> >
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Geoff Macartney <ge...@gmail.com>.
Oops sorry I mean Aled of course.
On Fri, 7 Dec 2018, 21:12 Geoff Macartney, <ge...@gmail.com>
wrote:
> Hi Alex,
>
> The way I read it, we just request to move to gitbox - "Initially, we are
> asking that projects voluntarily request to move their repositories to
> gitbox, hence this email." I *think* once we move then people have the
> choice of committing either to gitbox directly or to Github and the two
> will be synchronized (?)
>
> Geoff
>
> On Fri, 7 Dec 2018 at 21:03 Geoff Macartney <ge...@gmail.com>
> wrote:
>
>> Hi Brooklyners,
>>
>> Looks like we'll have to move Brooklyn to gitbox. Any thoughts on when to
>> do this? The voluntary timeframe is between now and January 9th 2019, and
>> it might be convenient to get this done in the presumably slack period
>> around Christmas.
>>
>> The process being
>>
>> - Consensus in the project (documented via the mailing list)
>> - File a JIRA ticket with INFRA to voluntarily move your project repos
>> over to gitbox
>>
>> shall we agree a timeframe in response to this email? I'll volunteer to
>> raise the INFRA ticket for the move once we're agreed.
>>
>> Let me suggest the week beginning 31st December.
>>
>> Regards
>> Geoff
>>
>>
>> On Fri, 7 Dec 2018 at 16:54 Daniel Gruno <hu...@apache.org> 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 :-).
>>>
>>>
>>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Geoff Macartney <ge...@gmail.com>.
Hi Alex,
The way I read it, we just request to move to gitbox - "Initially, we are
asking that projects voluntarily request to move their repositories to
gitbox, hence this email." I *think* once we move then people have the
choice of committing either to gitbox directly or to Github and the two
will be synchronized (?)
Geoff
On Fri, 7 Dec 2018 at 21:03 Geoff Macartney <ge...@gmail.com>
wrote:
> Hi Brooklyners,
>
> Looks like we'll have to move Brooklyn to gitbox. Any thoughts on when to
> do this? The voluntary timeframe is between now and January 9th 2019, and
> it might be convenient to get this done in the presumably slack period
> around Christmas.
>
> The process being
>
> - Consensus in the project (documented via the mailing list)
> - File a JIRA ticket with INFRA to voluntarily move your project repos
> over to gitbox
>
> shall we agree a timeframe in response to this email? I'll volunteer to
> raise the INFRA ticket for the move once we're agreed.
>
> Let me suggest the week beginning 31st December.
>
> Regards
> Geoff
>
>
> On Fri, 7 Dec 2018 at 16:54 Daniel Gruno <hu...@apache.org> 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 :-).
>>
>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Geoff Macartney <ge...@gmail.com>.
Hi Brooklyners,
Looks like we'll have to move Brooklyn to gitbox. Any thoughts on when to
do this? The voluntary timeframe is between now and January 9th 2019, and
it might be convenient to get this done in the presumably slack period
around Christmas.
The process being
- Consensus in the project (documented via the mailing list)
- File a JIRA ticket with INFRA to voluntarily move your project repos over
to gitbox
shall we agree a timeframe in response to this email? I'll volunteer to
raise the INFRA ticket for the move once we're agreed.
Let me suggest the week beginning 31st December.
Regards
Geoff
On Fri, 7 Dec 2018 at 16:54 Daniel Gruno <hu...@apache.org> 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 :-).
>
>
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Guys, will it make sense for us to move voluntarily to beat the crowds
and make sure that
the service actually works for us?
Thanks,
Roman.
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 8:52 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Richard Eckart de Castilho <re...@apache.org>.
On 7. Dec 2018, at 21:51, Marshall Schor <ms...@schor.com> wrote:
>
> I see uimafit (our only project using GIT at the moment) is already on gitbox.
> So no action is needed, I think.
That is my impression as well.
-- Richard
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Marshall Schor <ms...@schor.com>.
I see uimafit (our only project using GIT at the moment) is already on gitbox.
So no action is needed, I think.
-Marshall
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Vineet Garg <vg...@hortonworks.com>.
+1 on early move.
> On Dec 11, 2018, at 12:46 PM, Slim Bouguerra <bs...@apache.org> wrote:
>
> +1 on Early move.
>
> Having direct write access to Github is a good first step to move toward
> one place that can be used to review and merge pull requests IMO.
>
> On Dec 11, 2018, at 12:06 PM, Alan Gates <al...@gmail.com> wrote:
>
> This includes the hive project, as we're on the older git-wip-us. Do we
> want to move sooner or later?
>
> Alan.
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 8:52 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Slim Bouguerra <bs...@apache.org>.
Then next step will be to formalize/define the process within the community
thought.
On Tue, Dec 11, 2018 at 12:55 PM Alan Gates <al...@gmail.com> wrote:
> IIUC it's the only step necessary to have one place where we could review
> and merge pull requests. There'd be no more need for attaching patches to
> JIRA. Of course we'd need to update our CI processes to match.
>
> Alan.
>
> On Tue, Dec 11, 2018 at 12:46 PM Slim Bouguerra <bs...@apache.org> wrote:
>
> > +1 on Early move.
> >
> > Having direct write access to Github is a good first step to move toward
> > one place that can be used to review and merge pull requests IMO.
> >
> > On Dec 11, 2018, at 12:06 PM, Alan Gates <al...@gmail.com> wrote:
> >
> > This includes the hive project, as we're on the older git-wip-us. Do we
> > want to move sooner or later?
> >
> > Alan.
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <hu...@apache.org>
> > Date: Fri, Dec 7, 2018 at 8:52 AM
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org
> > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > project's dev list :-).
> >
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Alan Gates <al...@gmail.com>.
IIUC it's the only step necessary to have one place where we could review
and merge pull requests. There'd be no more need for attaching patches to
JIRA. Of course we'd need to update our CI processes to match.
Alan.
On Tue, Dec 11, 2018 at 12:46 PM Slim Bouguerra <bs...@apache.org> wrote:
> +1 on Early move.
>
> Having direct write access to Github is a good first step to move toward
> one place that can be used to review and merge pull requests IMO.
>
> On Dec 11, 2018, at 12:06 PM, Alan Gates <al...@gmail.com> wrote:
>
> This includes the hive project, as we're on the older git-wip-us. Do we
> want to move sooner or later?
>
> Alan.
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 8:52 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Slim Bouguerra <bs...@apache.org>.
+1 on Early move.
Having direct write access to Github is a good first step to move toward
one place that can be used to review and merge pull requests IMO.
On Dec 11, 2018, at 12:06 PM, Alan Gates <al...@gmail.com> wrote:
This includes the hive project, as we're on the older git-wip-us. Do we
want to move sooner or later?
Alan.
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 8:52 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Alan Gates <al...@gmail.com>.
This includes the hive project, as we're on the older git-wip-us. Do we
want to move sooner or later?
Alan.
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 8:52 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Henry Saputra <he...@gmail.com>.
+1
No objection from me.
On Mon, Dec 10, 2018 at 4:24 PM William Guo <gu...@apache.org> wrote:
> FYI
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Sat, Dec 8, 2018 at 12:54 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by William Guo <gu...@apache.org>.
FYI
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Sat, Dec 8, 2018 at 12:54 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Pepijn Noltes <pe...@gmail.com>.
Hi Roy,
Thanks for picking this up.
+1 for moving to gitbox voluntary.
Greetings,
Pepijn
On Sat, Dec 8, 2018 at 11:13 AM Roy Lenferink <rl...@apache.org> wrote:
>
> Requesting lazy consensus - does anyone have a problem with
> starting the process to migrate our existing git-wip-us repos [1] [2] 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.
>
> Roy
>
> [1] https://git-wip-us.apache.org/repos/asf?p=celix.git
> [2] https://git-wip-us.apache.org/repos/asf?p=celix-site.git
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <le...@gmail.com>.
The repositories have been moved and can be found here:
https://gitbox.apache.org/repos/asf/celix.git
https://gitbox.apache.org/repos/asf/celix-site.git
To be able to use the full GitHub integration, it is needed to link your
ASF and GitHub accounts which can be done here:
https://gitbox.apache.org/setup/
- Roy
Op ma 10 dec. 2018 om 19:19 schreef erjan altena <er...@gmail.com>:
> Hi,
>
> Since we get also write access through github and can use the github
> facilities also a +1 from me.
>
> Regards,
> Erjan
>
> On Mon, Dec 10, 2018 at 6:45 PM Gabriele Ricciardi <
> lele.ricciardi@gmail.com>
> wrote:
>
> > +1 for me too!
> >
> > And thanks Roy for taking care of it!
> >
> > Cheers,
> >
> > Gabriele
> >
> > Il giorno lun 10 dic 2018, 17:43 Roy Lenferink <rl...@apache.org>
> ha
> > scritto:
> >
> > > Forwarding Bjoern his +1 to the mailing list and adding my +1 as well.
> > > I have created a JIRA issue for moving over the repos [1]
> > >
> > > Roy
> > >
> > > [1] https://issues.apache.org/jira/browse/INFRA-17386
> > >
> > >
> > > Op zo 9 dec. 2018 om 22:42 schreef Bjoern Petri <
> > bjoern.petri@sundevil.de
> > > >:
> > >
> > > > Good idea.
> > > >
> > > > +1 from me as well
> > > >
> > > > Regards,
> > > > Bjoern
> > > >
> > > >
> > >
> >
>
>
> --
> -------------------------------------------------------
> Erjan Altena
>
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by erjan altena <er...@gmail.com>.
Hi,
Since we get also write access through github and can use the github
facilities also a +1 from me.
Regards,
Erjan
On Mon, Dec 10, 2018 at 6:45 PM Gabriele Ricciardi <le...@gmail.com>
wrote:
> +1 for me too!
>
> And thanks Roy for taking care of it!
>
> Cheers,
>
> Gabriele
>
> Il giorno lun 10 dic 2018, 17:43 Roy Lenferink <rl...@apache.org> ha
> scritto:
>
> > Forwarding Bjoern his +1 to the mailing list and adding my +1 as well.
> > I have created a JIRA issue for moving over the repos [1]
> >
> > Roy
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-17386
> >
> >
> > Op zo 9 dec. 2018 om 22:42 schreef Bjoern Petri <
> bjoern.petri@sundevil.de
> > >:
> >
> > > Good idea.
> > >
> > > +1 from me as well
> > >
> > > Regards,
> > > Bjoern
> > >
> > >
> >
>
--
-------------------------------------------------------
Erjan Altena
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Gabriele Ricciardi <le...@gmail.com>.
+1 for me too!
And thanks Roy for taking care of it!
Cheers,
Gabriele
Il giorno lun 10 dic 2018, 17:43 Roy Lenferink <rl...@apache.org> ha
scritto:
> Forwarding Bjoern his +1 to the mailing list and adding my +1 as well.
> I have created a JIRA issue for moving over the repos [1]
>
> Roy
>
> [1] https://issues.apache.org/jira/browse/INFRA-17386
>
>
> Op zo 9 dec. 2018 om 22:42 schreef Bjoern Petri <bjoern.petri@sundevil.de
> >:
>
> > Good idea.
> >
> > +1 from me as well
> >
> > Regards,
> > Bjoern
> >
> >
>
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
Forwarding Bjoern his +1 to the mailing list and adding my +1 as well.
I have created a JIRA issue for moving over the repos [1]
Roy
[1] https://issues.apache.org/jira/browse/INFRA-17386
Op zo 9 dec. 2018 om 22:42 schreef Bjoern Petri <bj...@sundevil.de>:
> Good idea.
>
> +1 from me as well
>
> Regards,
> Bjoern
>
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
Requesting lazy consensus - does anyone have a problem with
starting the process to migrate our existing git-wip-us repos [1] [2] 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.
Roy
[1] https://git-wip-us.apache.org/repos/asf?p=celix.git
[2] https://git-wip-us.apache.org/repos/asf?p=celix-site.git
---------- Forwarded message ---------
From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
The repositories have been moved to gitbox and are available here:
https://gitbox.apache.org/repos/asf/?p=httpcomponents-client.git
https://gitbox.apache.org/repos/asf/?p=httpcomponents-core.git
https://gitbox.apache.org/repos/asf/?p=httpcomponents-parent.git
https://gitbox.apache.org/repos/asf/?p=httpcomponents-stylecheck.git
https://gitbox.apache.org/repos/asf/?p=httpcomponents-website.git
In order to use the full GitHub integration (get write access to the repos), it is necessary to link your ASF id and GitHub account here: https://gitbox.apache.org/setup/
After linking the accounts, it is possible to handle pull requests the same as any other repo. It is also possible to use the GitHub remote instead of the Apache one.
If there are still any questions, please reply and add me as a recipient as well, as I am not subscribed to this mailing list ;)
- Roy
On 2018/12/15 18:49:07, Roy Lenferink <rl...@apache.org> wrote:
> I've created an issue with INFRA for this: https://issues.apache.org/jira/browse/INFRA-17450
>
> I'll post another message to this list when the migration has happened. Most of the times it will be moved within 4 hours.
>
> - Roy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
I've created an issue with INFRA for this: https://issues.apache.org/jira/browse/INFRA-17450
I'll post another message to this list when the migration has happened. Most of the times it will be moved within 4 hours.
- Roy
On 2018/12/12 21:15:01, Gary Gregory <ga...@gmail.com> wrote:
>
> +1 if I've not already said so.
>
> Gary
>
>
> >
> > +1 (very much in favor)
> >
> > Oleg
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Dec 12, 2018 at 2:14 PM Oleg Kalnichevski <ol...@apache.org> wrote:
> On Wed, 2018-12-12 at 19:22 +0100, Roy Lenferink wrote:
> > Hi folks,
> >
> > Does anyone have a problem with starting the process to migrate the
> > existing HttpComponents git-wip-us repos [1-5] to gitbox?
> > This means integrated access and easy PRs on the repos (write access
> > to the
> > GitHub repos).
> >
>
+1 if I've not already said so.
Gary
>
> +1 (very much in favor)
>
> Oleg
>
>
> > 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, I'll create a ticket with INFRA for
> > moving over
> > the repositories to GitBox.
> >
> > - Roy
> >
> > [1]
> > https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-client.git
> > [2]
> > https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-core.git
> > [3]
> > https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-parent.git
> > [4]
> > https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-stylecheck.git
> > [5]
> > https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-website.git
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > project's dev list :-).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
Re: Fwd: [NOTICE] Mandatory relocation of Apache git repositories
on git-wip-us.apache.org
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Wed, 2018-12-12 at 19:22 +0100, Roy Lenferink wrote:
> Hi folks,
>
> Does anyone have a problem with starting the process to migrate the
> existing HttpComponents git-wip-us repos [1-5] to gitbox?
> This means integrated access and easy PRs on the repos (write access
> to the
> GitHub repos).
>
+1 (very much in favor)
Oleg
> 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, I'll create a ticket with INFRA for
> moving over
> the repositories to GitBox.
>
> - Roy
>
> [1]
> https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-client.git
> [2]
> https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-core.git
> [3]
> https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-parent.git
> [4]
> https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-stylecheck.git
> [5]
> https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-website.git
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
Hi folks,
Does anyone have a problem with starting the process to migrate the
existing HttpComponents git-wip-us repos [1-5] 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, I'll create a ticket with INFRA for moving over
the repositories to GitBox.
- Roy
[1] https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-client.git
[2] https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-core.git
[3] https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-parent.git
[4] https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-stylecheck.git
[5] https://git-wip-us.apache.org/repos/asf/?p=httpcomponents-website.git
---------- Forwarded message ---------
From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Felix Cheung <fe...@apache.org>.
+1
On Mon, Dec 10, 2018 at 12:56 PM Roy Lenferink <rl...@apache.org>
wrote:
> Hi all,
>
> The Apache Incubator is still having a repository on git-wip-us as well
> [1].
>
> Does anyone have a problem with moving over the incubator repository to
> gitbox voluntarily?
> This means integrated access and easy PRs (write access to the GitHub
> repo).
>
> We need to document support for the decision from a mailing list post, so
> here it is.
>
> - Roy
>
> [1] https://git-wip-us.apache.org/repos/asf/incubator.git
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Matt Sicker <bo...@gmail.com>.
+1
We’ve been using it at Logging for a little while now and love it.
On Tue, Dec 11, 2018 at 08:03, Dave Meikle <dm...@apache.org> wrote:
> +1 from me too.
>
> Cheers,
> Dave
>
> On Tue, 11 Dec 2018 at 05:43, Myrle Krantz <my...@apache.org> wrote:
>
> > +1 gitbox is wonderful.
> >
> > On Tue, Dec 11, 2018 at 3:33 AM Dave Fisher <da...@comcast.net>
> wrote:
> >
> > > +1
> > >
> > > Sent from my iPhone
> > >
> > > > On Dec 10, 2018, at 6:19 PM, Paul King <pa...@asert.com.au> wrote:
> > > >
> > > > +1
> > > >
> > > >> On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink <
> rlenferink@apache.org>
> > > wrote:
> > > >>
> > > >> Hi all,
> > > >>
> > > >> The Apache Incubator is still having a repository on git-wip-us as
> > well
> > > >> [1].
> > > >>
> > > >> Does anyone have a problem with moving over the incubator repository
> > to
> > > >> gitbox voluntarily?
> > > >> This means integrated access and easy PRs (write access to the
> GitHub
> > > >> repo).
> > > >>
> > > >> We need to document support for the decision from a mailing list
> post,
> > > so
> > > >> here it is.
> > > >>
> > > >> - Roy
> > > >>
> > > >> [1] https://git-wip-us.apache.org/repos/asf/incubator.git
> > > >>
> > > >> ---------- Forwarded message ---------
> > > >> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > >> project's dev list :-).
> > > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Dave Meikle <dm...@apache.org>.
+1 from me too.
Cheers,
Dave
On Tue, 11 Dec 2018 at 05:43, Myrle Krantz <my...@apache.org> wrote:
> +1 gitbox is wonderful.
>
> On Tue, Dec 11, 2018 at 3:33 AM Dave Fisher <da...@comcast.net> wrote:
>
> > +1
> >
> > Sent from my iPhone
> >
> > > On Dec 10, 2018, at 6:19 PM, Paul King <pa...@asert.com.au> wrote:
> > >
> > > +1
> > >
> > >> On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink <rl...@apache.org>
> > wrote:
> > >>
> > >> Hi all,
> > >>
> > >> The Apache Incubator is still having a repository on git-wip-us as
> well
> > >> [1].
> > >>
> > >> Does anyone have a problem with moving over the incubator repository
> to
> > >> gitbox voluntarily?
> > >> This means integrated access and easy PRs (write access to the GitHub
> > >> repo).
> > >>
> > >> We need to document support for the decision from a mailing list post,
> > so
> > >> here it is.
> > >>
> > >> - Roy
> > >>
> > >> [1] https://git-wip-us.apache.org/repos/asf/incubator.git
> > >>
> > >> ---------- Forwarded message ---------
> > >> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > >> project's dev list :-).
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by sebb <se...@gmail.com>.
On Wed, 12 Dec 2018 at 18:03, Roy Lenferink <rl...@apache.org> wrote:
>
> The repo has moved to gitbox now [1]. The jenkins job still needs to be
> updated though [2]. If someone with the appropriate permissions can help
> with that, that would be nice.
Done
> - Roy
>
> [1] https://gitbox.apache.org/repos/asf/incubator.git
> [2] https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/
>
> Op di 11 dec. 2018 om 17:43 schreef Roy Lenferink <le...@gmail.com>:
>
> > Perfect. I have created an issue with INFRA for this and will post a
> > message to the list once the repo has been migrated.
> >
> > In the meantime I tried to update the Jenkins job responsible for
> > generating the Incubator website, but I noticed I haven't got enough
> > permisssions to do so.
> > Can a PMC chair assist and maybe add me to the hudson-jobadmin group in
> > whimsy?
> >
> > Thanks
> > - Roy
> >
> > Op di 11 dec. 2018 om 07:07 schreef Justin Mclean <
> > justin@classsoftware.com>:
> >
> >> +1 no objections from me
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
The repo has moved to gitbox now [1]. The jenkins job still needs to be
updated though [2]. If someone with the appropriate permissions can help
with that, that would be nice.
- Roy
[1] https://gitbox.apache.org/repos/asf/incubator.git
[2] https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/
Op di 11 dec. 2018 om 17:43 schreef Roy Lenferink <le...@gmail.com>:
> Perfect. I have created an issue with INFRA for this and will post a
> message to the list once the repo has been migrated.
>
> In the meantime I tried to update the Jenkins job responsible for
> generating the Incubator website, but I noticed I haven't got enough
> permisssions to do so.
> Can a PMC chair assist and maybe add me to the hudson-jobadmin group in
> whimsy?
>
> Thanks
> - Roy
>
> Op di 11 dec. 2018 om 07:07 schreef Justin Mclean <
> justin@classsoftware.com>:
>
>> +1 no objections from me
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <le...@gmail.com>.
Perfect. I have created an issue with INFRA for this and will post a
message to the list once the repo has been migrated.
In the meantime I tried to update the Jenkins job responsible for
generating the Incubator website, but I noticed I haven't got enough
permisssions to do so.
Can a PMC chair assist and maybe add me to the hudson-jobadmin group in
whimsy?
Thanks
- Roy
Op di 11 dec. 2018 om 07:07 schreef Justin Mclean <justin@classsoftware.com
>:
> +1 no objections from me
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Justin Mclean <ju...@classsoftware.com>.
+1 no objections from me
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Myrle Krantz <my...@apache.org>.
+1 gitbox is wonderful.
On Tue, Dec 11, 2018 at 3:33 AM Dave Fisher <da...@comcast.net> wrote:
> +1
>
> Sent from my iPhone
>
> > On Dec 10, 2018, at 6:19 PM, Paul King <pa...@asert.com.au> wrote:
> >
> > +1
> >
> >> On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink <rl...@apache.org>
> wrote:
> >>
> >> Hi all,
> >>
> >> The Apache Incubator is still having a repository on git-wip-us as well
> >> [1].
> >>
> >> Does anyone have a problem with moving over the incubator repository to
> >> gitbox voluntarily?
> >> This means integrated access and easy PRs (write access to the GitHub
> >> repo).
> >>
> >> We need to document support for the decision from a mailing list post,
> so
> >> here it is.
> >>
> >> - Roy
> >>
> >> [1] https://git-wip-us.apache.org/repos/asf/incubator.git
> >>
> >> ---------- Forwarded message ---------
> >> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> >> project's dev list :-).
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Dave Fisher <da...@comcast.net>.
+1
Sent from my iPhone
> On Dec 10, 2018, at 6:19 PM, Paul King <pa...@asert.com.au> wrote:
>
> +1
>
>> On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink <rl...@apache.org> wrote:
>>
>> Hi all,
>>
>> The Apache Incubator is still having a repository on git-wip-us as well
>> [1].
>>
>> Does anyone have a problem with moving over the incubator repository to
>> gitbox voluntarily?
>> This means integrated access and easy PRs (write access to the GitHub
>> repo).
>>
>> We need to document support for the decision from a mailing list post, so
>> here it is.
>>
>> - Roy
>>
>> [1] https://git-wip-us.apache.org/repos/asf/incubator.git
>>
>> ---------- Forwarded message ---------
>> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
>> project's dev list :-).
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Paul King <pa...@asert.com.au>.
+1
On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink <rl...@apache.org> wrote:
> Hi all,
>
> The Apache Incubator is still having a repository on git-wip-us as well
> [1].
>
> Does anyone have a problem with moving over the incubator repository to
> gitbox voluntarily?
> This means integrated access and easy PRs (write access to the GitHub
> repo).
>
> We need to document support for the decision from a mailing list post, so
> here it is.
>
> - Roy
>
> [1] https://git-wip-us.apache.org/repos/asf/incubator.git
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
[DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
Hi all,
The Apache Incubator is still having a repository on git-wip-us as well [1].
Does anyone have a problem with moving over the incubator repository to
gitbox voluntarily?
This means integrated access and easy PRs (write access to the GitHub repo).
We need to document support for the decision from a mailing list post, so
here it is.
- Roy
[1] https://git-wip-us.apache.org/repos/asf/incubator.git
---------- Forwarded message ---------
From: Daniel Gruno <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by mibo <mi...@apache.org>.
Wow, the Infra guys are really fast... Thanks to Daniel ;o)
Now the (new) Apache Olingo GitBox repos are:
- https://gitbox.apache.org/repos/asf/olingo-odata2.git
- https://gitbox.apache.org/repos/asf/olingo-odata4.git
- https://gitbox.apache.org/repos/asf/olingo-odata3-js.git
- https://gitbox.apache.org/repos/asf/olingo-odata4-js.git
Kind Regards, Michael
On Tue, Dec 11, 2018 at 9:19 PM Dave Fisher <da...@comcast.net> wrote:
>
> Yes, I would say do.
>
> Here’s my +1
>
> Sent from my iPhone
>
> > On Dec 11, 2018, at 12:00 PM, mibo <mi...@apache.org> wrote:
> >
> > Hi All,
> >
> > With currently 5 votes (see below) and no vetos IMHO we have a consensus (or?).
> > Christian
> > Ramesh
> > Francesco
> > Archana
> > Michael
> >
> > Based on this I created the JIRA issue: https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17400
> > So if there are no sudden objections we with Olingo will be part of the 'Voluntary relocation' ;o)
> >
> > Kind Regards, Michael
> >
> > Am 11. Dez. 2018, 06:03 +0100 schrieb Rai, Archana <ar...@sap.com>:
> >> +1
> >>
> >> -----Original Message-----
> >> From: Amend, Christian <ch...@sap.com>
> >> Sent: Monday, December 10, 2018 2:40 PM
> >> To: 'dev@olingo.apache.org' <de...@olingo.apache.org>
> >> Subject: [CAUTION] FW: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
> >>
> >> Hi Olingo Devs,
> >>
> >> the Git Repository will be moved. If we want to volunteer for the first wave of relocations we need to react until January 9th.
> >>
> >> WDYT?
> >>
> >> Best Regards,
> >> Christian
> >>
> >> -----Original Message-----
> >> From: Daniel Gruno <hu...@apache.org>
> >> Sent: Freitag, 7. Dezember 2018 17:53
> >> To: users@infra.apache.org
> >> 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 users@infra.apache.org, not your
> >> project's dev list :-).
> >>
> >>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Dave Fisher <da...@comcast.net>.
Yes, I would say do.
Here’s my +1
Sent from my iPhone
> On Dec 11, 2018, at 12:00 PM, mibo <mi...@apache.org> wrote:
>
> Hi All,
>
> With currently 5 votes (see below) and no vetos IMHO we have a consensus (or?).
> Christian
> Ramesh
> Francesco
> Archana
> Michael
>
> Based on this I created the JIRA issue: https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17400
> So if there are no sudden objections we with Olingo will be part of the 'Voluntary relocation' ;o)
>
> Kind Regards, Michael
>
> Am 11. Dez. 2018, 06:03 +0100 schrieb Rai, Archana <ar...@sap.com>:
>> +1
>>
>> -----Original Message-----
>> From: Amend, Christian <ch...@sap.com>
>> Sent: Monday, December 10, 2018 2:40 PM
>> To: 'dev@olingo.apache.org' <de...@olingo.apache.org>
>> Subject: [CAUTION] FW: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
>>
>> Hi Olingo Devs,
>>
>> the Git Repository will be moved. If we want to volunteer for the first wave of relocations we need to react until January 9th.
>>
>> WDYT?
>>
>> Best Regards,
>> Christian
>>
>> -----Original Message-----
>> From: Daniel Gruno <hu...@apache.org>
>> Sent: Freitag, 7. Dezember 2018 17:53
>> To: users@infra.apache.org
>> 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 users@infra.apache.org, not your
>> project's dev list :-).
>>
>>
RE: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by mibo <mi...@apache.org>.
Hi All,
With currently 5 votes (see below) and no vetos IMHO we have a consensus (or?).
Christian
Ramesh
Francesco
Archana
Michael
Based on this I created the JIRA issue: https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17400
So if there are no sudden objections we with Olingo will be part of the 'Voluntary relocation' ;o)
Kind Regards, Michael
Am 11. Dez. 2018, 06:03 +0100 schrieb Rai, Archana <ar...@sap.com>:
> +1
>
> -----Original Message-----
> From: Amend, Christian <ch...@sap.com>
> Sent: Monday, December 10, 2018 2:40 PM
> To: 'dev@olingo.apache.org' <de...@olingo.apache.org>
> Subject: [CAUTION] FW: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
>
> Hi Olingo Devs,
>
> the Git Repository will be moved. If we want to volunteer for the first wave of relocations we need to react until January 9th.
>
> WDYT?
>
> Best Regards,
> Christian
>
> -----Original Message-----
> From: Daniel Gruno <hu...@apache.org>
> Sent: Freitag, 7. Dezember 2018 17:53
> To: users@infra.apache.org
> 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 users@infra.apache.org, not your
> project's dev list :-).
>
>
RE: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by "Rai, Archana" <ar...@sap.com>.
+1
-----Original Message-----
From: Amend, Christian <ch...@sap.com>
Sent: Monday, December 10, 2018 2:40 PM
To: 'dev@olingo.apache.org' <de...@olingo.apache.org>
Subject: [CAUTION] FW: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Hi Olingo Devs,
the Git Repository will be moved. If we want to volunteer for the first wave of relocations we need to react until January 9th.
WDYT?
Best Regards,
Christian
-----Original Message-----
From: Daniel Gruno <hu...@apache.org>
Sent: Freitag, 7. Dezember 2018 17:53
To: users@infra.apache.org
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 users@infra.apache.org, not your
project's dev list :-).
Re: FW: [NOTICE] Mandatory relocation of Apache git
repositories on git-wip-us.apache.org
Posted by mibo <mi...@apache.org>.
+1 from me.
@Christian:
As we get our "Consensus in the project (documented via the mailing list)" do you plan to create the necessary JIRA ticket?
Regards, Michael
> - 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)
Am 10. Dez. 2018, 16:06 +0100 schrieb Francesco Chicchiriccò <il...@apache.org>:
> On 10/12/18 10:10, Amend, Christian wrote:
> > Hi Olingo Devs,
> >
> > the Git Repository will be moved. If we want to volunteer for the first wave of relocations we need to react until January 9th.
> >
> > WDYT?
>
> +1
>
> we did so a while ago in Syncope, was a good move.
>
> Regards.
>
> > -----Original Message-----
> > From: Daniel Gruno <hu...@apache.org>
> > Sent: Freitag, 7. Dezember 2018 17:53
> > To: users@infra.apache.org
> > 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 users@infra.apache.org, not your
> > project's dev list :-).
> >
> >
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Member at The Apache Software Foundation
> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
> http://home.apache.org/~ilgrosso/
>
Re: FW: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 10/12/18 10:10, Amend, Christian wrote:
> Hi Olingo Devs,
>
> the Git Repository will be moved. If we want to volunteer for the first wave of relocations we need to react until January 9th.
>
> WDYT?
+1
we did so a while ago in Syncope, was a good move.
Regards.
> -----Original Message-----
> From: Daniel Gruno <hu...@apache.org>
> Sent: Freitag, 7. Dezember 2018 17:53
> To: users@infra.apache.org
> 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 users@infra.apache.org, not your
> project's dev list :-).
>
>
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
Re: FW: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Ramesh Reddy <ra...@redhat.com>.
+1 please put in the request to move. GitHub makes accepting the patches a
whole lot simpler.
On Mon, Dec 10, 2018 at 3:10 AM Amend, Christian <ch...@sap.com>
wrote:
> Hi Olingo Devs,
>
> the Git Repository will be moved. If we want to volunteer for the first
> wave of relocations we need to react until January 9th.
>
> WDYT?
>
> Best Regards,
> Christian
>
> -----Original Message-----
> From: Daniel Gruno <hu...@apache.org>
> Sent: Freitag, 7. Dezember 2018 17:53
> To: users@infra.apache.org
> 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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
FW: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by "Amend, Christian" <ch...@sap.com>.
Hi Olingo Devs,
the Git Repository will be moved. If we want to volunteer for the first wave of relocations we need to react until January 9th.
WDYT?
Best Regards,
Christian
-----Original Message-----
From: Daniel Gruno <hu...@apache.org>
Sent: Freitag, 7. Dezember 2018 17:53
To: users@infra.apache.org
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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by William Lieurance <wi...@namikoda.com>.
I'm in favor of moving. Go for it. :-)
________________________________________
From: P. Ottlinger <po...@apache.org>
Sent: Saturday, December 8, 2018 1:36 PM
To: dev@tamaya.incubator.apache.org
Subject: Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Any objections or can I file an issue to move us over to the new system?
Thanks,
Phil
Am 07.12.18 um 17:52 schrieb Daniel Gruno:
> [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 :-).
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Anatole Tresch <at...@gmail.com>.
+1 for moving...
P. Ottlinger <po...@apache.org> schrieb am Sa., 8. Dez. 2018, 20:36:
> Any objections or can I file an issue to move us over to the new system?
>
> Thanks,
> Phil
>
> Am 07.12.18 um 17:52 schrieb Daniel Gruno:
> > [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 :-).
> >
> >
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Aaron Coburn <ac...@amherst.edu>.
+1 for migrating. Thanks for moving this forward.
Aaron
> On Dec 10, 2018, at 3:00 PM, Werner Keil <we...@gmail.com> wrote:
>
> +1 for moving, seems the standard way for all repositories, so better
> migrate.
>
> Werner
>
>
>
> On Mon, Dec 10, 2018 at 8:59 PM P. Ottlinger <po...@apache.org> wrote:
>
>> Am 08.12.18 um 20:36 schrieb P. Ottlinger:
>>> Any objections or can I file an issue to move us over to the new system?
>>
>> Filed
>> https://issues.apache.org/jira/browse/INFRA-17389
>> to trigger the migration.
>>
>> Let's see how things evolve and how powerful the github integration will
>> become :-)
>>
>> Phil
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Werner Keil <we...@gmail.com>.
+1 for moving, seems the standard way for all repositories, so better
migrate.
Werner
On Mon, Dec 10, 2018 at 8:59 PM P. Ottlinger <po...@apache.org> wrote:
> Am 08.12.18 um 20:36 schrieb P. Ottlinger:
> > Any objections or can I file an issue to move us over to the new system?
>
> Filed
> https://issues.apache.org/jira/browse/INFRA-17389
> to trigger the migration.
>
> Let's see how things evolve and how powerful the github integration will
> become :-)
>
> Phil
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by "P. Ottlinger" <po...@apache.org>.
Am 08.12.18 um 20:36 schrieb P. Ottlinger:
> Any objections or can I file an issue to move us over to the new system?
Filed
https://issues.apache.org/jira/browse/INFRA-17389
to trigger the migration.
Let's see how things evolve and how powerful the github integration will
become :-)
Phil
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by "P. Ottlinger" <po...@apache.org>.
Any objections or can I file an issue to move us over to the new system?
Thanks,
Phil
Am 07.12.18 um 17:52 schrieb Daniel Gruno:
> [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 :-).
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Kalyan Kumar Kalvagadda <kk...@cloudera.com.INVALID>.
I will be opening a INFRA ticket to move the repository to
gitbox.apache.org
*Thanks,Kalyan Kumar Kalvagadda* | Software Engineer
t. (469) 279- <0000000000>5732
cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
------------------------------
On Thu, Dec 13, 2018 at 3:45 AM Colm O hEigeartaigh <co...@apache.org>
wrote:
> +1.
>
> Colm.
>
> On Wed, Dec 12, 2018 at 5:34 PM Na Li <li...@cloudera.com.invalid>
> wrote:
>
> > Sergio,
> >
> > I prefer to move it sooner. Otherwise, we could forget when busy working
> on
> > other issues.
> >
> > Thanks,
> >
> > Lina
> >
> > On Tue, Dec 11, 2018 at 3:11 PM Sergio Pena
> > <se...@cloudera.com.invalid> wrote:
> >
> > > Hey team, the Sentry project is part of the git-wip.
> > > Do we want to move sooner and or later?
> > >
> > > - Sergio
> > >
> > > ---------- Forwarded message ---------
> > > From: Daniel Gruno <hu...@apache.org>
> > > Date: Fri, Dec 7, 2018 at 10:53 AM
> > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > git-wip-us.apache.org
> > > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > > project's dev list :-).
> > >
> >
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Colm O hEigeartaigh <co...@apache.org>.
+1.
Colm.
On Wed, Dec 12, 2018 at 5:34 PM Na Li <li...@cloudera.com.invalid> wrote:
> Sergio,
>
> I prefer to move it sooner. Otherwise, we could forget when busy working on
> other issues.
>
> Thanks,
>
> Lina
>
> On Tue, Dec 11, 2018 at 3:11 PM Sergio Pena
> <se...@cloudera.com.invalid> wrote:
>
> > Hey team, the Sentry project is part of the git-wip.
> > Do we want to move sooner and or later?
> >
> > - Sergio
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <hu...@apache.org>
> > Date: Fri, Dec 7, 2018 at 10:53 AM
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org
> > To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> > project's dev list :-).
> >
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Na Li <li...@cloudera.com.INVALID>.
Sergio,
I prefer to move it sooner. Otherwise, we could forget when busy working on
other issues.
Thanks,
Lina
On Tue, Dec 11, 2018 at 3:11 PM Sergio Pena
<se...@cloudera.com.invalid> wrote:
> Hey team, the Sentry project is part of the git-wip.
> Do we want to move sooner and or later?
>
> - Sergio
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018 at 10:53 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Sergio Pena <se...@cloudera.com.INVALID>.
Hey team, the Sentry project is part of the git-wip.
Do we want to move sooner and or later?
- Sergio
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018 at 10:53 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Thomas Bouron <th...@cloudsoft.io>.
Hey Geoff. All credits go to the infra team on this one, they were super
responsive!
On Fri, 14 Dec 2018 at 14:48 Geoff Macartney <ge...@gmail.com>
wrote:
> Wow that was quick. Thanks Thomas!
>
> Geoff
>
>
> On Fri, 14 Dec 2018 at 10:58 Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
> > Erratum: we now have a team for the people who did the Gitbox <-> GitHub
> > link, which gives committers the ability to merge PR directly from the
> > GitHub UI 🎉
> >
> >
> > On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <th...@cloudsoft.io>
> > wrote:
> >
> > > Migration successful[1]. It means that committers can push to either
> > > Gitbox or GitHub (still cannot merge directly through the UI though)
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> > >
> > > On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <thomas.bouron@cloudsoft.io
> >
> > > wrote:
> > >
> > >> Hi all.
> > >>
> > >> I think we have reached a consensus here as there is no +0 or -1.
> > >> I went ahead and created an INFRA ticket[1] to request the move.
> > >>
> > >> Best.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/INFRA-17440
> > >>
> > >> On Thu, 13 Dec 2018 at 13:53 John Campbell <
> > >> john.campbell@cloudsoftcorp.com> wrote:
> > >>
> > >>> No strong feelings, so +1 from me
> > >>>
> > >>> John Campbell
> > >>> Software Engineer
> > >>>
> > >>> Cloudsoft | Bringing Business to the Cloud
> > >>>
> > >>> E: John.campbell@cloudsoftcorp.com
> > >>> M: 07779 576614
> > >>> T: -
> > >>> L: www.linkedin.com/in/john-campbell-42105267
> > >>>
> > >>> Need a hand with AWS? Get a Free Consultation.
> > >>>
> > >>> > On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
> > >>> wrote:
> > >>> >
> > >>> > +1
> > >>> >
> > >>> > On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org>
> > >>> wrote:
> > >>> >
> > >>> >> Brooklyn team,
> > >>> >>
> > >>> >> Apart from myself, I don't think anyone has clearly come out in
> > >>> favour or
> > >>> >> opposed to this. I'd rather we got consensus and moved to gitbox
> > >>> early - so
> > >>> >> that if some people do object, we have time to work out the
> > >>> objections with
> > >>> >> infra, before we are involuntarily moved.
> > >>> >>
> > >>> >> Thoughts, anyone? Does this need a formal vote to get people
> > >>> responding?
> > >>> >>
> > >>> >> Richard.
> > >>> >>
> > >>> >>
> > >>> >> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
> > >>> 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 :-).
> > >>> >>>
> > >>> >>>
> > >>> >>>
> > >>> >>
> > >>> > --
> > >>> > Duncan Grant
> > >>> > Software Engineer
> > >>> >
> > >>> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the
> Cloud
> > >>> >
> > >>> > Need a hand with AWS? Get a Free Consultation.
> > >>> > <https://go.cloudsoft.io/healthcheck/>
> > >>>
> > >>> --
> > >> Thomas Bouron
> > >> Senior Software Engineer
> > >>
> > >> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >>
> > >> GitHub: https://github.com/tbouron
> > >> Twitter: https://twitter.com/eltibouron
> > >>
> > >> Need a hand with AWS? Get a Free Consultation.
> > >>
> > > --
> > > Thomas Bouron
> > > Senior Software Engineer
> > >
> > > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >
> > > GitHub: https://github.com/tbouron
> > > Twitter: https://twitter.com/eltibouron
> > >
> > > Need a hand with AWS? Get a Free Consultation.
> > >
> > --
> > Thomas Bouron
> > Senior Software Engineer
> >
> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >
> > GitHub: https://github.com/tbouron
> > Twitter: https://twitter.com/eltibouron
> >
> > Need a hand with AWS? Get a Free Consultation.
> >
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Geoff Macartney <ge...@gmail.com>.
Wow that was quick. Thanks Thomas!
Geoff
On Fri, 14 Dec 2018 at 10:58 Thomas Bouron <th...@cloudsoft.io>
wrote:
> Erratum: we now have a team for the people who did the Gitbox <-> GitHub
> link, which gives committers the ability to merge PR directly from the
> GitHub UI 🎉
>
>
> On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
> > Migration successful[1]. It means that committers can push to either
> > Gitbox or GitHub (still cannot merge directly through the UI though)
> >
> > [1]
> >
> https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> >
> > On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <th...@cloudsoft.io>
> > wrote:
> >
> >> Hi all.
> >>
> >> I think we have reached a consensus here as there is no +0 or -1.
> >> I went ahead and created an INFRA ticket[1] to request the move.
> >>
> >> Best.
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-17440
> >>
> >> On Thu, 13 Dec 2018 at 13:53 John Campbell <
> >> john.campbell@cloudsoftcorp.com> wrote:
> >>
> >>> No strong feelings, so +1 from me
> >>>
> >>> John Campbell
> >>> Software Engineer
> >>>
> >>> Cloudsoft | Bringing Business to the Cloud
> >>>
> >>> E: John.campbell@cloudsoftcorp.com
> >>> M: 07779 576614
> >>> T: -
> >>> L: www.linkedin.com/in/john-campbell-42105267
> >>>
> >>> Need a hand with AWS? Get a Free Consultation.
> >>>
> >>> > On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
> >>> wrote:
> >>> >
> >>> > +1
> >>> >
> >>> > On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org>
> >>> wrote:
> >>> >
> >>> >> Brooklyn team,
> >>> >>
> >>> >> Apart from myself, I don't think anyone has clearly come out in
> >>> favour or
> >>> >> opposed to this. I'd rather we got consensus and moved to gitbox
> >>> early - so
> >>> >> that if some people do object, we have time to work out the
> >>> objections with
> >>> >> infra, before we are involuntarily moved.
> >>> >>
> >>> >> Thoughts, anyone? Does this need a formal vote to get people
> >>> responding?
> >>> >>
> >>> >> Richard.
> >>> >>
> >>> >>
> >>> >> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
> >>> 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 :-).
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>
> >>> > --
> >>> > Duncan Grant
> >>> > Software Engineer
> >>> >
> >>> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >>> >
> >>> > Need a hand with AWS? Get a Free Consultation.
> >>> > <https://go.cloudsoft.io/healthcheck/>
> >>>
> >>> --
> >> Thomas Bouron
> >> Senior Software Engineer
> >>
> >> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >>
> >> GitHub: https://github.com/tbouron
> >> Twitter: https://twitter.com/eltibouron
> >>
> >> Need a hand with AWS? Get a Free Consultation.
> >>
> > --
> > Thomas Bouron
> > Senior Software Engineer
> >
> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >
> > GitHub: https://github.com/tbouron
> > Twitter: https://twitter.com/eltibouron
> >
> > Need a hand with AWS? Get a Free Consultation.
> >
> --
> Thomas Bouron
> Senior Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
> Need a hand with AWS? Get a Free Consultation.
>
[ACTION REQUIRED] Committers, link your ASF account to GitHub
Posted by Richard Downer <ri...@apache.org>.
If you are a current committer to Apache Brooklyn, and you would like to
use all the new features that Gitbox gives us, you will need to link your
GitHub and ASF accounts.
You can do this at https://gitbox.apache.org
Have fun with the big green "Merge Pull Request" button!!
Richard.
---------- Forwarded message ---------
From: Thomas Bouron <th...@cloudsoft.io>
Date: Fri, 14 Dec 2018 at 10:58
Subject: Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: <de...@brooklyn.apache.org>
Erratum: we now have a team for the people who did the Gitbox <-> GitHub
link, which gives committers the ability to merge PR directly from the
GitHub UI 🎉
On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <th...@cloudsoft.io>
wrote:
> Migration successful[1]. It means that committers can push to either
> Gitbox or GitHub (still cannot merge directly through the UI though)
>
> [1]
>
https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>
> On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
>> Hi all.
>>
>> I think we have reached a consensus here as there is no +0 or -1.
>> I went ahead and created an INFRA ticket[1] to request the move.
>>
>> Best.
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-17440
>>
>> On Thu, 13 Dec 2018 at 13:53 John Campbell <
>> john.campbell@cloudsoftcorp.com> wrote:
>>
>>> No strong feelings, so +1 from me
>>>
>>> John Campbell
>>> Software Engineer
>>>
>>> Cloudsoft | Bringing Business to the Cloud
>>>
>>> E: John.campbell@cloudsoftcorp.com
>>> M: 07779 576614
>>> T: -
>>> L: www.linkedin.com/in/john-campbell-42105267
>>>
>>> Need a hand with AWS? Get a Free Consultation.
>>>
>>> > On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
>>> wrote:
>>> >
>>> > +1
>>> >
>>> > On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org>
>>> wrote:
>>> >
>>> >> Brooklyn team,
>>> >>
>>> >> Apart from myself, I don't think anyone has clearly come out in
>>> favour or
>>> >> opposed to this. I'd rather we got consensus and moved to gitbox
>>> early - so
>>> >> that if some people do object, we have time to work out the
>>> objections with
>>> >> infra, before we are involuntarily moved.
>>> >>
>>> >> Thoughts, anyone? Does this need a formal vote to get people
>>> responding?
>>> >>
>>> >> Richard.
>>> >>
>>> >>
>>> >> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
>>> 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 :-).
>>> >>>
>>> >>>
>>> >>>
>>> >>
>>> > --
>>> > Duncan Grant
>>> > Software Engineer
>>> >
>>> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>> >
>>> > Need a hand with AWS? Get a Free Consultation.
>>> > <https://go.cloudsoft.io/healthcheck/>
>>>
>>> --
>> Thomas Bouron
>> Senior Software Engineer
>>
>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>
>> GitHub: https://github.com/tbouron
>> Twitter: https://twitter.com/eltibouron
>>
>> Need a hand with AWS? Get a Free Consultation.
>>
> --
> Thomas Bouron
> Senior Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
> Need a hand with AWS? Get a Free Consultation.
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: Brooklyn git -- git-wip-us GONE now gitbox or github
Posted by Thomas Bouron <th...@cloudsoft.io>.
I kept the Gitbox remote just in case. But I agree with you Geoff, we don't
need another remote anymore.
On Fri, 14 Dec 2018 at 22:57 Geoff Macartney <ge...@gmail.com>
wrote:
> Do we even need to have a remote for git-wip-us any more? Now that we can
> merge on Github I've removed the repo I had for merging PRs altogether!
>
>
>
>
>
> On Fri, 14 Dec 2018 at 12:28 Alex Heneveld <
> alex.heneveld@cloudsoftcorp.com>
> wrote:
>
> >
> > As per thread below: my `git pull` just failed, but this command in the
> > root brooklyn dir worked seamlessly for me:
> >
> > * for x in .git/{config,modules/*/config} ; do sed -i.bk
> > s/git-wip-us/gitbox/g $x ; done**
> > *
> > (I use submodules; slight tweaks should take care of it for other
> > topologies.)
> >
> > Best
> > Alex
> >
> >
> > On 14/12/2018 10:52, Thomas Bouron wrote:
> > > Erratum: we now have a team for the people who did the Gitbox <->
> GitHub
> > > link, which gives committers the ability to merge PR directly from the
> > > GitHub UI 🎉
> > >
> > >
> > > On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <thomas.bouron@cloudsoft.io
> >
> > > wrote:
> > >
> > >> Migration successful[1]. It means that committers can push to either
> > >> Gitbox or GitHub (still cannot merge directly through the UI though)
> > >>
> > >> [1]
> > >>
> >
> https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> > >>
> > >> On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <
> thomas.bouron@cloudsoft.io>
> > >> wrote:
> > >>
> > >>> Hi all.
> > >>>
> > >>> I think we have reached a consensus here as there is no +0 or -1.
> > >>> I went ahead and created an INFRA ticket[1] to request the move.
> > >>>
> > >>> Best.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/INFRA-17440
> > >>>
> > >>> On Thu, 13 Dec 2018 at 13:53 John Campbell <
> > >>> john.campbell@cloudsoftcorp.com> wrote:
> > >>>
> > >>>> No strong feelings, so +1 from me
> > >>>>
> > >>>> John Campbell
> > >>>> Software Engineer
> > >>>>
> > >>>> Cloudsoft | Bringing Business to the Cloud
> > >>>>
> > >>>> E: John.campbell@cloudsoftcorp.com
> > >>>> M: 07779 576614
> > >>>> T: -
> > >>>> L: www.linkedin.com/in/john-campbell-42105267
> > >>>>
> > >>>> Need a hand with AWS? Get a Free Consultation.
> > >>>>
> > >>>>> On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
> > >>>> wrote:
> > >>>>> +1
> > >>>>>
> > >>>>> On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org>
> > >>>> wrote:
> > >>>>>> Brooklyn team,
> > >>>>>>
> > >>>>>> Apart from myself, I don't think anyone has clearly come out in
> > >>>> favour or
> > >>>>>> opposed to this. I'd rather we got consensus and moved to gitbox
> > >>>> early - so
> > >>>>>> that if some people do object, we have time to work out the
> > >>>> objections with
> > >>>>>> infra, before we are involuntarily moved.
> > >>>>>>
> > >>>>>> Thoughts, anyone? Does this need a formal vote to get people
> > >>>> responding?
> > >>>>>> Richard.
> > >>>>>>
> > >>>>>>
> > >>>>>> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
> > >>>> 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 :-).
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>> --
> > >>>>> Duncan Grant
> > >>>>> Software Engineer
> > >>>>>
> > >>>>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the
> Cloud
> > >>>>>
> > >>>>> Need a hand with AWS? Get a Free Consultation.
> > >>>>> <https://go.cloudsoft.io/healthcheck/>
> > >>>> --
> > >>> Thomas Bouron
> > >>> Senior Software Engineer
> > >>>
> > >>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >>>
> > >>> GitHub: https://github.com/tbouron
> > >>> Twitter: https://twitter.com/eltibouron
> > >>>
> > >>> Need a hand with AWS? Get a Free Consultation.
> > >>>
> > >> --
> > >> Thomas Bouron
> > >> Senior Software Engineer
> > >>
> > >> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >>
> > >> GitHub: https://github.com/tbouron
> > >> Twitter: https://twitter.com/eltibouron
> > >>
> > >> Need a hand with AWS? Get a Free Consultation.
> > >>
> >
> >
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: Brooklyn git -- git-wip-us GONE now gitbox or github
Posted by Geoff Macartney <ge...@gmail.com>.
Do we even need to have a remote for git-wip-us any more? Now that we can
merge on Github I've removed the repo I had for merging PRs altogether!
On Fri, 14 Dec 2018 at 12:28 Alex Heneveld <al...@cloudsoftcorp.com>
wrote:
>
> As per thread below: my `git pull` just failed, but this command in the
> root brooklyn dir worked seamlessly for me:
>
> * for x in .git/{config,modules/*/config} ; do sed -i.bk
> s/git-wip-us/gitbox/g $x ; done**
> *
> (I use submodules; slight tweaks should take care of it for other
> topologies.)
>
> Best
> Alex
>
>
> On 14/12/2018 10:52, Thomas Bouron wrote:
> > Erratum: we now have a team for the people who did the Gitbox <-> GitHub
> > link, which gives committers the ability to merge PR directly from the
> > GitHub UI 🎉
> >
> >
> > On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <th...@cloudsoft.io>
> > wrote:
> >
> >> Migration successful[1]. It means that committers can push to either
> >> Gitbox or GitHub (still cannot merge directly through the UI though)
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> >>
> >> On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <th...@cloudsoft.io>
> >> wrote:
> >>
> >>> Hi all.
> >>>
> >>> I think we have reached a consensus here as there is no +0 or -1.
> >>> I went ahead and created an INFRA ticket[1] to request the move.
> >>>
> >>> Best.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/INFRA-17440
> >>>
> >>> On Thu, 13 Dec 2018 at 13:53 John Campbell <
> >>> john.campbell@cloudsoftcorp.com> wrote:
> >>>
> >>>> No strong feelings, so +1 from me
> >>>>
> >>>> John Campbell
> >>>> Software Engineer
> >>>>
> >>>> Cloudsoft | Bringing Business to the Cloud
> >>>>
> >>>> E: John.campbell@cloudsoftcorp.com
> >>>> M: 07779 576614
> >>>> T: -
> >>>> L: www.linkedin.com/in/john-campbell-42105267
> >>>>
> >>>> Need a hand with AWS? Get a Free Consultation.
> >>>>
> >>>>> On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
> >>>> wrote:
> >>>>> +1
> >>>>>
> >>>>> On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org>
> >>>> wrote:
> >>>>>> Brooklyn team,
> >>>>>>
> >>>>>> Apart from myself, I don't think anyone has clearly come out in
> >>>> favour or
> >>>>>> opposed to this. I'd rather we got consensus and moved to gitbox
> >>>> early - so
> >>>>>> that if some people do object, we have time to work out the
> >>>> objections with
> >>>>>> infra, before we are involuntarily moved.
> >>>>>>
> >>>>>> Thoughts, anyone? Does this need a formal vote to get people
> >>>> responding?
> >>>>>> Richard.
> >>>>>>
> >>>>>>
> >>>>>> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
> >>>> 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 :-).
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>> --
> >>>>> Duncan Grant
> >>>>> Software Engineer
> >>>>>
> >>>>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >>>>>
> >>>>> Need a hand with AWS? Get a Free Consultation.
> >>>>> <https://go.cloudsoft.io/healthcheck/>
> >>>> --
> >>> Thomas Bouron
> >>> Senior Software Engineer
> >>>
> >>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >>>
> >>> GitHub: https://github.com/tbouron
> >>> Twitter: https://twitter.com/eltibouron
> >>>
> >>> Need a hand with AWS? Get a Free Consultation.
> >>>
> >> --
> >> Thomas Bouron
> >> Senior Software Engineer
> >>
> >> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >>
> >> GitHub: https://github.com/tbouron
> >> Twitter: https://twitter.com/eltibouron
> >>
> >> Need a hand with AWS? Get a Free Consultation.
> >>
>
>
Brooklyn git -- git-wip-us GONE now gitbox or github
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
As per thread below: my `git pull` just failed, but this command in the
root brooklyn dir worked seamlessly for me:
* for x in .git/{config,modules/*/config} ; do sed -i.bk
s/git-wip-us/gitbox/g $x ; done**
*
(I use submodules; slight tweaks should take care of it for other
topologies.)
Best
Alex
On 14/12/2018 10:52, Thomas Bouron wrote:
> Erratum: we now have a team for the people who did the Gitbox <-> GitHub
> link, which gives committers the ability to merge PR directly from the
> GitHub UI 🎉
>
>
> On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
>> Migration successful[1]. It means that committers can push to either
>> Gitbox or GitHub (still cannot merge directly through the UI though)
>>
>> [1]
>> https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>>
>> On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <th...@cloudsoft.io>
>> wrote:
>>
>>> Hi all.
>>>
>>> I think we have reached a consensus here as there is no +0 or -1.
>>> I went ahead and created an INFRA ticket[1] to request the move.
>>>
>>> Best.
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-17440
>>>
>>> On Thu, 13 Dec 2018 at 13:53 John Campbell <
>>> john.campbell@cloudsoftcorp.com> wrote:
>>>
>>>> No strong feelings, so +1 from me
>>>>
>>>> John Campbell
>>>> Software Engineer
>>>>
>>>> Cloudsoft | Bringing Business to the Cloud
>>>>
>>>> E: John.campbell@cloudsoftcorp.com
>>>> M: 07779 576614
>>>> T: -
>>>> L: www.linkedin.com/in/john-campbell-42105267
>>>>
>>>> Need a hand with AWS? Get a Free Consultation.
>>>>
>>>>> On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
>>>> wrote:
>>>>> +1
>>>>>
>>>>> On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org>
>>>> wrote:
>>>>>> Brooklyn team,
>>>>>>
>>>>>> Apart from myself, I don't think anyone has clearly come out in
>>>> favour or
>>>>>> opposed to this. I'd rather we got consensus and moved to gitbox
>>>> early - so
>>>>>> that if some people do object, we have time to work out the
>>>> objections with
>>>>>> infra, before we are involuntarily moved.
>>>>>>
>>>>>> Thoughts, anyone? Does this need a formal vote to get people
>>>> responding?
>>>>>> Richard.
>>>>>>
>>>>>>
>>>>>> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
>>>> 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 :-).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> --
>>>>> Duncan Grant
>>>>> Software Engineer
>>>>>
>>>>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>>>>
>>>>> Need a hand with AWS? Get a Free Consultation.
>>>>> <https://go.cloudsoft.io/healthcheck/>
>>>> --
>>> Thomas Bouron
>>> Senior Software Engineer
>>>
>>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>>
>>> GitHub: https://github.com/tbouron
>>> Twitter: https://twitter.com/eltibouron
>>>
>>> Need a hand with AWS? Get a Free Consultation.
>>>
>> --
>> Thomas Bouron
>> Senior Software Engineer
>>
>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>
>> GitHub: https://github.com/tbouron
>> Twitter: https://twitter.com/eltibouron
>>
>> Need a hand with AWS? Get a Free Consultation.
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Thomas Bouron <th...@cloudsoft.io>.
Erratum: we now have a team for the people who did the Gitbox <-> GitHub
link, which gives committers the ability to merge PR directly from the
GitHub UI 🎉
On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <th...@cloudsoft.io>
wrote:
> Migration successful[1]. It means that committers can push to either
> Gitbox or GitHub (still cannot merge directly through the UI though)
>
> [1]
> https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>
> On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
>> Hi all.
>>
>> I think we have reached a consensus here as there is no +0 or -1.
>> I went ahead and created an INFRA ticket[1] to request the move.
>>
>> Best.
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-17440
>>
>> On Thu, 13 Dec 2018 at 13:53 John Campbell <
>> john.campbell@cloudsoftcorp.com> wrote:
>>
>>> No strong feelings, so +1 from me
>>>
>>> John Campbell
>>> Software Engineer
>>>
>>> Cloudsoft | Bringing Business to the Cloud
>>>
>>> E: John.campbell@cloudsoftcorp.com
>>> M: 07779 576614
>>> T: -
>>> L: www.linkedin.com/in/john-campbell-42105267
>>>
>>> Need a hand with AWS? Get a Free Consultation.
>>>
>>> > On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
>>> wrote:
>>> >
>>> > +1
>>> >
>>> > On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org>
>>> wrote:
>>> >
>>> >> Brooklyn team,
>>> >>
>>> >> Apart from myself, I don't think anyone has clearly come out in
>>> favour or
>>> >> opposed to this. I'd rather we got consensus and moved to gitbox
>>> early - so
>>> >> that if some people do object, we have time to work out the
>>> objections with
>>> >> infra, before we are involuntarily moved.
>>> >>
>>> >> Thoughts, anyone? Does this need a formal vote to get people
>>> responding?
>>> >>
>>> >> Richard.
>>> >>
>>> >>
>>> >> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
>>> 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 :-).
>>> >>>
>>> >>>
>>> >>>
>>> >>
>>> > --
>>> > Duncan Grant
>>> > Software Engineer
>>> >
>>> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>> >
>>> > Need a hand with AWS? Get a Free Consultation.
>>> > <https://go.cloudsoft.io/healthcheck/>
>>>
>>> --
>> Thomas Bouron
>> Senior Software Engineer
>>
>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>
>> GitHub: https://github.com/tbouron
>> Twitter: https://twitter.com/eltibouron
>>
>> Need a hand with AWS? Get a Free Consultation.
>>
> --
> Thomas Bouron
> Senior Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
> Need a hand with AWS? Get a Free Consultation.
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Thomas Bouron <th...@cloudsoft.io>.
Migration successful[1]. It means that committers can push to either Gitbox
or GitHub (still cannot merge directly through the UI though)
[1]
https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <th...@cloudsoft.io>
wrote:
> Hi all.
>
> I think we have reached a consensus here as there is no +0 or -1.
> I went ahead and created an INFRA ticket[1] to request the move.
>
> Best.
>
> [1] https://issues.apache.org/jira/browse/INFRA-17440
>
> On Thu, 13 Dec 2018 at 13:53 John Campbell <
> john.campbell@cloudsoftcorp.com> wrote:
>
>> No strong feelings, so +1 from me
>>
>> John Campbell
>> Software Engineer
>>
>> Cloudsoft | Bringing Business to the Cloud
>>
>> E: John.campbell@cloudsoftcorp.com
>> M: 07779 576614
>> T: -
>> L: www.linkedin.com/in/john-campbell-42105267
>>
>> Need a hand with AWS? Get a Free Consultation.
>>
>> > On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
>> wrote:
>> >
>> > +1
>> >
>> > On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org> wrote:
>> >
>> >> Brooklyn team,
>> >>
>> >> Apart from myself, I don't think anyone has clearly come out in favour
>> or
>> >> opposed to this. I'd rather we got consensus and moved to gitbox early
>> - so
>> >> that if some people do object, we have time to work out the objections
>> with
>> >> infra, before we are involuntarily moved.
>> >>
>> >> Thoughts, anyone? Does this need a formal vote to get people
>> responding?
>> >>
>> >> Richard.
>> >>
>> >>
>> >> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
>> 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 :-).
>> >>>
>> >>>
>> >>>
>> >>
>> > --
>> > Duncan Grant
>> > Software Engineer
>> >
>> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>> >
>> > Need a hand with AWS? Get a Free Consultation.
>> > <https://go.cloudsoft.io/healthcheck/>
>>
>> --
> Thomas Bouron
> Senior Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
> Need a hand with AWS? Get a Free Consultation.
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Thomas Bouron <th...@cloudsoft.io>.
Hi all.
I think we have reached a consensus here as there is no +0 or -1.
I went ahead and created an INFRA ticket[1] to request the move.
Best.
[1] https://issues.apache.org/jira/browse/INFRA-17440
On Thu, 13 Dec 2018 at 13:53 John Campbell <jo...@cloudsoftcorp.com>
wrote:
> No strong feelings, so +1 from me
>
> John Campbell
> Software Engineer
>
> Cloudsoft | Bringing Business to the Cloud
>
> E: John.campbell@cloudsoftcorp.com
> M: 07779 576614
> T: -
> L: www.linkedin.com/in/john-campbell-42105267
>
> Need a hand with AWS? Get a Free Consultation.
>
> > On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io>
> wrote:
> >
> > +1
> >
> > On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org> wrote:
> >
> >> Brooklyn team,
> >>
> >> Apart from myself, I don't think anyone has clearly come out in favour
> or
> >> opposed to this. I'd rather we got consensus and moved to gitbox early
> - so
> >> that if some people do object, we have time to work out the objections
> with
> >> infra, before we are involuntarily moved.
> >>
> >> Thoughts, anyone? Does this need a formal vote to get people responding?
> >>
> >> Richard.
> >>
> >>
> >> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
> >>>
> >>>
> >>>
> >>
> > --
> > Duncan Grant
> > Software Engineer
> >
> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >
> > Need a hand with AWS? Get a Free Consultation.
> > <https://go.cloudsoft.io/healthcheck/>
>
> --
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by John Campbell <jo...@cloudsoftcorp.com>.
No strong feelings, so +1 from me
John Campbell
Software Engineer
Cloudsoft | Bringing Business to the Cloud
E: John.campbell@cloudsoftcorp.com
M: 07779 576614
T: -
L: www.linkedin.com/in/john-campbell-42105267
Need a hand with AWS? Get a Free Consultation.
> On 13 Dec 2018, at 09:31, Duncan Grant <du...@cloudsoft.io> wrote:
>
> +1
>
> On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org> wrote:
>
>> Brooklyn team,
>>
>> Apart from myself, I don't think anyone has clearly come out in favour or
>> opposed to this. I'd rather we got consensus and moved to gitbox early - so
>> that if some people do object, we have time to work out the objections with
>> infra, before we are involuntarily moved.
>>
>> Thoughts, anyone? Does this need a formal vote to get people responding?
>>
>> Richard.
>>
>>
>> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
>>>
>>>
>>>
>>
> --
> Duncan Grant
> Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> Need a hand with AWS? Get a Free Consultation.
> <https://go.cloudsoft.io/healthcheck/>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Duncan Grant <du...@cloudsoft.io>.
+1
On Wed, 12 Dec 2018 at 16:42 Richard Downer <ri...@apache.org> wrote:
> Brooklyn team,
>
> Apart from myself, I don't think anyone has clearly come out in favour or
> opposed to this. I'd rather we got consensus and moved to gitbox early - so
> that if some people do object, we have time to work out the objections with
> infra, before we are involuntarily moved.
>
> Thoughts, anyone? Does this need a formal vote to get people responding?
>
> Richard.
>
>
> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
> >
> >
> >
>
--
Duncan Grant
Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
Need a hand with AWS? Get a Free Consultation.
<https://go.cloudsoft.io/healthcheck/>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
+1
On 12/12/2018 17:08, Mark McKenna wrote:
> +1 Moving to gitbox makes sense
>
> On Wed, 12 Dec 2018, 16:56 Aled Sage <aled.sage@gmail.com wrote:
>
>> +1 from me.
>>
>> We need "Consensus in the project (documented via the mailing list)" - I
>> interpreted that as us needing a formal vote, but if an informal email
>> thread will do then that's fine with me
>>
>> Aled
>>
>>
>> On 12/12/2018 16:41, Richard Downer wrote:
>>> Brooklyn team,
>>>
>>> Apart from myself, I don't think anyone has clearly come out in favour or
>>> opposed to this. I'd rather we got consensus and moved to gitbox early -
>> so
>>> that if some people do object, we have time to work out the objections
>> with
>>> infra, before we are involuntarily moved.
>>>
>>> Thoughts, anyone? Does this need a formal vote to get people responding?
>>>
>>> Richard.
>>>
>>>
>>> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
>>>>
>>>>
>>>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Thomas Bouron <th...@cloudsoft.io>.
Sorry Richard, it's a +1 from me too
On Wed, 12 Dec 2018 at 17:08 Mark McKenna <m4...@apache.org> wrote:
> +1 Moving to gitbox makes sense
>
> On Wed, 12 Dec 2018, 16:56 Aled Sage <aled.sage@gmail.com wrote:
>
> > +1 from me.
> >
> > We need "Consensus in the project (documented via the mailing list)" - I
> > interpreted that as us needing a formal vote, but if an informal email
> > thread will do then that's fine with me
> >
> > Aled
> >
> >
> > On 12/12/2018 16:41, Richard Downer wrote:
> > > Brooklyn team,
> > >
> > > Apart from myself, I don't think anyone has clearly come out in favour
> or
> > > opposed to this. I'd rather we got consensus and moved to gitbox early
> -
> > so
> > > that if some people do object, we have time to work out the objections
> > with
> > > infra, before we are involuntarily moved.
> > >
> > > Thoughts, anyone? Does this need a formal vote to get people
> responding?
> > >
> > > Richard.
> > >
> > >
> > > On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
> 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 :-).
> > >>
> > >>
> > >>
> >
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Mark McKenna <m4...@apache.org>.
+1 Moving to gitbox makes sense
On Wed, 12 Dec 2018, 16:56 Aled Sage <aled.sage@gmail.com wrote:
> +1 from me.
>
> We need "Consensus in the project (documented via the mailing list)" - I
> interpreted that as us needing a formal vote, but if an informal email
> thread will do then that's fine with me
>
> Aled
>
>
> On 12/12/2018 16:41, Richard Downer wrote:
> > Brooklyn team,
> >
> > Apart from myself, I don't think anyone has clearly come out in favour or
> > opposed to this. I'd rather we got consensus and moved to gitbox early -
> so
> > that if some people do object, we have time to work out the objections
> with
> > infra, before we are involuntarily moved.
> >
> > Thoughts, anyone? Does this need a formal vote to get people responding?
> >
> > Richard.
> >
> >
> > On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
> >>
> >>
> >>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Juan Cabrerizo <ju...@cloudsoft.io>.
+1 for gitbox
On Wed, 12 Dec 2018 at 20:29, Paul Campbell <pa...@cloudsoft.io>
wrote:
> +1 move to gitbox
>
> On Wed, 12 Dec 2018, 16:56 Aled Sage <aled.sage@gmail.com wrote:
>
> > +1 from me.
> >
> > We need "Consensus in the project (documented via the mailing list)" - I
> > interpreted that as us needing a formal vote, but if an informal email
> > thread will do then that's fine with me
> >
> > Aled
> >
> >
> > On 12/12/2018 16:41, Richard Downer wrote:
> > > Brooklyn team,
> > >
> > > Apart from myself, I don't think anyone has clearly come out in favour
> or
> > > opposed to this. I'd rather we got consensus and moved to gitbox early
> -
> > so
> > > that if some people do object, we have time to work out the objections
> > with
> > > infra, before we are involuntarily moved.
> > >
> > > Thoughts, anyone? Does this need a formal vote to get people
> responding?
> > >
> > > Richard.
> > >
> > >
> > > On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org>
> 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 :-).
> > >>
> > >>
> > >>
> >
>
--
Juan Cabrerizo
Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
E: juan@cloudsoft.io
L: https://www.linkedin.com/in/juancabrerizo/
Need a hand with AWS? Get a Free Consultation.
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Paul Campbell <pa...@cloudsoft.io>.
+1 move to gitbox
On Wed, 12 Dec 2018, 16:56 Aled Sage <aled.sage@gmail.com wrote:
> +1 from me.
>
> We need "Consensus in the project (documented via the mailing list)" - I
> interpreted that as us needing a formal vote, but if an informal email
> thread will do then that's fine with me
>
> Aled
>
>
> On 12/12/2018 16:41, Richard Downer wrote:
> > Brooklyn team,
> >
> > Apart from myself, I don't think anyone has clearly come out in favour or
> > opposed to this. I'd rather we got consensus and moved to gitbox early -
> so
> > that if some people do object, we have time to work out the objections
> with
> > infra, before we are involuntarily moved.
> >
> > Thoughts, anyone? Does this need a formal vote to get people responding?
> >
> > Richard.
> >
> >
> > On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
> >>
> >>
> >>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Aled Sage <al...@gmail.com>.
+1 from me.
We need "Consensus in the project (documented via the mailing list)" - I
interpreted that as us needing a formal vote, but if an informal email
thread will do then that's fine with me
Aled
On 12/12/2018 16:41, Richard Downer wrote:
> Brooklyn team,
>
> Apart from myself, I don't think anyone has clearly come out in favour or
> opposed to this. I'd rather we got consensus and moved to gitbox early - so
> that if some people do object, we have time to work out the objections with
> infra, before we are involuntarily moved.
>
> Thoughts, anyone? Does this need a formal vote to get people responding?
>
> Richard.
>
>
> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
>>
>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Richard Downer <ri...@apache.org>.
Brooklyn team,
Apart from myself, I don't think anyone has clearly come out in favour or
opposed to this. I'd rather we got consensus and moved to gitbox early - so
that if some people do object, we have time to work out the objections with
infra, before we are involuntarily moved.
Thoughts, anyone? Does this need a formal vote to get people responding?
Richard.
On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <hu...@apache.org> 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 :-).
>
>
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Michael Miklavcic <mi...@gmail.com>.
If it's the option I'm picturing, I've used that for merging in a PR
against my PR. It's pretty simple and I don't recall it allowing options
for fitting our format. Unless I'm mistaken or that has changed, I'd
recommend our current workflow.
On Mon, Dec 10, 2018 at 3:26 PM Justin Leet <ju...@gmail.com> wrote:
> "merge pull request" just offers a couple ways to commit directly within
> GitHub (plain merge of all commits, squash down into one commit, and rebase
> the PR and merge it). I don't recall it allowing you to enforce a format
> on the PRs for the commit (e.g. <PR Name> (<CONTRIBUTOR> via <COMMITTER>)
> closes apache/metron#<PR NUM>), which unfortunately makes it less than
> ideal for us, since it's prone to typos. If you don't have that
> requirement, it's great, I've used it before on other projects.
>
> If someone knows if it's possible to set it up to autobuild the appropriate
> commit message, I'd probably be for it.
>
> On Mon, Dec 10, 2018 at 5:12 PM Nick Allen <ni...@nickallen.org> wrote:
>
> > Another thing to note here is that committers have admin access to the
> > Github account. This access is granted once you link your accounts using
> > the URL that Roy sent. It took about an hour for mine to sync.
> >
> > This means we can do things like close abandoned pull requests ourselves.
> > This also exposes the "merge pull request" button in Github. I am not
> > quite sure how that might differ from our current 'prepare-commit'
> script.
> > I would suggest we keep using the script until we figure that out.
> >
> >
> >
> >
> > On Mon, Dec 10, 2018 at 3:29 PM Roy Lenferink <rl...@apache.org>
> > wrote:
> >
> > > The repo has just moved to gitbox. Keep in mind the (ASF) remote has
> > > changed. The GitHub remote remains the same.
> > > I've opened a pull request to adapt the scripts to the gitbox URLs.
> > >
> > > In order to fully use the GitBox functionality, it is needed to link
> your
> > > ASF and GitHub account which can be done here:
> > > https://gitbox.apache.org/setup/
> > >
> > > When having any questions, don't hesitate to ask!
> > >
> > > - Roy
> > >
> > > Op ma 10 dec. 2018 om 20:11 schreef Roy Lenferink <
> rlenferink@apache.org
> > >:
> > >
> > > > I have created the issue with INFRA to move over from git-wip-us to
> > > > GitBox.
> > > > METRON-1931 is created for updating the scripts with the new GitBox
> > > > location. I'll start with this once the repositories are moved.
> > > >
> > > > - Roy
> > > >
> > > > Op ma 10 dec. 2018 om 15:52 schreef Nick Allen <ni...@nickallen.org>:
> > > >
> > > >> +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 <
> ottobackwards@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> +1
> > > >>>
> > > >>> We will need jiras and PR’s for updating our scripts post move
> > however.
> > > >>>
> > > >>
> > >
> >
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Justin Leet <ju...@gmail.com>.
"merge pull request" just offers a couple ways to commit directly within
GitHub (plain merge of all commits, squash down into one commit, and rebase
the PR and merge it). I don't recall it allowing you to enforce a format
on the PRs for the commit (e.g. <PR Name> (<CONTRIBUTOR> via <COMMITTER>)
closes apache/metron#<PR NUM>), which unfortunately makes it less than
ideal for us, since it's prone to typos. If you don't have that
requirement, it's great, I've used it before on other projects.
If someone knows if it's possible to set it up to autobuild the appropriate
commit message, I'd probably be for it.
On Mon, Dec 10, 2018 at 5:12 PM Nick Allen <ni...@nickallen.org> wrote:
> Another thing to note here is that committers have admin access to the
> Github account. This access is granted once you link your accounts using
> the URL that Roy sent. It took about an hour for mine to sync.
>
> This means we can do things like close abandoned pull requests ourselves.
> This also exposes the "merge pull request" button in Github. I am not
> quite sure how that might differ from our current 'prepare-commit' script.
> I would suggest we keep using the script until we figure that out.
>
>
>
>
> On Mon, Dec 10, 2018 at 3:29 PM Roy Lenferink <rl...@apache.org>
> wrote:
>
> > The repo has just moved to gitbox. Keep in mind the (ASF) remote has
> > changed. The GitHub remote remains the same.
> > I've opened a pull request to adapt the scripts to the gitbox URLs.
> >
> > In order to fully use the GitBox functionality, it is needed to link your
> > ASF and GitHub account which can be done here:
> > https://gitbox.apache.org/setup/
> >
> > When having any questions, don't hesitate to ask!
> >
> > - Roy
> >
> > Op ma 10 dec. 2018 om 20:11 schreef Roy Lenferink <rlenferink@apache.org
> >:
> >
> > > I have created the issue with INFRA to move over from git-wip-us to
> > > GitBox.
> > > METRON-1931 is created for updating the scripts with the new GitBox
> > > location. I'll start with this once the repositories are moved.
> > >
> > > - Roy
> > >
> > > Op ma 10 dec. 2018 om 15:52 schreef Nick Allen <ni...@nickallen.org>:
> > >
> > >> +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 <ot...@gmail.com>
> > >> wrote:
> > >>
> > >>> +1
> > >>>
> > >>> We will need jiras and PR’s for updating our scripts post move
> however.
> > >>>
> > >>
> >
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Nick Allen <ni...@nickallen.org>.
Another thing to note here is that committers have admin access to the
Github account. This access is granted once you link your accounts using
the URL that Roy sent. It took about an hour for mine to sync.
This means we can do things like close abandoned pull requests ourselves.
This also exposes the "merge pull request" button in Github. I am not
quite sure how that might differ from our current 'prepare-commit' script.
I would suggest we keep using the script until we figure that out.
On Mon, Dec 10, 2018 at 3:29 PM Roy Lenferink <rl...@apache.org> wrote:
> The repo has just moved to gitbox. Keep in mind the (ASF) remote has
> changed. The GitHub remote remains the same.
> I've opened a pull request to adapt the scripts to the gitbox URLs.
>
> In order to fully use the GitBox functionality, it is needed to link your
> ASF and GitHub account which can be done here:
> https://gitbox.apache.org/setup/
>
> When having any questions, don't hesitate to ask!
>
> - Roy
>
> Op ma 10 dec. 2018 om 20:11 schreef Roy Lenferink <rl...@apache.org>:
>
> > I have created the issue with INFRA to move over from git-wip-us to
> > GitBox.
> > METRON-1931 is created for updating the scripts with the new GitBox
> > location. I'll start with this once the repositories are moved.
> >
> > - Roy
> >
> > Op ma 10 dec. 2018 om 15:52 schreef Nick Allen <ni...@nickallen.org>:
> >
> >> +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 <ot...@gmail.com>
> >> wrote:
> >>
> >>> +1
> >>>
> >>> We will need jiras and PR’s for updating our scripts post move however.
> >>>
> >>
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
The repo has just moved to gitbox. Keep in mind the (ASF) remote has
changed. The GitHub remote remains the same.
I've opened a pull request to adapt the scripts to the gitbox URLs.
In order to fully use the GitBox functionality, it is needed to link your
ASF and GitHub account which can be done here:
https://gitbox.apache.org/setup/
When having any questions, don't hesitate to ask!
- Roy
Op ma 10 dec. 2018 om 20:11 schreef Roy Lenferink <rl...@apache.org>:
> I have created the issue with INFRA to move over from git-wip-us to
> GitBox.
> METRON-1931 is created for updating the scripts with the new GitBox
> location. I'll start with this once the repositories are moved.
>
> - Roy
>
> Op ma 10 dec. 2018 om 15:52 schreef Nick Allen <ni...@nickallen.org>:
>
>> +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 <ot...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> We will need jiras and PR’s for updating our scripts post move however.
>>>
>>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
I have created the issue with INFRA to move over from git-wip-us to GitBox.
METRON-1931 is created for updating the scripts with the new GitBox
location. I'll start with this once the repositories are moved.
- Roy
Op ma 10 dec. 2018 om 15:52 schreef Nick Allen <ni...@nickallen.org>:
> +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 <ot...@gmail.com>
> wrote:
>
>> +1
>>
>> We will need jiras and PR’s for updating our scripts post move however.
>>
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Nick Allen <ni...@nickallen.org>.
+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 <ot...@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 (rlenferink@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 <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Otto Fowler <ot...@gmail.com>.
+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 (rlenferink@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 <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
[DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Roy Lenferink <rl...@apache.org>.
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 <hu...@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: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Dave Fisher <da...@comcast.net>.
Git is open source. https://en.m.wikipedia.org/wiki/Git
GitHub was just acquired by Microsoft.
GitLab is an alternative to GitHub.
GitBox is a service from Apache Infrastructure to coordinate replication of GitHub with internal copies of everything in the Apache space. If GitHub were to go away then nothing is lost and a switch to something like GitLab is possible.
Sent from my iPhone
> On Dec 7, 2018, at 9:28 AM, JD <jd...@gmail.com> wrote:
>
> Except that GIT is now owned by MS!!!!
>
> I seriously DOUBT that MS will support a competitor to it's
> office software on their "OWNED" enterprise website.
Microsoft is not concerned about OpenOffice.
For example 50% of the VMs running on Azure are Linux.
>
> I think it would be a bad idea!!!
GitHub repositories will be very convenient for our support configurations - forum, MediaWiki, and updates service.
>
>
>
>> On 12/07/2018 10:08 AM, Mechtilde wrote:
>> Hello
>>
>> I know there is http://git.apache.org/openoffice.git/
>>
>> But I didn't know how it works or it should work.
I wonder what’s in there.
>>
>> I hope this is the time for our progejt to switch from svn to git as the
>> main repository.
>> We already discussed it several times in the past.
I’m not sure, that’s up to the active developers.
It could make sense for language translations.
Regards,
Dave
>>
>> Kind Regards
>>
>> Mechtilde
>> (Member of the PMC)
>>
>>> Am 07.12.18 um 17:52 schrieb Daniel Gruno:
>>> [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 :-).
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Peter Kovacs <Pe...@Apache.org>.
I think you confuse Github [1] and git [2]. The first is a company that
offers a service. Microsoft bought and can influence business decisions.
The other is a technology where participants disclaim their copyrights
(please note that on GPL licenses not all copyrights are disclaimed. The
exception is to change the license.)
I simplify of course to make a point.
All the Best
Peter
[1] github.com
[2] https://git-scm.com/
On 07.12.18 18:28, JD wrote:
> Except that GIT is now owned by MS!!!!
>
> I seriously DOUBT that MS will support a competitor to it's
> office software on their "OWNED" enterprise website.
>
> I think it would be a bad idea!!!
>
>
>
> On 12/07/2018 10:08 AM, Mechtilde wrote:
>> Hello
>>
>> I know there is http://git.apache.org/openoffice.git/
>>
>> But I didn't know how it works or it should work.
>>
>> I hope this is the time for our progejt to switch from svn to git as the
>> main repository.
>> We already discussed it several times in the past.
>>
>> Kind Regards
>>
>> Mechtilde
>> (Member of the PMC)
>>
>> Am 07.12.18 um 17:52 schrieb Daniel Gruno:
>>> [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 :-).
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by JD <jd...@gmail.com>.
Except that GIT is now owned by MS!!!!
I seriously DOUBT that MS will support a competitor to it's
office software on their "OWNED" enterprise website.
I think it would be a bad idea!!!
On 12/07/2018 10:08 AM, Mechtilde wrote:
> Hello
>
> I know there is http://git.apache.org/openoffice.git/
>
> But I didn't know how it works or it should work.
>
> I hope this is the time for our progejt to switch from svn to git as the
> main repository.
> We already discussed it several times in the past.
>
> Kind Regards
>
> Mechtilde
> (Member of the PMC)
>
> Am 07.12.18 um 17:52 schrieb Daniel Gruno:
>> [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 :-).
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Gavin McDonald <ip...@gmail.com>.
You can use Github directly or Gitbox directly, git.a.o would no longer be
involved. (And does not need to be)
On Fri, Dec 7, 2018 at 8:33 PM Mechtilde <oo...@mechtilde.de> wrote:
> Hello
>
> Am 07.12.18 um 20:59 schrieb Dave Fisher:
> > Hi -
>
> >
> > SVN -> git.apache.org -> GitBox -> GitHub.
> >
> > When we switch to GitHub development then it will be:
> >
> > GitHub -> GitBox -> git.apache.org
> >
>
> Is it possible to use git.apache.org directly?
>
> Kind regards
>
> --
> Mechtilde Stehmann
> ## Apache OpenOffice
> ## Freie Office Suite für Linux, MacOSX, Windows
> ## Debian Developer
> ## Loook, tbsync, libreoffice-canzeley-client
> ## PGP encryption welcome
> ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
>
>
--
Gav...
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Mechtilde <oo...@mechtilde.de>.
Hello
Am 07.12.18 um 20:59 schrieb Dave Fisher:
> Hi -
>
> SVN -> git.apache.org -> GitBox -> GitHub.
>
> When we switch to GitHub development then it will be:
>
> GitHub -> GitBox -> git.apache.org
>
Is it possible to use git.apache.org directly?
Kind regards
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, tbsync, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Fisher <da...@comcast.net>.
Hi -
> On Dec 7, 2018, at 11:36 AM, Mechtilde <oo...@mechtilde.de> wrote:
>
> Hello Dave
>
> Am 07.12.18 um 20:01 schrieb Dave Fisher:
>> Hi -
>>
>>> On Dec 7, 2018, at 9:08 AM, Mechtilde <oo...@mechtilde.de> wrote:
>>>
>>> Hello
>>>
>>> I know there is http://git.apache.org/openoffice.git/
>>
>> I “cloned” this to my machine.
>>
>> This looks like an update git mirror of svn.
>>
>> I see your latest commits:
>>
>> $ git log
>> commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, origin/HEAD)
>> Author: Mechtilde Stehmann <me...@apache.org>
>> Date: Fri Dec 7 18:30:38 2018 +0000
>>
>> merged actual translation from pootle with actual code base in trunk for ru
>>
>> git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 13f79535-47bb-0310-9956-ffa450edef68
>>
>> commit 23744e0c67a04df55971794b54a12afb90354627
>> Author: Mechtilde Stehmann <me...@apache.org>
>> Date: Fri Dec 7 18:27:01 2018 +0000
>>
>> merged actual translation from pootle with actual code base in trunk for ja
>>
>> git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 13f79535-47bb-0310-9956-ffa450edef68
>>
>> commit 6891308ea2b55199eb36583780f62e25d5ac40d4
>
> So this is the same as at Github?
Yes. That is apache copy.
SVN -> git.apache.org -> GitBox -> GitHub.
When we switch to GitHub development then it will be:
GitHub -> GitBox -> git.apache.org
Regards,
Dave
>>
>> Regards,
>> Dave
>>
>>>
>>> But I didn't know how it works or it should work.
>>>
>>> I hope this is the time for our progejt to switch from svn to git as the
>>> main repository.
>>> We already discussed it several times in the past.
>>>
>>> Kind Regards
>>>
> Kind regards
>
> --
> Mechtilde Stehmann
> ## Apache OpenOffice
> ## Freie Office Suite für Linux, MacOSX, Windows
> ## Debian Developer
> ## Loook, tbsync, libreoffice-canzeley-client
> ## PGP encryption welcome
> ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Mechtilde <oo...@mechtilde.de>.
Hello Dave
Am 07.12.18 um 20:01 schrieb Dave Fisher:
> Hi -
>
>> On Dec 7, 2018, at 9:08 AM, Mechtilde <oo...@mechtilde.de> wrote:
>>
>> Hello
>>
>> I know there is http://git.apache.org/openoffice.git/
>
> I “cloned” this to my machine.
>
> This looks like an update git mirror of svn.
>
> I see your latest commits:
>
> $ git log
> commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, origin/HEAD)
> Author: Mechtilde Stehmann <me...@apache.org>
> Date: Fri Dec 7 18:30:38 2018 +0000
>
> merged actual translation from pootle with actual code base in trunk for ru
>
> git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 13f79535-47bb-0310-9956-ffa450edef68
>
> commit 23744e0c67a04df55971794b54a12afb90354627
> Author: Mechtilde Stehmann <me...@apache.org>
> Date: Fri Dec 7 18:27:01 2018 +0000
>
> merged actual translation from pootle with actual code base in trunk for ja
>
> git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 13f79535-47bb-0310-9956-ffa450edef68
>
> commit 6891308ea2b55199eb36583780f62e25d5ac40d4
So this is the same as at Github?
>
> Regards,
> Dave
>
>>
>> But I didn't know how it works or it should work.
>>
>> I hope this is the time for our progejt to switch from svn to git as the
>> main repository.
>> We already discussed it several times in the past.
>>
>> Kind Regards
>>
Kind regards
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, tbsync, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Andrea Pescetti <pe...@apache.org>.
On 07/12/2018 Mechtilde wrote:
> Am 07.12.18 um 20:26 schrieb Dave Fisher:
>> Our openoffice.git mirror of svn is not on git-wip-us.apache.org.
OK. So this means that this entire thread (that was sent to all Apache
projects) does not apply to us in itself. Changes are coming only for
projects using git-wip-us.apache.org.
>> Before we switch from SVN to GitBox/GitHun for our main repository we will need to understand how to do the hooks to Bugzilla issues. I will use the setup of a Git repository for the Forum setup to figure that out.
> Do we have the hooks from SVN?
It's the Bugzilla bot mentioned in my latest message about MWiki VM
migration. It used to run on the old MWiki VM and it must still be
ported to the new MWiki VM (ideally tomorrow).
>> Meanwhile we can get a sense from the Dev teams when they would want to switch early next year.
This is an entirely separate issue. I mean, this discussion is about
infrastructural changes for projects using the server named
git-wip-us.apache.org (OpenOffice is not).
Deciding whether and how to use Git is independent of changes to that
specific server.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Mechtilde <oo...@mechtilde.de>.
Am 07.12.18 um 21:02 schrieb Dave Fisher:
>
>
>> On Dec 7, 2018, at 11:37 AM, Mechtilde <oo...@mechtilde.de> wrote:
>>
>> Hello
>>
>> Am 07.12.18 um 20:26 schrieb Dave Fisher:
>>> One more bit -
>>>
>>> Our openoffice.git mirror of svn is not on git-wip-us.apache.org.
>>>
>>> Before we switch from SVN to GitBox/GitHun for our main repository we will need to understand how to do the hooks to Bugzilla issues. I will use the setup of a Git repository for the Forum setup to figure that out.
>>
>> Do we have the hooks from SVN?
>
> I’m told by Infra that we will need to do research and perhaps write a Git replacement for the hooks we have between bugzilla and SVN,
>
> I would want to figure this out first. (Or we can take a decision to lose this capability temporarily)
we can first figure it out. thats ok for me.
Kind regards
>
> Warm Regards,
> Dave
>
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, tbsync, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Fisher <da...@comcast.net>.
> On Dec 7, 2018, at 11:37 AM, Mechtilde <oo...@mechtilde.de> wrote:
>
> Hello
>
> Am 07.12.18 um 20:26 schrieb Dave Fisher:
>> One more bit -
>>
>> Our openoffice.git mirror of svn is not on git-wip-us.apache.org.
>>
>> Before we switch from SVN to GitBox/GitHun for our main repository we will need to understand how to do the hooks to Bugzilla issues. I will use the setup of a Git repository for the Forum setup to figure that out.
>
> Do we have the hooks from SVN?
I’m told by Infra that we will need to do research and perhaps write a Git replacement for the hooks we have between bugzilla and SVN,
I would want to figure this out first. (Or we can take a decision to lose this capability temporarily)
Warm Regards,
Dave
>>
>> Meanwhile we can get a sense from the Dev teams when they would want to switch early next year.
>>
>> Regards,
>> Dave
>>
>
> Kind regards
>
> --
> Mechtilde Stehmann
> ## Apache OpenOffice
> ## Freie Office Suite für Linux, MacOSX, Windows
> ## Debian Developer
> ## Loook, tbsync, libreoffice-canzeley-client
> ## PGP encryption welcome
> ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Mechtilde <oo...@mechtilde.de>.
Hello
Am 07.12.18 um 20:26 schrieb Dave Fisher:
> One more bit -
>
> Our openoffice.git mirror of svn is not on git-wip-us.apache.org.
>
> Before we switch from SVN to GitBox/GitHun for our main repository we will need to understand how to do the hooks to Bugzilla issues. I will use the setup of a Git repository for the Forum setup to figure that out.
Do we have the hooks from SVN?
>
> Meanwhile we can get a sense from the Dev teams when they would want to switch early next year.
>
> Regards,
> Dave
>
Kind regards
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, tbsync, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Fisher <da...@comcast.net>.
One more bit -
Our openoffice.git mirror of svn is not on git-wip-us.apache.org.
Before we switch from SVN to GitBox/GitHun for our main repository we will need to understand how to do the hooks to Bugzilla issues. I will use the setup of a Git repository for the Forum setup to figure that out.
Meanwhile we can get a sense from the Dev teams when they would want to switch early next year.
Regards,
Dave
> On Dec 7, 2018, at 11:01 AM, Dave Fisher <da...@comcast.net> wrote:
>
> Hi -
>
>> On Dec 7, 2018, at 9:08 AM, Mechtilde <oo...@mechtilde.de> wrote:
>>
>> Hello
>>
>> I know there is http://git.apache.org/openoffice.git/
>
> I “cloned” this to my machine.
>
> This looks like an update git mirror of svn.
>
> I see your latest commits:
>
> $ git log
> commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, origin/HEAD)
> Author: Mechtilde Stehmann <me...@apache.org>
> Date: Fri Dec 7 18:30:38 2018 +0000
>
> merged actual translation from pootle with actual code base in trunk for ru
>
> git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 13f79535-47bb-0310-9956-ffa450edef68
>
> commit 23744e0c67a04df55971794b54a12afb90354627
> Author: Mechtilde Stehmann <me...@apache.org>
> Date: Fri Dec 7 18:27:01 2018 +0000
>
> merged actual translation from pootle with actual code base in trunk for ja
>
> git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 13f79535-47bb-0310-9956-ffa450edef68
>
> commit 6891308ea2b55199eb36583780f62e25d5ac40d4
>
> Regards,
> Dave
>
>>
>> But I didn't know how it works or it should work.
>>
>> I hope this is the time for our progejt to switch from svn to git as the
>> main repository.
>> We already discussed it several times in the past.
>>
>> Kind Regards
>>
>> Mechtilde
>> (Member of the PMC)
>>
>> Am 07.12.18 um 17:52 schrieb Daniel Gruno:
>>> [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 :-).
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> --
>> Mechtilde Stehmann
>> ## Apache OpenOffice
>> ## Freie Office Suite für Linux, MacOSX, Windows
>> ## Debian Developer
>> ## Loook, tbsync, libreoffice-canzeley-client
>> ## PGP encryption welcome
>> ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Fisher <da...@comcast.net>.
Hi -
> On Dec 7, 2018, at 9:08 AM, Mechtilde <oo...@mechtilde.de> wrote:
>
> Hello
>
> I know there is http://git.apache.org/openoffice.git/
I “cloned” this to my machine.
This looks like an update git mirror of svn.
I see your latest commits:
$ git log
commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, origin/HEAD)
Author: Mechtilde Stehmann <me...@apache.org>
Date: Fri Dec 7 18:30:38 2018 +0000
merged actual translation from pootle with actual code base in trunk for ru
git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 13f79535-47bb-0310-9956-ffa450edef68
commit 23744e0c67a04df55971794b54a12afb90354627
Author: Mechtilde Stehmann <me...@apache.org>
Date: Fri Dec 7 18:27:01 2018 +0000
merged actual translation from pootle with actual code base in trunk for ja
git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 13f79535-47bb-0310-9956-ffa450edef68
commit 6891308ea2b55199eb36583780f62e25d5ac40d4
Regards,
Dave
>
> But I didn't know how it works or it should work.
>
> I hope this is the time for our progejt to switch from svn to git as the
> main repository.
> We already discussed it several times in the past.
>
> Kind Regards
>
> Mechtilde
> (Member of the PMC)
>
> Am 07.12.18 um 17:52 schrieb Daniel Gruno:
>> [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 :-).
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> --
> Mechtilde Stehmann
> ## Apache OpenOffice
> ## Freie Office Suite für Linux, MacOSX, Windows
> ## Debian Developer
> ## Loook, tbsync, libreoffice-canzeley-client
> ## PGP encryption welcome
> ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Mechtilde <oo...@mechtilde.de>.
Hello
I know there is http://git.apache.org/openoffice.git/
But I didn't know how it works or it should work.
I hope this is the time for our progejt to switch from svn to git as the
main repository.
We already discussed it several times in the past.
Kind Regards
Mechtilde
(Member of the PMC)
Am 07.12.18 um 17:52 schrieb Daniel Gruno:
> [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 :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, tbsync, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Steve Viens <sv...@gmail.com>.
+1 from me too.
Steve
On Sun, Dec 9, 2018 at 5:58 PM Kurt Stam <ku...@gmail.com> wrote:
> +1 from me too
>
> Where will we move to? Github or gitbox.apache.org?
>
> On Dec 8, 2018, at 5:09 PM, Alex O'Ree <al...@apache.org> wrote:
>
> Juddi devs, I got this from infra yesterday and it does apply to both
> juddi and scout. It sounds like it will be a minimal impact besides
> updating some links on the website and poms.
> All those in favor of moving during the voluntary time period, vote +1
> otherwise state your intentions.
>
> +1 for the voluntary period for me.
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <hu...@apache.org>
> Date: Fri, Dec 7, 2018, 11:52 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> --
Steve Viens
sviens@gmail.com
603-828-2397
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Kurt Stam <ku...@gmail.com>.
+1 from me too
Where will we move to? Github or gitbox.apache.org <http://gitbox.apache.org/>?
> On Dec 8, 2018, at 5:09 PM, Alex O'Ree <al...@apache.org> wrote:
>
> Juddi devs, I got this from infra yesterday and it does apply to both juddi and scout. It sounds like it will be a minimal impact besides updating some links on the website and poms.
> All those in favor of moving during the voluntary time period, vote +1 otherwise state your intentions.
>
> +1 for the voluntary period for me.
>
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <humbedooh@apache.org <ma...@apache.org>>
> Date: Fri, Dec 7, 2018, 11:52 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org <http://git-wip-us.apache.org/>
> To: users@infra.apache.org <ma...@infra.apache.org> <users@infra.apache.org <ma...@infra.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 <http://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 <http://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 <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 <ma...@infra.apache.org>, not your
> project's dev list :-).
>
>
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Alex O'Ree <al...@apache.org>.
Juddi devs, I got this from infra yesterday and it does apply to both juddi
and scout. It sounds like it will be a minimal impact besides updating some
links on the website and poms.
All those in favor of moving during the voluntary time period, vote +1
otherwise state your intentions.
+1 for the voluntary period for me.
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: Fri, Dec 7, 2018, 11:52 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Brondsema <da...@brondsema.net>.
It's completed. If you have a checkout of the main repo you should update the
remote url from https://git-wip-us.apache.org/repos/asf/allura.git to
https://gitbox.apache.org/repos/asf/allura.git/ And similarly for
allura-site.git It looks like the old url redirects to the new one so that's nice.
On 1/17/19 3:47 PM, Dave Brondsema wrote:
> Ok I'm going to go ahead with a request to move the repo then.
>
> On 12/18/18 10:52 AM, Dave Brondsema wrote:
>> I think I'll request the move sometime in January (after holidays), if nobody
>> has any other preference. I'll post here when its going to change.
>>
>> On 12/11/18 11:46 AM, Dave Brondsema wrote:
>>> Does anyone have a preference on when we move our git repo? I think it will
>>> mostly just be a change in URL and we'll have to update our local checkouts
>>> "origin" url, and I can change the forge-allura.apache.org mirroring of it.
>>>
>>> It looks like the new system will also allow committers to set up integration
>>> with GitHub and do commits through GitHub since there is bi-directional sync
>>> between them. My preference would be to keep activity centered on our own
>>> self-hosted forge-allura.apache.org of course :)
>>>
>>> -Dave
>>>
>>> On 12/7/18 11:52 AM, 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 :-).
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Brondsema <da...@brondsema.net>.
Ok I'm going to go ahead with a request to move the repo then.
On 12/18/18 10:52 AM, Dave Brondsema wrote:
> I think I'll request the move sometime in January (after holidays), if nobody
> has any other preference. I'll post here when its going to change.
>
> On 12/11/18 11:46 AM, Dave Brondsema wrote:
>> Does anyone have a preference on when we move our git repo? I think it will
>> mostly just be a change in URL and we'll have to update our local checkouts
>> "origin" url, and I can change the forge-allura.apache.org mirroring of it.
>>
>> It looks like the new system will also allow committers to set up integration
>> with GitHub and do commits through GitHub since there is bi-directional sync
>> between them. My preference would be to keep activity centered on our own
>> self-hosted forge-allura.apache.org of course :)
>>
>> -Dave
>>
>> On 12/7/18 11:52 AM, 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 :-).
>>>
>>>
>>
>>
>>
>
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Brondsema <da...@brondsema.net>.
I think I'll request the move sometime in January (after holidays), if nobody
has any other preference. I'll post here when its going to change.
On 12/11/18 11:46 AM, Dave Brondsema wrote:
> Does anyone have a preference on when we move our git repo? I think it will
> mostly just be a change in URL and we'll have to update our local checkouts
> "origin" url, and I can change the forge-allura.apache.org mirroring of it.
>
> It looks like the new system will also allow committers to set up integration
> with GitHub and do commits through GitHub since there is bi-directional sync
> between them. My preference would be to keep activity centered on our own
> self-hosted forge-allura.apache.org of course :)
>
> -Dave
>
> On 12/7/18 11:52 AM, 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 :-).
>>
>>
>
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Dave Brondsema <da...@brondsema.net>.
Does anyone have a preference on when we move our git repo? I think it will
mostly just be a change in URL and we'll have to update our local checkouts
"origin" url, and I can change the forge-allura.apache.org mirroring of it.
It looks like the new system will also allow committers to set up integration
with GitHub and do commits through GitHub since there is bi-directional sync
between them. My preference would be to keep activity centered on our own
self-hosted forge-allura.apache.org of course :)
-Dave
On 12/7/18 11:52 AM, 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 :-).
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Volodymyr Vysotskyi <vo...@apache.org>.
After moving to the gitbox, a writable remote repository is
https://gitbox.apache.org/repos/asf/calcite.git instead of git-wip-us.
Kind regards,
Volodymyr Vysotskyi
On Wed, Dec 26, 2018 at 9:44 AM Julian Hyde <jh...@apache.org> wrote:
> Regarding the “site” branch. After a release, it should always point to
> the same as “master”. (It may diverge later, if there are changes made to
> the web site in master branch that we do not wish to immediately publish.)
> Sorry I forgot to push to site.
>
> Regarding gitbox. How should I set up my environment? I previously had
> origin as follows:
>
> $ git remote -v |grep origin
> origin https://git-wip-us.apache.org/repos/asf/calcite.git (fetch)
> origin https://git-wip-us.apache.org/repos/asf/calcite.git (push)
>
> Now I point it to GitHub, as follows:
>
> $ git remote set-url origin git@github.com:apache/calcite.git
>
> but I am not able to push.
>
> Julian
>
>
> > On Dec 25, 2018, at 7:56 PM, Andrei Sereda <an...@sereda.cc> wrote:
> >
> > Just in case.
> >
> > I made some changes to elastic adapter documentation (but didn't deploy
> > them) :
> > 1) c3e076c0
> > <
> https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564
> >
> >
> > 2) af739cbe
> > <
> https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a
> >
> >
> > My changes should be in both master and site branches.
> >
> > On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <francischuang@apache.org
> >
> > wrote:
> >
> >> When I deployed the changes to update the PMC Chair, I deployed the
> >> master branch. I checked out the site branch, but it appeared to be
> >> missing the site commits for Calcite 1.18 release and since I don't
> >> commit to Calcite often, I didn't want to cherry-pick the commits into
> >> the site branch and potentially break things.
> >>
> >> I think deploying the master branch should be safe for now, because 1.18
> >> was just released and there hasn't been any changes to the site for 1.19
> >> yet.
> >>
> >> On 26/12/2018 1:02 pm, Michael Mior wrote:
> >>> I've made commits to master to update the site but somehow my site
> branch
> >>> seems to be out of sync with what's deployed. If someone who has
> deployed
> >>> the site recently has a chance to check it out that would be great.
> >>>
> >>> --
> >>> Michael Mior
> >>> mmior@apache.org
> >>>
> >>>
> >>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com> a
> >>> écrit :
> >>>
> >>>> The migration is already done to my surprise. I'll try to update the
> >> site
> >>>> and send out an announcement to committers later today.
> >>>>
> >>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org
> >>>> wrote:
> >>>>
> >>>>> Thanks for sorting this out, Michael! Can't wait to try it!
> >>>>>
> >>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
> >>>>>> Since there have been no objections and the release is now complete,
> >>>>> I've
> >>>>>> requested the migration.
> >>>>>>
> >>>>>> https://issues.apache.org/jira/browse/INFRA-17498
> >>>>>>
> >>>>>> --
> >>>>>> Michael Mior
> >>>>>> mmior@apache.org
> >>>>>>
> >>>>>>
> >>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
> >>>>> écrit :
> >>>>>>> [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 :-).
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>
> >>
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Michael Mior <mm...@apache.org>.
Yup, that did the trick. Thanks!
--
Michael Mior
mmior@apache.org
Le ven. 28 déc. 2018 à 14:33, Julian Hyde <jh...@gmail.com> a écrit :
> The release news was disappearing because I’d forgotten to commit it to
> master. The problem should be fixed. When you regenerate the site using
> Jekyll, the only changes you should see will be your own.
>
> > On Dec 28, 2018, at 11:29 AM, Michael Mior <mm...@apache.org> wrote:
> >
> > Sorry for the silence on this.
> >
> > Julian, I'd like to deploy the site, but when I build, I see the latest
> > release announcement disappear. Given your reminder that site and master
> > should be the same after a release, I'll try to sort through what's going
> > on later today.
> >
> > On Thu, Dec 27, 2018, 16:04 Julian Hyde <jhyde@apache.org wrote:
> >
> >> Thanks, Francis.
> >>
> >> $ git remote set-url origin
> >> https://gitbox.apache.org/repos/asf/calcite.git <
> >> https://gitbox.apache.org/repos/asf/calcite.git>
> >>
> >> was sufficient to allow me to pull/fetch. And after I linked accounts
> >> using https://gitbox.apache.org/ <https://gitbox.apache.org/> I was
> able
> >> to also push.
> >>
> >> The “site” branch is now in sync with “master”, which is as it should
> be,
> >> right after a release.
> >>
> >> Michael, Did you know that your commit
> >>
> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239
> >> <
> >>
> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239
> >
> >> is in git but is not deployed to the site (via svn)? I’ll let you
> publish
> >> when you are ready.
> >>
> >> Julian
> >>
> >>
> >>> On Dec 25, 2018, at 11:46 PM, Francis Chuang <francischuang@apache.org
> >
> >> wrote:
> >>>
> >>> I haven't tried pushing directly to Github yet, but did you link your
> >> Github and Apache accounts here: https://gitbox.apache.org/ ?
> >>>
> >>>> On 26/12/2018 6:35 pm, Julian Hyde wrote:
> >>>> Regarding the “site” branch. After a release, it should always point
> to
> >> the same as “master”. (It may diverge later, if there are changes made
> to
> >> the web site in master branch that we do not wish to immediately
> publish.)
> >> Sorry I forgot to push to site.
> >>>>
> >>>> Regarding gitbox. How should I set up my environment? I previously had
> >> origin as follows:
> >>>>
> >>>> $ git remote -v |grep origin
> >>>> origin https://git-wip-us.apache.org/repos/asf/calcite.git
> >> (fetch)
> >>>> origin https://git-wip-us.apache.org/repos/asf/calcite.git
> (push)
> >>>>
> >>>> Now I point it to GitHub, as follows:
> >>>>
> >>>> $ git remote set-url origin git@github.com:apache/calcite.git
> >>>>
> >>>> but I am not able to push.
> >>>>
> >>>> Julian
> >>>>
> >>>>
> >>>>> On Dec 25, 2018, at 7:56 PM, Andrei Sereda <an...@sereda.cc> wrote:
> >>>>>
> >>>>> Just in case.
> >>>>>
> >>>>> I made some changes to elastic adapter documentation (but didn't
> deploy
> >>>>> them) :
> >>>>> 1) c3e076c0
> >>>>> <
> >>
> https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564
> >>>
> >>>>>
> >>>>> 2) af739cbe
> >>>>> <
> >>
> https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a
> >>>
> >>>>>
> >>>>> My changes should be in both master and site branches.
> >>>>>
> >>>>> On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <
> >> francischuang@apache.org>
> >>>>> wrote:
> >>>>>
> >>>>>> When I deployed the changes to update the PMC Chair, I deployed the
> >>>>>> master branch. I checked out the site branch, but it appeared to be
> >>>>>> missing the site commits for Calcite 1.18 release and since I don't
> >>>>>> commit to Calcite often, I didn't want to cherry-pick the commits
> into
> >>>>>> the site branch and potentially break things.
> >>>>>>
> >>>>>> I think deploying the master branch should be safe for now, because
> >> 1.18
> >>>>>> was just released and there hasn't been any changes to the site for
> >> 1.19
> >>>>>> yet.
> >>>>>>
> >>>>>>> On 26/12/2018 1:02 pm, Michael Mior wrote:
> >>>>>>> I've made commits to master to update the site but somehow my site
> >> branch
> >>>>>>> seems to be out of sync with what's deployed. If someone who has
> >> deployed
> >>>>>>> the site recently has a chance to check it out that would be great.
> >>>>>>>
> >>>>>>> --
> >>>>>>> Michael Mior
> >>>>>>> mmior@apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <michael.mior@gmail.com
> >
> >> a
> >>>>>>> écrit :
> >>>>>>>
> >>>>>>>> The migration is already done to my surprise. I'll try to update
> the
> >>>>>> site
> >>>>>>>> and send out an announcement to committers later today.
> >>>>>>>>
> >>>>>>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <
> >> francischuang@apache.org
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Thanks for sorting this out, Michael! Can't wait to try it!
> >>>>>>>>>
> >>>>>>>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
> >>>>>>>>>> Since there have been no objections and the release is now
> >> complete,
> >>>>>>>>> I've
> >>>>>>>>>> requested the migration.
> >>>>>>>>>>
> >>>>>>>>>> https://issues.apache.org/jira/browse/INFRA-17498
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Michael Mior
> >>>>>>>>>> mmior@apache.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <humbedooh@apache.org
> >
> >> a
> >>>>>>>>> écrit :
> >>>>>>>>>>> [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 :-).
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>
> >>
> >>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Julian Hyde <jh...@gmail.com>.
The release news was disappearing because I’d forgotten to commit it to master. The problem should be fixed. When you regenerate the site using Jekyll, the only changes you should see will be your own.
> On Dec 28, 2018, at 11:29 AM, Michael Mior <mm...@apache.org> wrote:
>
> Sorry for the silence on this.
>
> Julian, I'd like to deploy the site, but when I build, I see the latest
> release announcement disappear. Given your reminder that site and master
> should be the same after a release, I'll try to sort through what's going
> on later today.
>
> On Thu, Dec 27, 2018, 16:04 Julian Hyde <jhyde@apache.org wrote:
>
>> Thanks, Francis.
>>
>> $ git remote set-url origin
>> https://gitbox.apache.org/repos/asf/calcite.git <
>> https://gitbox.apache.org/repos/asf/calcite.git>
>>
>> was sufficient to allow me to pull/fetch. And after I linked accounts
>> using https://gitbox.apache.org/ <https://gitbox.apache.org/> I was able
>> to also push.
>>
>> The “site” branch is now in sync with “master”, which is as it should be,
>> right after a release.
>>
>> Michael, Did you know that your commit
>> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239
>> <
>> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239>
>> is in git but is not deployed to the site (via svn)? I’ll let you publish
>> when you are ready.
>>
>> Julian
>>
>>
>>> On Dec 25, 2018, at 11:46 PM, Francis Chuang <fr...@apache.org>
>> wrote:
>>>
>>> I haven't tried pushing directly to Github yet, but did you link your
>> Github and Apache accounts here: https://gitbox.apache.org/ ?
>>>
>>>> On 26/12/2018 6:35 pm, Julian Hyde wrote:
>>>> Regarding the “site” branch. After a release, it should always point to
>> the same as “master”. (It may diverge later, if there are changes made to
>> the web site in master branch that we do not wish to immediately publish.)
>> Sorry I forgot to push to site.
>>>>
>>>> Regarding gitbox. How should I set up my environment? I previously had
>> origin as follows:
>>>>
>>>> $ git remote -v |grep origin
>>>> origin https://git-wip-us.apache.org/repos/asf/calcite.git
>> (fetch)
>>>> origin https://git-wip-us.apache.org/repos/asf/calcite.git (push)
>>>>
>>>> Now I point it to GitHub, as follows:
>>>>
>>>> $ git remote set-url origin git@github.com:apache/calcite.git
>>>>
>>>> but I am not able to push.
>>>>
>>>> Julian
>>>>
>>>>
>>>>> On Dec 25, 2018, at 7:56 PM, Andrei Sereda <an...@sereda.cc> wrote:
>>>>>
>>>>> Just in case.
>>>>>
>>>>> I made some changes to elastic adapter documentation (but didn't deploy
>>>>> them) :
>>>>> 1) c3e076c0
>>>>> <
>> https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564
>>>
>>>>>
>>>>> 2) af739cbe
>>>>> <
>> https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a
>>>
>>>>>
>>>>> My changes should be in both master and site branches.
>>>>>
>>>>> On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <
>> francischuang@apache.org>
>>>>> wrote:
>>>>>
>>>>>> When I deployed the changes to update the PMC Chair, I deployed the
>>>>>> master branch. I checked out the site branch, but it appeared to be
>>>>>> missing the site commits for Calcite 1.18 release and since I don't
>>>>>> commit to Calcite often, I didn't want to cherry-pick the commits into
>>>>>> the site branch and potentially break things.
>>>>>>
>>>>>> I think deploying the master branch should be safe for now, because
>> 1.18
>>>>>> was just released and there hasn't been any changes to the site for
>> 1.19
>>>>>> yet.
>>>>>>
>>>>>>> On 26/12/2018 1:02 pm, Michael Mior wrote:
>>>>>>> I've made commits to master to update the site but somehow my site
>> branch
>>>>>>> seems to be out of sync with what's deployed. If someone who has
>> deployed
>>>>>>> the site recently has a chance to check it out that would be great.
>>>>>>>
>>>>>>> --
>>>>>>> Michael Mior
>>>>>>> mmior@apache.org
>>>>>>>
>>>>>>>
>>>>>>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com>
>> a
>>>>>>> écrit :
>>>>>>>
>>>>>>>> The migration is already done to my surprise. I'll try to update the
>>>>>> site
>>>>>>>> and send out an announcement to committers later today.
>>>>>>>>
>>>>>>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <
>> francischuang@apache.org
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks for sorting this out, Michael! Can't wait to try it!
>>>>>>>>>
>>>>>>>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
>>>>>>>>>> Since there have been no objections and the release is now
>> complete,
>>>>>>>>> I've
>>>>>>>>>> requested the migration.
>>>>>>>>>>
>>>>>>>>>> https://issues.apache.org/jira/browse/INFRA-17498
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Michael Mior
>>>>>>>>>> mmior@apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org>
>> a
>>>>>>>>> écrit :
>>>>>>>>>>> [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 :-).
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>
>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Michael Mior <mm...@apache.org>.
Sorry for the silence on this.
Julian, I'd like to deploy the site, but when I build, I see the latest
release announcement disappear. Given your reminder that site and master
should be the same after a release, I'll try to sort through what's going
on later today.
On Thu, Dec 27, 2018, 16:04 Julian Hyde <jhyde@apache.org wrote:
> Thanks, Francis.
>
> $ git remote set-url origin
> https://gitbox.apache.org/repos/asf/calcite.git <
> https://gitbox.apache.org/repos/asf/calcite.git>
>
> was sufficient to allow me to pull/fetch. And after I linked accounts
> using https://gitbox.apache.org/ <https://gitbox.apache.org/> I was able
> to also push.
>
> The “site” branch is now in sync with “master”, which is as it should be,
> right after a release.
>
> Michael, Did you know that your commit
> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239
> <
> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239>
> is in git but is not deployed to the site (via svn)? I’ll let you publish
> when you are ready.
>
> Julian
>
>
> > On Dec 25, 2018, at 11:46 PM, Francis Chuang <fr...@apache.org>
> wrote:
> >
> > I haven't tried pushing directly to Github yet, but did you link your
> Github and Apache accounts here: https://gitbox.apache.org/ ?
> >
> > On 26/12/2018 6:35 pm, Julian Hyde wrote:
> >> Regarding the “site” branch. After a release, it should always point to
> the same as “master”. (It may diverge later, if there are changes made to
> the web site in master branch that we do not wish to immediately publish.)
> Sorry I forgot to push to site.
> >>
> >> Regarding gitbox. How should I set up my environment? I previously had
> origin as follows:
> >>
> >> $ git remote -v |grep origin
> >> origin https://git-wip-us.apache.org/repos/asf/calcite.git
> (fetch)
> >> origin https://git-wip-us.apache.org/repos/asf/calcite.git (push)
> >>
> >> Now I point it to GitHub, as follows:
> >>
> >> $ git remote set-url origin git@github.com:apache/calcite.git
> >>
> >> but I am not able to push.
> >>
> >> Julian
> >>
> >>
> >>> On Dec 25, 2018, at 7:56 PM, Andrei Sereda <an...@sereda.cc> wrote:
> >>>
> >>> Just in case.
> >>>
> >>> I made some changes to elastic adapter documentation (but didn't deploy
> >>> them) :
> >>> 1) c3e076c0
> >>> <
> https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564
> >
> >>>
> >>> 2) af739cbe
> >>> <
> https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a
> >
> >>>
> >>> My changes should be in both master and site branches.
> >>>
> >>> On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <
> francischuang@apache.org>
> >>> wrote:
> >>>
> >>>> When I deployed the changes to update the PMC Chair, I deployed the
> >>>> master branch. I checked out the site branch, but it appeared to be
> >>>> missing the site commits for Calcite 1.18 release and since I don't
> >>>> commit to Calcite often, I didn't want to cherry-pick the commits into
> >>>> the site branch and potentially break things.
> >>>>
> >>>> I think deploying the master branch should be safe for now, because
> 1.18
> >>>> was just released and there hasn't been any changes to the site for
> 1.19
> >>>> yet.
> >>>>
> >>>> On 26/12/2018 1:02 pm, Michael Mior wrote:
> >>>>> I've made commits to master to update the site but somehow my site
> branch
> >>>>> seems to be out of sync with what's deployed. If someone who has
> deployed
> >>>>> the site recently has a chance to check it out that would be great.
> >>>>>
> >>>>> --
> >>>>> Michael Mior
> >>>>> mmior@apache.org
> >>>>>
> >>>>>
> >>>>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com>
> a
> >>>>> écrit :
> >>>>>
> >>>>>> The migration is already done to my surprise. I'll try to update the
> >>>> site
> >>>>>> and send out an announcement to committers later today.
> >>>>>>
> >>>>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <
> francischuang@apache.org
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Thanks for sorting this out, Michael! Can't wait to try it!
> >>>>>>>
> >>>>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
> >>>>>>>> Since there have been no objections and the release is now
> complete,
> >>>>>>> I've
> >>>>>>>> requested the migration.
> >>>>>>>>
> >>>>>>>> https://issues.apache.org/jira/browse/INFRA-17498
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Michael Mior
> >>>>>>>> mmior@apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org>
> a
> >>>>>>> écrit :
> >>>>>>>>> [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 :-).
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>
> >
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Julian Hyde <jh...@apache.org>.
Thanks, Francis.
$ git remote set-url origin https://gitbox.apache.org/repos/asf/calcite.git <https://gitbox.apache.org/repos/asf/calcite.git>
was sufficient to allow me to pull/fetch. And after I linked accounts using https://gitbox.apache.org/ <https://gitbox.apache.org/> I was able to also push.
The “site” branch is now in sync with “master”, which is as it should be, right after a release.
Michael, Did you know that your commit https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239 <https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239> is in git but is not deployed to the site (via svn)? I’ll let you publish when you are ready.
Julian
> On Dec 25, 2018, at 11:46 PM, Francis Chuang <fr...@apache.org> wrote:
>
> I haven't tried pushing directly to Github yet, but did you link your Github and Apache accounts here: https://gitbox.apache.org/ ?
>
> On 26/12/2018 6:35 pm, Julian Hyde wrote:
>> Regarding the “site” branch. After a release, it should always point to the same as “master”. (It may diverge later, if there are changes made to the web site in master branch that we do not wish to immediately publish.) Sorry I forgot to push to site.
>>
>> Regarding gitbox. How should I set up my environment? I previously had origin as follows:
>>
>> $ git remote -v |grep origin
>> origin https://git-wip-us.apache.org/repos/asf/calcite.git (fetch)
>> origin https://git-wip-us.apache.org/repos/asf/calcite.git (push)
>>
>> Now I point it to GitHub, as follows:
>>
>> $ git remote set-url origin git@github.com:apache/calcite.git
>>
>> but I am not able to push.
>>
>> Julian
>>
>>
>>> On Dec 25, 2018, at 7:56 PM, Andrei Sereda <an...@sereda.cc> wrote:
>>>
>>> Just in case.
>>>
>>> I made some changes to elastic adapter documentation (but didn't deploy
>>> them) :
>>> 1) c3e076c0
>>> <https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564>
>>>
>>> 2) af739cbe
>>> <https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a>
>>>
>>> My changes should be in both master and site branches.
>>>
>>> On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <fr...@apache.org>
>>> wrote:
>>>
>>>> When I deployed the changes to update the PMC Chair, I deployed the
>>>> master branch. I checked out the site branch, but it appeared to be
>>>> missing the site commits for Calcite 1.18 release and since I don't
>>>> commit to Calcite often, I didn't want to cherry-pick the commits into
>>>> the site branch and potentially break things.
>>>>
>>>> I think deploying the master branch should be safe for now, because 1.18
>>>> was just released and there hasn't been any changes to the site for 1.19
>>>> yet.
>>>>
>>>> On 26/12/2018 1:02 pm, Michael Mior wrote:
>>>>> I've made commits to master to update the site but somehow my site branch
>>>>> seems to be out of sync with what's deployed. If someone who has deployed
>>>>> the site recently has a chance to check it out that would be great.
>>>>>
>>>>> --
>>>>> Michael Mior
>>>>> mmior@apache.org
>>>>>
>>>>>
>>>>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com> a
>>>>> écrit :
>>>>>
>>>>>> The migration is already done to my surprise. I'll try to update the
>>>> site
>>>>>> and send out an announcement to committers later today.
>>>>>>
>>>>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks for sorting this out, Michael! Can't wait to try it!
>>>>>>>
>>>>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
>>>>>>>> Since there have been no objections and the release is now complete,
>>>>>>> I've
>>>>>>>> requested the migration.
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/browse/INFRA-17498
>>>>>>>>
>>>>>>>> --
>>>>>>>> Michael Mior
>>>>>>>> mmior@apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
>>>>>>> écrit :
>>>>>>>>> [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 :-).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Francis Chuang <fr...@apache.org>.
I haven't tried pushing directly to Github yet, but did you link your
Github and Apache accounts here: https://gitbox.apache.org/ ?
On 26/12/2018 6:35 pm, Julian Hyde wrote:
> Regarding the “site” branch. After a release, it should always point to the same as “master”. (It may diverge later, if there are changes made to the web site in master branch that we do not wish to immediately publish.) Sorry I forgot to push to site.
>
> Regarding gitbox. How should I set up my environment? I previously had origin as follows:
>
> $ git remote -v |grep origin
> origin https://git-wip-us.apache.org/repos/asf/calcite.git (fetch)
> origin https://git-wip-us.apache.org/repos/asf/calcite.git (push)
>
> Now I point it to GitHub, as follows:
>
> $ git remote set-url origin git@github.com:apache/calcite.git
>
> but I am not able to push.
>
> Julian
>
>
>> On Dec 25, 2018, at 7:56 PM, Andrei Sereda <an...@sereda.cc> wrote:
>>
>> Just in case.
>>
>> I made some changes to elastic adapter documentation (but didn't deploy
>> them) :
>> 1) c3e076c0
>> <https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564>
>>
>> 2) af739cbe
>> <https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a>
>>
>> My changes should be in both master and site branches.
>>
>> On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <fr...@apache.org>
>> wrote:
>>
>>> When I deployed the changes to update the PMC Chair, I deployed the
>>> master branch. I checked out the site branch, but it appeared to be
>>> missing the site commits for Calcite 1.18 release and since I don't
>>> commit to Calcite often, I didn't want to cherry-pick the commits into
>>> the site branch and potentially break things.
>>>
>>> I think deploying the master branch should be safe for now, because 1.18
>>> was just released and there hasn't been any changes to the site for 1.19
>>> yet.
>>>
>>> On 26/12/2018 1:02 pm, Michael Mior wrote:
>>>> I've made commits to master to update the site but somehow my site branch
>>>> seems to be out of sync with what's deployed. If someone who has deployed
>>>> the site recently has a chance to check it out that would be great.
>>>>
>>>> --
>>>> Michael Mior
>>>> mmior@apache.org
>>>>
>>>>
>>>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com> a
>>>> écrit :
>>>>
>>>>> The migration is already done to my surprise. I'll try to update the
>>> site
>>>>> and send out an announcement to committers later today.
>>>>>
>>>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org
>>>>> wrote:
>>>>>
>>>>>> Thanks for sorting this out, Michael! Can't wait to try it!
>>>>>>
>>>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
>>>>>>> Since there have been no objections and the release is now complete,
>>>>>> I've
>>>>>>> requested the migration.
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/INFRA-17498
>>>>>>>
>>>>>>> --
>>>>>>> Michael Mior
>>>>>>> mmior@apache.org
>>>>>>>
>>>>>>>
>>>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
>>>>>> écrit :
>>>>>>>> [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 :-).
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Julian Hyde <jh...@apache.org>.
Regarding the “site” branch. After a release, it should always point to the same as “master”. (It may diverge later, if there are changes made to the web site in master branch that we do not wish to immediately publish.) Sorry I forgot to push to site.
Regarding gitbox. How should I set up my environment? I previously had origin as follows:
$ git remote -v |grep origin
origin https://git-wip-us.apache.org/repos/asf/calcite.git (fetch)
origin https://git-wip-us.apache.org/repos/asf/calcite.git (push)
Now I point it to GitHub, as follows:
$ git remote set-url origin git@github.com:apache/calcite.git
but I am not able to push.
Julian
> On Dec 25, 2018, at 7:56 PM, Andrei Sereda <an...@sereda.cc> wrote:
>
> Just in case.
>
> I made some changes to elastic adapter documentation (but didn't deploy
> them) :
> 1) c3e076c0
> <https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564>
>
> 2) af739cbe
> <https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a>
>
> My changes should be in both master and site branches.
>
> On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <fr...@apache.org>
> wrote:
>
>> When I deployed the changes to update the PMC Chair, I deployed the
>> master branch. I checked out the site branch, but it appeared to be
>> missing the site commits for Calcite 1.18 release and since I don't
>> commit to Calcite often, I didn't want to cherry-pick the commits into
>> the site branch and potentially break things.
>>
>> I think deploying the master branch should be safe for now, because 1.18
>> was just released and there hasn't been any changes to the site for 1.19
>> yet.
>>
>> On 26/12/2018 1:02 pm, Michael Mior wrote:
>>> I've made commits to master to update the site but somehow my site branch
>>> seems to be out of sync with what's deployed. If someone who has deployed
>>> the site recently has a chance to check it out that would be great.
>>>
>>> --
>>> Michael Mior
>>> mmior@apache.org
>>>
>>>
>>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com> a
>>> écrit :
>>>
>>>> The migration is already done to my surprise. I'll try to update the
>> site
>>>> and send out an announcement to committers later today.
>>>>
>>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org
>>>> wrote:
>>>>
>>>>> Thanks for sorting this out, Michael! Can't wait to try it!
>>>>>
>>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
>>>>>> Since there have been no objections and the release is now complete,
>>>>> I've
>>>>>> requested the migration.
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/INFRA-17498
>>>>>>
>>>>>> --
>>>>>> Michael Mior
>>>>>> mmior@apache.org
>>>>>>
>>>>>>
>>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
>>>>> écrit :
>>>>>>> [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 :-).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Andrei Sereda <an...@sereda.cc>.
Just in case.
I made some changes to elastic adapter documentation (but didn't deploy
them) :
1) c3e076c0
<https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564>
2) af739cbe
<https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a>
My changes should be in both master and site branches.
On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <fr...@apache.org>
wrote:
> When I deployed the changes to update the PMC Chair, I deployed the
> master branch. I checked out the site branch, but it appeared to be
> missing the site commits for Calcite 1.18 release and since I don't
> commit to Calcite often, I didn't want to cherry-pick the commits into
> the site branch and potentially break things.
>
> I think deploying the master branch should be safe for now, because 1.18
> was just released and there hasn't been any changes to the site for 1.19
> yet.
>
> On 26/12/2018 1:02 pm, Michael Mior wrote:
> > I've made commits to master to update the site but somehow my site branch
> > seems to be out of sync with what's deployed. If someone who has deployed
> > the site recently has a chance to check it out that would be great.
> >
> > --
> > Michael Mior
> > mmior@apache.org
> >
> >
> > Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com> a
> > écrit :
> >
> >> The migration is already done to my surprise. I'll try to update the
> site
> >> and send out an announcement to committers later today.
> >>
> >> On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org
> >> wrote:
> >>
> >>> Thanks for sorting this out, Michael! Can't wait to try it!
> >>>
> >>> On 26/12/2018 2:13 am, Michael Mior wrote:
> >>>> Since there have been no objections and the release is now complete,
> >>> I've
> >>>> requested the migration.
> >>>>
> >>>> https://issues.apache.org/jira/browse/INFRA-17498
> >>>>
> >>>> --
> >>>> Michael Mior
> >>>> mmior@apache.org
> >>>>
> >>>>
> >>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
> >>> écrit :
> >>>>> [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 :-).
> >>>>>
> >>>>>
> >>>>>
> >>>
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Francis Chuang <fr...@apache.org>.
When I deployed the changes to update the PMC Chair, I deployed the
master branch. I checked out the site branch, but it appeared to be
missing the site commits for Calcite 1.18 release and since I don't
commit to Calcite often, I didn't want to cherry-pick the commits into
the site branch and potentially break things.
I think deploying the master branch should be safe for now, because 1.18
was just released and there hasn't been any changes to the site for 1.19
yet.
On 26/12/2018 1:02 pm, Michael Mior wrote:
> I've made commits to master to update the site but somehow my site branch
> seems to be out of sync with what's deployed. If someone who has deployed
> the site recently has a chance to check it out that would be great.
>
> --
> Michael Mior
> mmior@apache.org
>
>
> Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com> a
> écrit :
>
>> The migration is already done to my surprise. I'll try to update the site
>> and send out an announcement to committers later today.
>>
>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org
>> wrote:
>>
>>> Thanks for sorting this out, Michael! Can't wait to try it!
>>>
>>> On 26/12/2018 2:13 am, Michael Mior wrote:
>>>> Since there have been no objections and the release is now complete,
>>> I've
>>>> requested the migration.
>>>>
>>>> https://issues.apache.org/jira/browse/INFRA-17498
>>>>
>>>> --
>>>> Michael Mior
>>>> mmior@apache.org
>>>>
>>>>
>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
>>> écrit :
>>>>> [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 :-).
>>>>>
>>>>>
>>>>>
>>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Michael Mior <mm...@apache.org>.
I've made commits to master to update the site but somehow my site branch
seems to be out of sync with what's deployed. If someone who has deployed
the site recently has a chance to check it out that would be great.
--
Michael Mior
mmior@apache.org
Le mar. 25 déc. 2018 à 16:20, Michael Mior <mi...@gmail.com> a
écrit :
> The migration is already done to my surprise. I'll try to update the site
> and send out an announcement to committers later today.
>
> On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org
> wrote:
>
>> Thanks for sorting this out, Michael! Can't wait to try it!
>>
>> On 26/12/2018 2:13 am, Michael Mior wrote:
>> > Since there have been no objections and the release is now complete,
>> I've
>> > requested the migration.
>> >
>> > https://issues.apache.org/jira/browse/INFRA-17498
>> >
>> > --
>> > Michael Mior
>> > mmior@apache.org
>> >
>> >
>> > Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
>> écrit :
>> >
>> >> [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 :-).
>> >>
>> >>
>> >>
>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Michael Mior <mi...@gmail.com>.
The migration is already done to my surprise. I'll try to update the site
and send out an announcement to committers later today.
On Tue, Dec 25, 2018, 16:15 Francis Chuang <francischuang@apache.org wrote:
> Thanks for sorting this out, Michael! Can't wait to try it!
>
> On 26/12/2018 2:13 am, Michael Mior wrote:
> > Since there have been no objections and the release is now complete, I've
> > requested the migration.
> >
> > https://issues.apache.org/jira/browse/INFRA-17498
> >
> > --
> > Michael Mior
> > mmior@apache.org
> >
> >
> > Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a
> écrit :
> >
> >> [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 :-).
> >>
> >>
> >>
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Francis Chuang <fr...@apache.org>.
Thanks for sorting this out, Michael! Can't wait to try it!
On 26/12/2018 2:13 am, Michael Mior wrote:
> Since there have been no objections and the release is now complete, I've
> requested the migration.
>
> https://issues.apache.org/jira/browse/INFRA-17498
>
> --
> Michael Mior
> mmior@apache.org
>
>
> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a écrit :
>
>> [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 :-).
>>
>>
>>
Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Michael Mior <mm...@apache.org>.
Since there have been no objections and the release is now complete, I've
requested the migration.
https://issues.apache.org/jira/browse/INFRA-17498
--
Michael Mior
mmior@apache.org
Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <hu...@apache.org> a écrit :
> [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 :-).
>
>
>
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by "P. Ottlinger" <po...@apache.org>.
Hi guys,
thanks for all your work and efforts -
the new integration is *awesome* and will make it much much easier for
external contributions to flow into our repos.
@fellow devs: please follow the advice via gitbox.apache.org and enable
2-Factor-Authentication for your github account before checking out all
repos locally ;-)
*kudos*
/phil/
Am 07.12.18 um 17:52 schrieb Daniel Gruno:
> ## 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
Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Posted by Makoto Yui <my...@apache.org>.
FYI
---------- Forwarded message ---------
From: Daniel Gruno <hu...@apache.org>
Date: 2018年12月8日(土) 1:53
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: users@infra.apache.org <us...@infra.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 users@infra.apache.org, not your
project's dev list :-).
--
Makoto YUI <myui AT apache.org>
Principal Engineer, Arm Treasure Data.
http://myui.github.io/
RE: FW: [NOTICE] Mandatory relocation of Apache
gitrepositoriesongit-wip-us.apache.org
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
Looks we have an agreed consensus to move the repos. I’ll raise the INFRA issue and get it started.
Cheers,
Ian
Sent from Mail for Windows 10
From: Stuart Owen
Sent: 12 December 2018 15:15
To: dev@taverna.incubator.apache.org
Subject: Re: FW: [NOTICE] Mandatory relocation of Apache gitrepositoriesongit-wip-us.apache.org
+ 1 from me too, seems like a sensible move.
On 12/12/2018 15:03, Sagar wrote:
> +1, It will make things easier.
>
> On Wed, Dec 12, 2018 at 7:21 PM Ian Dunlop <ia...@gmail.com> wrote:
>
>> Hello,
>>
>> Thanks for that Andy. Lets go for +1s by 9 Jan 2019. I’ll give it mine.
>> Stian has already.
>>
>> +1
>>
>> Cheers,
>>
>> Ian
>>
>> Sent from Mail for Windows 10
>>
>> From: Andy Seaborne
>> Sent: 11 December 2018 15:18
>> To: dev@taverna.incubator.apache.org
>> Subject: Re: FW: [NOTICE] Mandatory relocation of Apache git
>> repositoriesongit-wip-us.apache.org
>>
>> On 10/12/2018 15:02, Ian Dunlop wrote:
>>> Hello,
>>>
>>> I guess this git move will affect Taverna. We need “Consensus in the
>> project (documented via the mailing list)” to go ahead. I don’t know what
>> constitutes consensus so I propose that we take silence as agreement. If
>> there are no objections to the repo moves documented below (with reasons)
>> before 9 Jan then we can raise the necessary INFRA tickets and get things
>> moved. Seems like it is going to happen anyway after Feb 7.
>>> Cheers,
>>>
>>> Ian
>> Here is an example:
>>
>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17389
>>
>> and the comment asks for a link to the dev@ to show consensus.
>> Seems that some +1's to show the PMC has seen it is enough.
>> Tricky to link to the absence of something.
>>
>> Andy
>>
>>
>>> Sent from Mail for Windows 10
>>>
>>> From: Daniel Gruno
>>> Sent: 07 December 2018 16:53
>>> To: users@infra.apache.org
>>> Subject: [NOTICE] Mandatory relocation of Apache git repositories
>> ongit-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 users@infra.apache.org, not your
>>> project's dev list :-).
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>>
>>>
>>
Re: FW: [NOTICE] Mandatory relocation of Apache git
repositoriesongit-wip-us.apache.org
Posted by Stuart Owen <st...@manchester.ac.uk>.
+ 1 from me too, seems like a sensible move.
On 12/12/2018 15:03, Sagar wrote:
> +1, It will make things easier.
>
> On Wed, Dec 12, 2018 at 7:21 PM Ian Dunlop <ia...@gmail.com> wrote:
>
>> Hello,
>>
>> Thanks for that Andy. Lets go for +1s by 9 Jan 2019. I’ll give it mine.
>> Stian has already.
>>
>> +1
>>
>> Cheers,
>>
>> Ian
>>
>> Sent from Mail for Windows 10
>>
>> From: Andy Seaborne
>> Sent: 11 December 2018 15:18
>> To: dev@taverna.incubator.apache.org
>> Subject: Re: FW: [NOTICE] Mandatory relocation of Apache git
>> repositoriesongit-wip-us.apache.org
>>
>> On 10/12/2018 15:02, Ian Dunlop wrote:
>>> Hello,
>>>
>>> I guess this git move will affect Taverna. We need “Consensus in the
>> project (documented via the mailing list)” to go ahead. I don’t know what
>> constitutes consensus so I propose that we take silence as agreement. If
>> there are no objections to the repo moves documented below (with reasons)
>> before 9 Jan then we can raise the necessary INFRA tickets and get things
>> moved. Seems like it is going to happen anyway after Feb 7.
>>> Cheers,
>>>
>>> Ian
>> Here is an example:
>>
>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17389
>>
>> and the comment asks for a link to the dev@ to show consensus.
>> Seems that some +1's to show the PMC has seen it is enough.
>> Tricky to link to the absence of something.
>>
>> Andy
>>
>>
>>> Sent from Mail for Windows 10
>>>
>>> From: Daniel Gruno
>>> Sent: 07 December 2018 16:53
>>> To: users@infra.apache.org
>>> Subject: [NOTICE] Mandatory relocation of Apache git repositories
>> ongit-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 users@infra.apache.org, not your
>>> project's dev list :-).
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>>
>>>
>>
Re: FW: [NOTICE] Mandatory relocation of Apache git repositoriesongit-wip-us.apache.org
Posted by Sagar <ku...@gmail.com>.
+1, It will make things easier.
On Wed, Dec 12, 2018 at 7:21 PM Ian Dunlop <ia...@gmail.com> wrote:
> Hello,
>
> Thanks for that Andy. Lets go for +1s by 9 Jan 2019. I’ll give it mine.
> Stian has already.
>
> +1
>
> Cheers,
>
> Ian
>
> Sent from Mail for Windows 10
>
> From: Andy Seaborne
> Sent: 11 December 2018 15:18
> To: dev@taverna.incubator.apache.org
> Subject: Re: FW: [NOTICE] Mandatory relocation of Apache git
> repositoriesongit-wip-us.apache.org
>
> On 10/12/2018 15:02, Ian Dunlop wrote:
> > Hello,
> >
> > I guess this git move will affect Taverna. We need “Consensus in the
> project (documented via the mailing list)” to go ahead. I don’t know what
> constitutes consensus so I propose that we take silence as agreement. If
> there are no objections to the repo moves documented below (with reasons)
> before 9 Jan then we can raise the necessary INFRA tickets and get things
> moved. Seems like it is going to happen anyway after Feb 7.
> >
> > Cheers,
> >
> > Ian
>
> Here is an example:
>
> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17389
>
> and the comment asks for a link to the dev@ to show consensus.
> Seems that some +1's to show the PMC has seen it is enough.
> Tricky to link to the absence of something.
>
> Andy
>
>
> >
> > Sent from Mail for Windows 10
> >
> > From: Daniel Gruno
> > Sent: 07 December 2018 16:53
> > To: users@infra.apache.org
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories
> ongit-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 users@infra.apache.org, not your
> > project's dev list :-).
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> >
> >
>
>
--
Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.
RE: FW: [NOTICE] Mandatory relocation of Apache git
repositoriesongit-wip-us.apache.org
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
Thanks for that Andy. Lets go for +1s by 9 Jan 2019. I’ll give it mine. Stian has already.
+1
Cheers,
Ian
Sent from Mail for Windows 10
From: Andy Seaborne
Sent: 11 December 2018 15:18
To: dev@taverna.incubator.apache.org
Subject: Re: FW: [NOTICE] Mandatory relocation of Apache git repositoriesongit-wip-us.apache.org
On 10/12/2018 15:02, Ian Dunlop wrote:
> Hello,
>
> I guess this git move will affect Taverna. We need “Consensus in the project (documented via the mailing list)” to go ahead. I don’t know what constitutes consensus so I propose that we take silence as agreement. If there are no objections to the repo moves documented below (with reasons) before 9 Jan then we can raise the necessary INFRA tickets and get things moved. Seems like it is going to happen anyway after Feb 7.
>
> Cheers,
>
> Ian
Here is an example:
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17389
and the comment asks for a link to the dev@ to show consensus.
Seems that some +1's to show the PMC has seen it is enough.
Tricky to link to the absence of something.
Andy
>
> Sent from Mail for Windows 10
>
> From: Daniel Gruno
> Sent: 07 December 2018 16:53
> To: users@infra.apache.org
> Subject: [NOTICE] Mandatory relocation of Apache git repositories ongit-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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
>
Re: FW: [NOTICE] Mandatory relocation of Apache git repositories
ongit-wip-us.apache.org
Posted by Andy Seaborne <an...@apache.org>.
On 10/12/2018 15:02, Ian Dunlop wrote:
> Hello,
>
> I guess this git move will affect Taverna. We need “Consensus in the project (documented via the mailing list)” to go ahead. I don’t know what constitutes consensus so I propose that we take silence as agreement. If there are no objections to the repo moves documented below (with reasons) before 9 Jan then we can raise the necessary INFRA tickets and get things moved. Seems like it is going to happen anyway after Feb 7.
>
> Cheers,
>
> Ian
Here is an example:
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17389
and the comment asks for a link to the dev@ to show consensus.
Seems that some +1's to show the PMC has seen it is enough.
Tricky to link to the absence of something.
Andy
>
> Sent from Mail for Windows 10
>
> From: Daniel Gruno
> Sent: 07 December 2018 16:53
> To: users@infra.apache.org
> Subject: [NOTICE] Mandatory relocation of Apache git repositories ongit-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 users@infra.apache.org, not your
> project's dev list :-).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
>
Re: FW: [NOTICE] Mandatory relocation of Apache git repositories ongit-wip-us.apache.org
Posted by Stian Soiland-Reyes <st...@apache.org>.
+1, move to github write access will make dealing with pull requests much
easier. Also we could still push to the gitbox server with Apache
credentials, so GitHub account is not required.
On Mon, 10 Dec 2018, 15:02 Ian Dunlop <ianwdunlop@gmail.com wrote:
> Hello,
>
>
>
> I guess this git move will affect Taverna. We need “Consensus in the
> project (documented via the mailing list)” to go ahead. I don’t know what
> constitutes consensus so I propose that we take silence as agreement. If
> there are no objections to the repo moves documented below (with reasons)
> before 9 Jan then we can raise the necessary INFRA tickets and get things
> moved. Seems like it is going to happen anyway after Feb 7.
>
>
>
> Cheers,
>
>
>
> Ian
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *Daniel Gruno <hu...@apache.org>
> *Sent: *07 December 2018 16:53
> *To: *users@infra.apache.org
> *Subject: *[NOTICE] Mandatory relocation of Apache git repositories
> ongit-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 users@infra.apache.org, not your
>
> project's dev list :-).
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>
> For additional commands, e-mail: dev-help@community.apache.org
>
>
>
>
>
FW: [NOTICE] Mandatory relocation of Apache git repositories
ongit-wip-us.apache.org
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
I guess this git move will affect Taverna. We need “Consensus in the project (documented via the mailing list)” to go ahead. I don’t know what constitutes consensus so I propose that we take silence as agreement. If there are no objections to the repo moves documented below (with reasons) before 9 Jan then we can raise the necessary INFRA tickets and get things moved. Seems like it is going to happen anyway after Feb 7.
Cheers,
Ian
Sent from Mail for Windows 10
From: Daniel Gruno
Sent: 07 December 2018 16:53
To: users@infra.apache.org
Subject: [NOTICE] Mandatory relocation of Apache git repositories ongit-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 users@infra.apache.org, not your
project's dev list :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
Posted by Aled Sage <al...@gmail.com>.
Hi Brooklyn community members,
We use https://git-wip-us.apache.org/repos/asf/brooklyn, so this impacts us.
We have the choice of waiting a month or two, or volunteering to move to
either gitbox.apache.org OR github [1] for our development and code pushes.
Being able to merge pull requests directly in github would be really
convenient! However, I've not looked into the details of each option.
Anyone have strong opinions?
Aled
[1] https://reference.apache.org/committer/github
On 07/12/2018 16:52, 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 :-).
>
>