[NOTICE] Mandatory migration of git repositories to gitbox.apache.org

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Apache Infrastructure Team
Hello, deltaspike folks.
As stated earlier in 2018, all git repositories must be migrated from
the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
is being decommissioned. Your project is receiving this email because
you still have repositories on git-wip-us that needs to be migrated.

The following repositories on git-wip-us belong to your project:
 - deltaspike.git


We are now entering the mandated (coordinated) move stage of the roadmap,
and you are asked to please coordinate migration with the Apache
Infrastructure Team before February 7th. All repositories not migrated
on February 7th will be mass migrated without warning, and we'd appreciate
it if we could work together to avoid a big mess that day :-).

Moving to gitbox means you will get full write access on GitHub as well,
and be able to close/merge pull requests and much more.

To have your repositories moved, please follow these steps:

- Ensure consensus on the move (a link to a lists.apache.org thread will
  suffice for us as evidence).
- Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA

Your migration should only take a few minutes. If you wish to migrate
at a specific time of day or date, please do let us know in the ticket.

As always, we appreciate your understanding and patience as we move
things around and work to provide better services and features for
the Apache Family.

Should you wish to contact us with feedback or questions, please do so
at: [hidden email].


With regards,
Apache Infrastructure

Reply | Threaded
Open this post in threaded view
|

[VOTE] Move our git repo to Apache gitbox

Mark Struberg-3
Hi folks!

I've made good experience with gitbox in other ASF projects.
I'd say we just call it 'deltaspike' as is. We just have one repo, so that would be a 1:1 migration.
As with everything GIT the sha1 doesn'T change anyway...

Can I pull the trigger?

Here is my +1

The VOTE is open for 72h

LieGrue,
strub

> Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <[hidden email]>:
>
> Hello, deltaspike folks.
> As stated earlier in 2018, all git repositories must be migrated from
> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> is being decommissioned. Your project is receiving this email because
> you still have repositories on git-wip-us that needs to be migrated.
>
> The following repositories on git-wip-us belong to your project:
> - deltaspike.git
>
>
> We are now entering the mandated (coordinated) move stage of the roadmap,
> and you are asked to please coordinate migration with the Apache
> Infrastructure Team before February 7th. All repositories not migrated
> on February 7th will be mass migrated without warning, and we'd appreciate
> it if we could work together to avoid a big mess that day :-).
>
> Moving to gitbox means you will get full write access on GitHub as well,
> and be able to close/merge pull requests and much more.
>
> To have your repositories moved, please follow these steps:
>
> - Ensure consensus on the move (a link to a lists.apache.org thread will
>  suffice for us as evidence).
> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
>
> Your migration should only take a few minutes. If you wish to migrate
> at a specific time of day or date, please do let us know in the ticket.
>
> As always, we appreciate your understanding and patience as we move
> things around and work to provide better services and features for
> the Apache Family.
>
> Should you wish to contact us with feedback or questions, please do so
> at: [hidden email].
>
>
> With regards,
> Apache Infrastructure
>

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Romain Manni-Bucau
+1

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le lun. 7 janv. 2019 à 18:08, Mark Struberg <[hidden email]> a
écrit :

> Hi folks!
>
> I've made good experience with gitbox in other ASF projects.
> I'd say we just call it 'deltaspike' as is. We just have one repo, so that
> would be a 1:1 migration.
> As with everything GIT the sha1 doesn'T change anyway...
>
> Can I pull the trigger?
>
> Here is my +1
>
> The VOTE is open for 72h
>
> LieGrue,
> strub
>
> > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> [hidden email]>:
> >
> > Hello, deltaspike folks.
> > As stated earlier in 2018, all git repositories must be migrated from
> > the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> > is being decommissioned. Your project is receiving this email because
> > you still have repositories on git-wip-us that needs to be migrated.
> >
> > The following repositories on git-wip-us belong to your project:
> > - deltaspike.git
> >
> >
> > We are now entering the mandated (coordinated) move stage of the roadmap,
> > and you are asked to please coordinate migration with the Apache
> > Infrastructure Team before February 7th. All repositories not migrated
> > on February 7th will be mass migrated without warning, and we'd
> appreciate
> > it if we could work together to avoid a big mess that day :-).
> >
> > Moving to gitbox means you will get full write access on GitHub as well,
> > and be able to close/merge pull requests and much more.
> >
> > To have your repositories moved, please follow these steps:
> >
> > - Ensure consensus on the move (a link to a lists.apache.org thread will
> >  suffice for us as evidence).
> > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> >
> > Your migration should only take a few minutes. If you wish to migrate
> > at a specific time of day or date, please do let us know in the ticket.
> >
> > As always, we appreciate your understanding and patience as we move
> > things around and work to provide better services and features for
> > the Apache Family.
> >
> > Should you wish to contact us with feedback or questions, please do so
> > at: [hidden email].
> >
> >
> > With regards,
> > Apache Infrastructure
> >
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Thomas Andraschko-2
+1

