[VOTE] Migrate existing Git repos to GitBox

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

[VOTE] Migrate existing Git repos to GitBox

Matt Sicker
This is a vote to migrate existing Git repositories from the old git-wip-us
infrastructure to the new gitbox infrastructure. New Apache projects are
not allowed to use git-wip-us and are instead directed to use gitbox. As
such, it makes sense for us to stay consistent with other projects.

The advantages to migrating to gitbox besides infra is much better GitHub
integration. The gist of how GitBox works is that git repos are mirrored
two-way between apache and github. The old git-wip-us github integration is
read-only which makes merging pull requests a chore and also makes the
github project pages a bit confusing as they aren't traditional github
projects as it is.

This vote only applies to existing git repositories at Commons. Existing
svn repositories will be covered in a different vote later on.

If you have a preference for Jira or GH Issues or something, please feel
free to add that to your vote. All existing projects are already in Jira as
it is.

References:
https://issues.apache.org/jira/browse/INFRA-16413
https://gitbox.apache.org/

--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Pascal Schumacher
+1

Am 22.04.2018 um 19:07 schrieb Matt Sicker:

> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it makes sense for us to stay consistent with other projects.
>
> The advantages to migrating to gitbox besides infra is much better GitHub
> integration. The gist of how GitBox works is that git repos are mirrored
> two-way between apache and github. The old git-wip-us github integration is
> read-only which makes merging pull requests a chore and also makes the
> github project pages a bit confusing as they aren't traditional github
> projects as it is.
>
> This vote only applies to existing git repositories at Commons. Existing
> svn repositories will be covered in a different vote later on.
>
> If you have a preference for Jira or GH Issues or something, please feel
> free to add that to your vote. All existing projects are already in Jira as
> it is.
>
> References:
> https://issues.apache.org/jira/browse/INFRA-16413
> https://gitbox.apache.org/
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Romain Manni-Bucau
+1

Le 22 avr. 2018 19:10, "Pascal Schumacher" <[hidden email]> a
écrit :

> +1
>
> Am 22.04.2018 um 19:07 schrieb Matt Sicker:
>
>> This is a vote to migrate existing Git repositories from the old
>> git-wip-us
>> infrastructure to the new gitbox infrastructure. New Apache projects are
>> not allowed to use git-wip-us and are instead directed to use gitbox. As
>> such, it makes sense for us to stay consistent with other projects.
>>
>> The advantages to migrating to gitbox besides infra is much better GitHub
>> integration. The gist of how GitBox works is that git repos are mirrored
>> two-way between apache and github. The old git-wip-us github integration
>> is
>> read-only which makes merging pull requests a chore and also makes the
>> github project pages a bit confusing as they aren't traditional github
>> projects as it is.
>>
>> This vote only applies to existing git repositories at Commons. Existing
>> svn repositories will be covered in a different vote later on.
>>
>> If you have a preference for Jira or GH Issues or something, please feel
>> free to add that to your vote. All existing projects are already in Jira
>> as
>> it is.
>>
>> References:
>> https://issues.apache.org/jira/browse/INFRA-16413
>> https://gitbox.apache.org/
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

garydgregory
In reply to this post by Matt Sicker
+1

Gary

On Sun, Apr 22, 2018, 11:07 Matt Sicker <[hidden email]> wrote:

> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it makes sense for us to stay consistent with other projects.
>
> The advantages to migrating to gitbox besides infra is much better GitHub
> integration. The gist of how GitBox works is that git repos are mirrored
> two-way between apache and github. The old git-wip-us github integration is
> read-only which makes merging pull requests a chore and also makes the
> github project pages a bit confusing as they aren't traditional github
> projects as it is.
>
> This vote only applies to existing git repositories at Commons. Existing
> svn repositories will be covered in a different vote later on.
>
> If you have a preference for Jira or GH Issues or something, please feel
> free to add that to your vote. All existing projects are already in Jira as
> it is.
>
> References:
> https://issues.apache.org/jira/browse/INFRA-16413
> https://gitbox.apache.org/
>
> --
> Matt Sicker <[hidden email]>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Rob Tompkins
+1

