You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by Roy Lenferink <rl...@apache.org> on 2018/12/09 11:32:30 UTC
[DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.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: [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 :-).