Am Mo., 7. Jan. 2019 um 18:09 Uhr schrieb Romain Manni-Bucau <
[hidden email]>:

> +1
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le lun. 7 janv. 2019 à 18:08, Mark Struberg <[hidden email]> a
> écrit :
>
> > Hi folks!
> >
> > I've made good experience with gitbox in other ASF projects.
> > I'd say we just call it 'deltaspike' as is. We just have one repo, so
> that
> > would be a 1:1 migration.
> > As with everything GIT the sha1 doesn'T change anyway...
> >
> > Can I pull the trigger?
> >
> > Here is my +1
> >
> > The VOTE is open for 72h
> >
> > LieGrue,
> > strub
> >
> > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > [hidden email]>:
> > >
> > > Hello, deltaspike folks.
> > > As stated earlier in 2018, all git repositories must be migrated from
> > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> > > is being decommissioned. Your project is receiving this email because
> > > you still have repositories on git-wip-us that needs to be migrated.
> > >
> > > The following repositories on git-wip-us belong to your project:
> > > - deltaspike.git
> > >
> > >
> > > We are now entering the mandated (coordinated) move stage of the
> roadmap,
> > > and you are asked to please coordinate migration with the Apache
> > > Infrastructure Team before February 7th. All repositories not migrated
> > > on February 7th will be mass migrated without warning, and we'd
> > appreciate
> > > it if we could work together to avoid a big mess that day :-).
> > >
> > > Moving to gitbox means you will get full write access on GitHub as
> well,
> > > and be able to close/merge pull requests and much more.
> > >
> > > To have your repositories moved, please follow these steps:
> > >
> > > - Ensure consensus on the move (a link to a lists.apache.org thread
> will
> > >  suffice for us as evidence).
> > > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> > >
> > > Your migration should only take a few minutes. If you wish to migrate
> > > at a specific time of day or date, please do let us know in the ticket.
> > >
> > > As always, we appreciate your understanding and patience as we move
> > > things around and work to provide better services and features for
> > > the Apache Family.
> > >
> > > Should you wish to contact us with feedback or questions, please do so
> > > at: [hidden email].
> > >
> > >
> > > With regards,
> > > Apache Infrastructure
> > >
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Christian Kaltepoth
+1

Am Mo., 7. Jan. 2019, 18:18 hat Thomas Andraschko <
[hidden email]> geschrieben:

> +1
>
> Am Mo., 7. Jan. 2019 um 18:09 Uhr schrieb Romain Manni-Bucau <
> [hidden email]>:
>
> > +1
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le lun. 7 janv. 2019 à 18:08, Mark Struberg <[hidden email]>
> a
> > écrit :
> >
> > > Hi folks!
> > >
> > > I've made good experience with gitbox in other ASF projects.
> > > I'd say we just call it 'deltaspike' as is. We just have one repo, so
> > that
> > > would be a 1:1 migration.
> > > As with everything GIT the sha1 doesn'T change anyway...
> > >
> > > Can I pull the trigger?
> > >
> > > Here is my +1
> > >
> > > The VOTE is open for 72h
> > >
> > > LieGrue,
> > > strub
> > >
> > > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > > [hidden email]>:
> > > >
> > > > Hello, deltaspike folks.
> > > > As stated earlier in 2018, all git repositories must be migrated from
> > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old
> service
> > > > is being decommissioned. Your project is receiving this email because
> > > > you still have repositories on git-wip-us that needs to be migrated.
> > > >
> > > > The following repositories on git-wip-us belong to your project:
> > > > - deltaspike.git
> > > >
> > > >
> > > > We are now entering the mandated (coordinated) move stage of the
> > roadmap,
> > > > and you are asked to please coordinate migration with the Apache
> > > > Infrastructure Team before February 7th. All repositories not
> migrated
> > > > on February 7th will be mass migrated without warning, and we'd
> > > appreciate
> > > > it if we could work together to avoid a big mess that day :-).
> > > >
> > > > Moving to gitbox means you will get full write access on GitHub as
> > well,
> > > > and be able to close/merge pull requests and much more.
> > > >
> > > > To have your repositories moved, please follow these steps:
> > > >
> > > > - Ensure consensus on the move (a link to a lists.apache.org thread
> > will
> > > >  suffice for us as evidence).
> > > > - Create a JIRA ticket at
> https://issues.apache.org/jira/browse/INFRA
> > > >
> > > > Your migration should only take a few minutes. If you wish to migrate
> > > > at a specific time of day or date, please do let us know in the
> ticket.
> > > >
> > > > As always, we appreciate your understanding and patience as we move
> > > > things around and work to provide better services and features for
> > > > the Apache Family.
> > > >
> > > > Should you wish to contact us with feedback or questions, please do
> so
> > > > at: [hidden email].
> > > >
> > > >
> > > > With regards,
> > > > Apache Infrastructure
> > > >
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Jason Porter
+1

On Mon, Jan 7, 2019 at 12:16 Christian Kaltepoth <[hidden email]>
wrote:

> +1
>
> Am Mo., 7. Jan. 2019, 18:18 hat Thomas Andraschko <
> [hidden email]> geschrieben:
>
> > +1
> >
> > Am Mo., 7. Jan. 2019 um 18:09 Uhr schrieb Romain Manni-Bucau <
> > [hidden email]>:
> >
> > > +1
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > <
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > >
> > >
> > > Le lun. 7 janv. 2019 à 18:08, Mark Struberg <[hidden email]
> >
> > a
> > > écrit :
> > >
> > > > Hi folks!
> > > >
> > > > I've made good experience with gitbox in other ASF projects.
> > > > I'd say we just call it 'deltaspike' as is. We just have one repo, so
> > > that
> > > > would be a 1:1 migration.
> > > > As with everything GIT the sha1 doesn'T change anyway...
> > > >
> > > > Can I pull the trigger?
> > > >
> > > > Here is my +1
> > > >
> > > > The VOTE is open for 72h
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > > > [hidden email]>:
> > > > >
> > > > > Hello, deltaspike folks.
> > > > > As stated earlier in 2018, all git repositories must be migrated
> from
> > > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old
> > service
> > > > > is being decommissioned. Your project is receiving this email
> because
> > > > > you still have repositories on git-wip-us that needs to be
> migrated.
> > > > >
> > > > > The following repositories on git-wip-us belong to your project:
> > > > > - deltaspike.git
> > > > >
> > > > >
> > > > > We are now entering the mandated (coordinated) move stage of the
> > > roadmap,
> > > > > and you are asked to please coordinate migration with the Apache
> > > > > Infrastructure Team before February 7th. All repositories not
> > migrated
> > > > > on February 7th will be mass migrated without warning, and we'd
> > > > appreciate
> > > > > it if we could work together to avoid a big mess that day :-).
> > > > >
> > > > > Moving to gitbox means you will get full write access on GitHub as
> > > well,
> > > > > and be able to close/merge pull requests and much more.
> > > > >
> > > > > To have your repositories moved, please follow these steps:
> > > > >
> > > > > - Ensure consensus on the move (a link to a lists.apache.org
> thread
> > > will
> > > > >  suffice for us as evidence).
> > > > > - Create a JIRA ticket at
> > https://issues.apache.org/jira/browse/INFRA
> > > > >
> > > > > Your migration should only take a few minutes. If you wish to
> migrate
> > > > > at a specific time of day or date, please do let us know in the
> > ticket.
> > > > >
> > > > > As always, we appreciate your understanding and patience as we move
> > > > > things around and work to provide better services and features for
> > > > > the Apache Family.
> > > > >
> > > > > Should you wish to contact us with feedback or questions, please do
> > so
> > > > > at: [hidden email].
> > > > >
> > > > >
> > > > > With regards,
> > > > > Apache Infrastructure
> > > > >
> > > >
> > > >
> > >
> >
>
--
Sent from Gmail Mobile
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Alexander Falb
+1