> On Apr 22, 2018, at 1:21 PM, Gary Gregory <[hidden email]> wrote:
>
> +1
>
> Gary
>
>> On Sun, Apr 22, 2018, 11:07 Matt Sicker <[hidden email]> wrote:
>>
>> This is a vote to migrate existing Git repositories from the old git-wip-us
>> infrastructure to the new gitbox infrastructure. New Apache projects are
>> not allowed to use git-wip-us and are instead directed to use gitbox. As
>> such, it makes sense for us to stay consistent with other projects.
>>
>> The advantages to migrating to gitbox besides infra is much better GitHub
>> integration. The gist of how GitBox works is that git repos are mirrored
>> two-way between apache and github. The old git-wip-us github integration is
>> read-only which makes merging pull requests a chore and also makes the
>> github project pages a bit confusing as they aren't traditional github
>> projects as it is.
>>
>> This vote only applies to existing git repositories at Commons. Existing
>> svn repositories will be covered in a different vote later on.
>>
>> If you have a preference for Jira or GH Issues or something, please feel
>> free to add that to your vote. All existing projects are already in Jira as
>> it is.
>>
>> References:
>> https://issues.apache.org/jira/browse/INFRA-16413
>> https://gitbox.apache.org/
>>
>> --
>> Matt Sicker <[hidden email]>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Oliver Heger-3
In reply to this post by Matt Sicker
+1

Oliver

Am 22.04.2018 um 19:07 schrieb Matt Sicker:

> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it makes sense for us to stay consistent with other projects.
>
> The advantages to migrating to gitbox besides infra is much better GitHub
> integration. The gist of how GitBox works is that git repos are mirrored
> two-way between apache and github. The old git-wip-us github integration is
> read-only which makes merging pull requests a chore and also makes the
> github project pages a bit confusing as they aren't traditional github
> projects as it is.
>
> This vote only applies to existing git repositories at Commons. Existing
> svn repositories will be covered in a different vote later on.
>
> If you have a preference for Jira or GH Issues or something, please feel
> free to add that to your vote. All existing projects are already in Jira as
> it is.
>
> References:
> https://issues.apache.org/jira/browse/INFRA-16413
> https://gitbox.apache.org/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Ralph Goers
In reply to this post by Matt Sicker
+1

Although I really would like to see documentation somewhere on how the process differs. For example, with GitBox can we now merge pull requests directly at GitHub? That would be a nice benefit.  Can we still commit to the ASF git repo or only at GitHub?

Ralph

> On Apr 22, 2018, at 10:07 AM, Matt Sicker <[hidden email]> wrote:
>
> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it makes sense for us to stay consistent with other projects.
>
> The advantages to migrating to gitbox besides infra is much better GitHub
> integration. The gist of how GitBox works is that git repos are mirrored
> two-way between apache and github. The old git-wip-us github integration is
> read-only which makes merging pull requests a chore and also makes the
> github project pages a bit confusing as they aren't traditional github
> projects as it is.
>
> This vote only applies to existing git repositories at Commons. Existing
> svn repositories will be covered in a different vote later on.
>
> If you have a preference for Jira or GH Issues or something, please feel
> free to add that to your vote. All existing projects are already in Jira as
> it is.
>
> References:
> https://issues.apache.org/jira/browse/INFRA-16413
> https://gitbox.apache.org/
>
> --
> Matt Sicker <[hidden email]>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Stefan Bodewig
In reply to this post by Matt Sicker
On 2018-04-22, Matt Sicker wrote:

> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it makes sense for us to stay consistent with other projects.

+1

> If you have a preference for Jira or GH Issues or something, please
> feel free to add that to your vote. All existing projects are already
> in Jira as it is.

I'd like to stick with JIRA for the projects that already have a
(longish?)  history of issues in JIRA as it makes searching for issues
easier.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Matt Sicker
In reply to this post by Ralph Goers
On 22 April 2018 at 13:34, Ralph Goers <[hidden email]> wrote:

> For example, with GitBox can we now merge pull requests directly at
> GitHub? That would be a nice benefit.  Can we still commit to the ASF git
> repo or only at GitHub?
>

From my understanding, you can merge PRs directly via the UI (or the "hub"
command line tool). As for where you push code, it seems to be driven from
either repository (apache or github), though that might be configurable to
avoid history conflicts.


--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Adam Soroka
I have asked INFRA about this (for another project) and they confirmed that GitBox runs the mirroring Github => Apache, so that PRs can be merged at Github. I did not ask about whether commits can also be pushed directly to Apache.

ajs6f

> On Apr 22, 2018, at 3:03 PM, Matt Sicker <[hidden email]> wrote:
>
> On 22 April 2018 at 13:34, Ralph Goers <[hidden email]> wrote:
>
>> For example, with GitBox can we now merge pull requests directly at
>> GitHub? That would be a nice benefit.  Can we still commit to the ASF git
>> repo or only at GitHub?
>>
>
> From my understanding, you can merge PRs directly via the UI (or the "hub"
> command line tool). As for where you push code, it seems to be driven from
> either repository (apache or github), though that might be configurable to
> avoid history conflicts.
>
>
> --
> Matt Sicker <[hidden email]>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Matt Sicker
An example project already using gitbox is whimsy:
https://github.com/apache/whimsy

On 22 April 2018 at 14:06, ajs6f <[hidden email]> wrote:

> I have asked INFRA about this (for another project) and they confirmed
> that GitBox runs the mirroring Github => Apache, so that PRs can be merged
> at Github. I did not ask about whether commits can also be pushed directly
> to Apache.
>
> ajs6f
>
> > On Apr 22, 2018, at 3:03 PM, Matt Sicker <[hidden email]> wrote:
> >
> > On 22 April 2018 at 13:34, Ralph Goers <[hidden email]>
> wrote:
> >
> >> For example, with GitBox can we now merge pull requests directly at
> >> GitHub? That would be a nice benefit.  Can we still commit to the ASF
> git
> >> repo or only at GitHub?
> >>
> >
> > From my understanding, you can merge PRs directly via the UI (or the
> "hub"
> > command line tool). As for where you push code, it seems to be driven
> from
> > either repository (apache or github), though that might be configurable
> to
> > avoid history conflicts.
> >
> >
> > --
> > Matt Sicker <[hidden email]>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Gilles Sadowski
On Sun, 22 Apr 2018 14:11:46 -0500, Matt Sicker wrote:
> An example project already using gitbox is whimsy:
> https://github.com/apache/whimsy

And "Commons Geometry":
   https://gitbox.apache.org/repos/asf?p=commons-geometry.git

Commits were pushed to that "remote".

Gilles

> On 22 April 2018 at 14:06, ajs6f <[hidden email]> wrote:
>
>> I have asked INFRA about this (for another project) and they
>> confirmed
>> that GitBox runs the mirroring Github => Apache, so that PRs can be
>> merged
>> at Github. I did not ask about whether commits can also be pushed
>> directly
>> to Apache.
>>
>> ajs6f
>>
>> > On Apr 22, 2018, at 3:03 PM, Matt Sicker <[hidden email]> wrote:
>> >
>> > On 22 April 2018 at 13:34, Ralph Goers
>> <[hidden email]>
>> wrote:
>> >
>> >> For example, with GitBox can we now merge pull requests directly
>> at
>> >> GitHub? That would be a nice benefit.  Can we still commit to the
>> ASF
>> git
>> >> repo or only at GitHub?
>> >>
>> >
>> > From my understanding, you can merge PRs directly via the UI (or
>> the
>> "hub"
>> > command line tool). As for where you push code, it seems to be
>> driven
>> from
>> > either repository (apache or github), though that might be
>> configurable
>> to
>> > avoid history conflicts.
>> >
>> >
>> > --
>> > Matt Sicker <[hidden email]>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Migrate existing Git repos to GitBox

Matt Sicker
This vote passes with 7 +1s and no -1s. I'll update infra that we're ready
to do this.

On 23 April 2018 at 02:37, Gilles <[hidden email]> wrote:

> On Sun, 22 Apr 2018 14:11:46 -0500, Matt Sicker wrote:
>
>> An example project already using gitbox is whimsy:
>> https://github.com/apache/whimsy
>>
>
> And "Commons Geometry":
>   https://gitbox.apache.org/repos/asf?p=commons-geometry.git
>
> Commits were pushed to that "remote".
>
> Gilles
>
>
> On 22 April 2018 at 14:06, ajs6f <[hidden email]> wrote:
>>
>> I have asked INFRA about this (for another project) and they confirmed
>>> that GitBox runs the mirroring Github => Apache, so that PRs can be
>>> merged
>>> at Github. I did not ask about whether commits can also be pushed
>>> directly
>>> to Apache.
>>>
>>> ajs6f
>>>
>>> > On Apr 22, 2018, at 3:03 PM, Matt Sicker <[hidden email]> wrote:
>>> >
>>> > On 22 April 2018 at 13:34, Ralph Goers <[hidden email]>
>>> wrote:
>>> >
>>> >> For example, with GitBox can we now merge pull requests directly at
>>> >> GitHub? That would be a nice benefit.  Can we still commit to the ASF
>>> git
>>> >> repo or only at GitHub?
>>> >>
>>> >
>>> > From my understanding, you can merge PRs directly via the UI (or the
>>> "hub"
>>> > command line tool). As for where you push code, it seems to be driven
>>> from
>>> > either repository (apache or github), though that might be configurable
>>> to
>>> > avoid history conflicts.
>>> >
>>> >
>>> > --
>>> > Matt Sicker <[hidden email]>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Matt Sicker <[hidden email]>