On Mon, Jan 7, 2019 at 8:23 PM Jason Porter <[hidden email]> wrote:

> +1
>
> On Mon, Jan 7, 2019 at 12:16 Christian Kaltepoth <[hidden email]>
> wrote:
>
> > +1
> >
> > Am Mo., 7. Jan. 2019, 18:18 hat Thomas Andraschko <
> > [hidden email]> geschrieben:
> >
> > > +1
> > >
> > > Am Mo., 7. Jan. 2019 um 18:09 Uhr schrieb Romain Manni-Bucau <
> > > [hidden email]>:
> > >
> > > > +1
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > > <http://rmannibucau.wordpress.com> | Github <
> > > > https://github.com/rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > > <
> > > >
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > > >
> > > >
> > > >
> > > > Le lun. 7 janv. 2019 à 18:08, Mark Struberg
> <[hidden email]
> > >
> > > a
> > > > écrit :
> > > >
> > > > > Hi folks!
> > > > >
> > > > > I've made good experience with gitbox in other ASF projects.
> > > > > I'd say we just call it 'deltaspike' as is. We just have one repo,
> so
> > > > that
> > > > > would be a 1:1 migration.
> > > > > As with everything GIT the sha1 doesn'T change anyway...
> > > > >
> > > > > Can I pull the trigger?
> > > > >
> > > > > Here is my +1
> > > > >
> > > > > The VOTE is open for 72h
> > > > >
> > > > > LieGrue,
> > > > > strub
> > > > >
> > > > > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > > > > [hidden email]>:
> > > > > >
> > > > > > Hello, deltaspike folks.
> > > > > > As stated earlier in 2018, all git repositories must be migrated
> > from
> > > > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old
> > > service
> > > > > > is being decommissioned. Your project is receiving this email
> > because
> > > > > > you still have repositories on git-wip-us that needs to be
> > migrated.
> > > > > >
> > > > > > The following repositories on git-wip-us belong to your project:
> > > > > > - deltaspike.git
> > > > > >
> > > > > >
> > > > > > We are now entering the mandated (coordinated) move stage of the
> > > > roadmap,
> > > > > > and you are asked to please coordinate migration with the Apache
> > > > > > Infrastructure Team before February 7th. All repositories not
> > > migrated
> > > > > > on February 7th will be mass migrated without warning, and we'd
> > > > > appreciate
> > > > > > it if we could work together to avoid a big mess that day :-).
> > > > > >
> > > > > > Moving to gitbox means you will get full write access on GitHub
> as
> > > > well,
> > > > > > and be able to close/merge pull requests and much more.
> > > > > >
> > > > > > To have your repositories moved, please follow these steps:
> > > > > >
> > > > > > - Ensure consensus on the move (a link to a lists.apache.org
> > thread
> > > > will
> > > > > >  suffice for us as evidence).
> > > > > > - Create a JIRA ticket at
> > > https://issues.apache.org/jira/browse/INFRA
> > > > > >
> > > > > > Your migration should only take a few minutes. If you wish to
> > migrate
> > > > > > at a specific time of day or date, please do let us know in the
> > > ticket.
> > > > > >
> > > > > > As always, we appreciate your understanding and patience as we
> move
> > > > > > things around and work to provide better services and features
> for
> > > > > > the Apache Family.
> > > > > >
> > > > > > Should you wish to contact us with feedback or questions, please
> do
> > > so
> > > > > > at: [hidden email].
> > > > > >
> > > > > >
> > > > > > With regards,
> > > > > > Apache Infrastructure
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> --
> Sent from Gmail Mobile
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Gerhard Petracek-2
In reply to this post by Mark Struberg-3
+1

regards,
gerhard



Am Mo., 7. Jan. 2019 um 18:08 Uhr schrieb Mark Struberg
<[hidden email]>:

> Hi folks!
>
> I've made good experience with gitbox in other ASF projects.
> I'd say we just call it 'deltaspike' as is. We just have one repo, so that
> would be a 1:1 migration.
> As with everything GIT the sha1 doesn'T change anyway...
>
> Can I pull the trigger?
>
> Here is my +1
>
> The VOTE is open for 72h
>
> LieGrue,
> strub
>
> > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> [hidden email]>:
> >
> > Hello, deltaspike folks.
> > As stated earlier in 2018, all git repositories must be migrated from
> > the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> > is being decommissioned. Your project is receiving this email because
> > you still have repositories on git-wip-us that needs to be migrated.
> >
> > The following repositories on git-wip-us belong to your project:
> > - deltaspike.git
> >
> >
> > We are now entering the mandated (coordinated) move stage of the roadmap,
> > and you are asked to please coordinate migration with the Apache
> > Infrastructure Team before February 7th. All repositories not migrated
> > on February 7th will be mass migrated without warning, and we'd
> appreciate
> > it if we could work together to avoid a big mess that day :-).
> >
> > Moving to gitbox means you will get full write access on GitHub as well,
> > and be able to close/merge pull requests and much more.
> >
> > To have your repositories moved, please follow these steps:
> >
> > - Ensure consensus on the move (a link to a lists.apache.org thread will
> >  suffice for us as evidence).
> > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> >
> > Your migration should only take a few minutes. If you wish to migrate
> > at a specific time of day or date, please do let us know in the ticket.
> >
> > As always, we appreciate your understanding and patience as we move
> > things around and work to provide better services and features for
> > the Apache Family.
> >
> > Should you wish to contact us with feedback or questions, please do so
> > at: [hidden email].
> >
> >
> > With regards,
> > Apache Infrastructure
> >
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Rudy De Busscher
+1

Rudy

On Mon, 7 Jan 2019 at 23:38, Gerhard Petracek <[hidden email]> wrote:

> +1
>
> regards,
> gerhard
>
>
>
> Am Mo., 7. Jan. 2019 um 18:08 Uhr schrieb Mark Struberg
> <[hidden email]>:
>
> > Hi folks!
> >
> > I've made good experience with gitbox in other ASF projects.
> > I'd say we just call it 'deltaspike' as is. We just have one repo, so
> that
> > would be a 1:1 migration.
> > As with everything GIT the sha1 doesn'T change anyway...
> >
> > Can I pull the trigger?
> >
> > Here is my +1
> >
> > The VOTE is open for 72h
> >
> > LieGrue,
> > strub
> >
> > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > [hidden email]>:
> > >
> > > Hello, deltaspike folks.
> > > As stated earlier in 2018, all git repositories must be migrated from
> > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> > > is being decommissioned. Your project is receiving this email because
> > > you still have repositories on git-wip-us that needs to be migrated.
> > >
> > > The following repositories on git-wip-us belong to your project:
> > > - deltaspike.git
> > >
> > >
> > > We are now entering the mandated (coordinated) move stage of the
> roadmap,
> > > and you are asked to please coordinate migration with the Apache
> > > Infrastructure Team before February 7th. All repositories not migrated
> > > on February 7th will be mass migrated without warning, and we'd
> > appreciate
> > > it if we could work together to avoid a big mess that day :-).
> > >
> > > Moving to gitbox means you will get full write access on GitHub as
> well,
> > > and be able to close/merge pull requests and much more.
> > >
> > > To have your repositories moved, please follow these steps:
> > >
> > > - Ensure consensus on the move (a link to a lists.apache.org thread
> will
> > >  suffice for us as evidence).
> > > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> > >
> > > Your migration should only take a few minutes. If you wish to migrate
> > > at a specific time of day or date, please do let us know in the ticket.
> > >
> > > As always, we appreciate your understanding and patience as we move
> > > things around and work to provide better services and features for
> > > the Apache Family.
> > >
> > > Should you wish to contact us with feedback or questions, please do so
> > > at: [hidden email].
> > >
> > >
> > > With regards,
> > > Apache Infrastructure
> > >
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Rafael Benevides
+1

On Tue, Jan 8, 2019 at 4:03 AM Rudy De Busscher <[hidden email]>
wrote:

> +1
>
> Rudy
>
> On Mon, 7 Jan 2019 at 23:38, Gerhard Petracek <[hidden email]>
> wrote:
>
> > +1
> >
> > regards,
> > gerhard
> >
> >
> >
> > Am Mo., 7. Jan. 2019 um 18:08 Uhr schrieb Mark Struberg
> > <[hidden email]>:
> >
> > > Hi folks!
> > >
> > > I've made good experience with gitbox in other ASF projects.
> > > I'd say we just call it 'deltaspike' as is. We just have one repo, so
> > that
> > > would be a 1:1 migration.
> > > As with everything GIT the sha1 doesn'T change anyway...
> > >
> > > Can I pull the trigger?
> > >
> > > Here is my +1
> > >
> > > The VOTE is open for 72h
> > >
> > > LieGrue,
> > > strub
> > >
> > > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > > [hidden email]>:
> > > >
> > > > Hello, deltaspike folks.
> > > > As stated earlier in 2018, all git repositories must be migrated from
> > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old
> service
> > > > is being decommissioned. Your project is receiving this email because
> > > > you still have repositories on git-wip-us that needs to be migrated.
> > > >
> > > > The following repositories on git-wip-us belong to your project:
> > > > - deltaspike.git
> > > >
> > > >
> > > > We are now entering the mandated (coordinated) move stage of the
> > roadmap,
> > > > and you are asked to please coordinate migration with the Apache
> > > > Infrastructure Team before February 7th. All repositories not
> migrated
> > > > on February 7th will be mass migrated without warning, and we'd
> > > appreciate
> > > > it if we could work together to avoid a big mess that day :-).
> > > >
> > > > Moving to gitbox means you will get full write access on GitHub as
> > well,
> > > > and be able to close/merge pull requests and much more.
> > > >
> > > > To have your repositories moved, please follow these steps:
> > > >
> > > > - Ensure consensus on the move (a link to a lists.apache.org thread
> > will
> > > >  suffice for us as evidence).
> > > > - Create a JIRA ticket at
> https://issues.apache.org/jira/browse/INFRA
> > > >
> > > > Your migration should only take a few minutes. If you wish to migrate
> > > > at a specific time of day or date, please do let us know in the
> ticket.
> > > >
> > > > As always, we appreciate your understanding and patience as we move
> > > > things around and work to provide better services and features for
> > > > the Apache Family.
> > > >
> > > > Should you wish to contact us with feedback or questions, please do
> so
> > > > at: [hidden email].
> > > >
> > > >
> > > > With regards,
> > > > Apache Infrastructure
> > > >
> > >
> > >
> >
>


--
*Rafael Benevides | Senior Product Manager*
Director of Developer Experience
Follow me at Twitter: @rafabene <https://twitter.com/rafabene>
M: +1-407-401-3555
Register today at https://developers.redhat.com/
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move our git repo to Apache gitbox

Daniel Cunha-2
+1

Em ter, 8 de jan de 2019 às 12:27, Rafael Benevides <[hidden email]>
escreveu:

> +1
>
> On Tue, Jan 8, 2019 at 4:03 AM Rudy De Busscher <[hidden email]>
> wrote:
>
> > +1
> >
> > Rudy
> >
> > On Mon, 7 Jan 2019 at 23:38, Gerhard Petracek <[hidden email]>
> > wrote:
> >
> > > +1
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > Am Mo., 7. Jan. 2019 um 18:08 Uhr schrieb Mark Struberg
> > > <[hidden email]>:
> > >
> > > > Hi folks!
> > > >
> > > > I've made good experience with gitbox in other ASF projects.
> > > > I'd say we just call it 'deltaspike' as is. We just have one repo, so
> > > that
> > > > would be a 1:1 migration.
> > > > As with everything GIT the sha1 doesn'T change anyway...
> > > >
> > > > Can I pull the trigger?
> > > >
> > > > Here is my +1
> > > >
> > > > The VOTE is open for 72h
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > > > [hidden email]>:
> > > > >
> > > > > Hello, deltaspike folks.
> > > > > As stated earlier in 2018, all git repositories must be migrated
> from
> > > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old
> > service
> > > > > is being decommissioned. Your project is receiving this email
> because
> > > > > you still have repositories on git-wip-us that needs to be
> migrated.
> > > > >
> > > > > The following repositories on git-wip-us belong to your project:
> > > > > - deltaspike.git
> > > > >
> > > > >
> > > > > We are now entering the mandated (coordinated) move stage of the
> > > roadmap,
> > > > > and you are asked to please coordinate migration with the Apache
> > > > > Infrastructure Team before February 7th. All repositories not
> > migrated
> > > > > on February 7th will be mass migrated without warning, and we'd
> > > > appreciate
> > > > > it if we could work together to avoid a big mess that day :-).
> > > > >
> > > > > Moving to gitbox means you will get full write access on GitHub as
> > > well,
> > > > > and be able to close/merge pull requests and much more.
> > > > >
> > > > > To have your repositories moved, please follow these steps:
> > > > >
> > > > > - Ensure consensus on the move (a link to a lists.apache.org
> thread
> > > will
> > > > >  suffice for us as evidence).
> > > > > - Create a JIRA ticket at
> > https://issues.apache.org/jira/browse/INFRA
> > > > >
> > > > > Your migration should only take a few minutes. If you wish to
> migrate
> > > > > at a specific time of day or date, please do let us know in the
> > ticket.
> > > > >
> > > > > As always, we appreciate your understanding and patience as we move
> > > > > things around and work to provide better services and features for
> > > > > the Apache Family.
> > > > >
> > > > > Should you wish to contact us with feedback or questions, please do
> > so
> > > > > at: [hidden email].
> > > > >
> > > > >
> > > > > With regards,
> > > > > Apache Infrastructure
> > > > >
> > > >
> > > >
> > >
> >
>
>
> --
> *Rafael Benevides | Senior Product Manager*
> Director of Developer Experience
> Follow me at Twitter: @rafabene <https://twitter.com/rafabene>
> M: +1-407-401-3555
> Register today at https://developers.redhat.com/
>


--
Daniel "soro" Cunha
https://twitter.com/dvlc_
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] [RESULT] Move our git repo to Apache gitbox

Mark Struberg-3
In reply to this post by Mark Struberg-3
Hi folks!

The VOTE did pass with

+1: Mark, Romain, Thomas, Christian, Jason, Alex, Gerhard, Rudy, Rafael, Daniel

No -1 nor 0

txs and LieGrue,
strub


> Am 07.01.2019 um 18:08 schrieb Mark Struberg <[hidden email]>:
>
> Hi folks!
>
> I've made good experience with gitbox in other ASF projects.
> I'd say we just call it 'deltaspike' as is. We just have one repo, so that would be a 1:1 migration.
> As with everything GIT the sha1 doesn'T change anyway...
>
> Can I pull the trigger?
>
> Here is my +1
>
> The VOTE is open for 72h
>
> LieGrue,
> strub
>
>> Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <[hidden email]>:
>>
>> Hello, deltaspike folks.
>> As stated earlier in 2018, all git repositories must be migrated from
>> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
>> is being decommissioned. Your project is receiving this email because
>> you still have repositories on git-wip-us that needs to be migrated.
>>
>> The following repositories on git-wip-us belong to your project:
>> - deltaspike.git
>>
>>
>> We are now entering the mandated (coordinated) move stage of the roadmap,
>> and you are asked to please coordinate migration with the Apache
>> Infrastructure Team before February 7th. All repositories not migrated
>> on February 7th will be mass migrated without warning, and we'd appreciate
>> it if we could work together to avoid a big mess that day :-).
>>
>> Moving to gitbox means you will get full write access on GitHub as well,
>> and be able to close/merge pull requests and much more.
>>
>> To have your repositories moved, please follow these steps:
>>
>> - Ensure consensus on the move (a link to a lists.apache.org thread will
>> suffice for us as evidence).
>> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
>>
>> Your migration should only take a few minutes. If you wish to migrate
>> at a specific time of day or date, please do let us know in the ticket.
>>
>> As always, we appreciate your understanding and patience as we move
>> things around and work to provide better services and features for
>> the Apache Family.
>>
>> Should you wish to contact us with feedback or questions, please do so
>> at: [hidden email].
>>
>>
>> With regards,
>> Apache Infrastructure
>>
>