You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myriad.apache.org by JP Gilaberte <jp...@apache.org> on 2018/09/13 14:26:18 UTC
[Proposal] Migrate to gitbox
Hi all,
I am starting this vote (copy from Ambary folks) to migrate Myriad
project from git-wip
repository to gitbox, which allows a deeper integration with github
features. Moving to gitbox will allow committers to merge, close or edit
pull requests in the github UI.
Other advantages:
- JIRA linking can be enabled on request to the Apache Infra team, which
will automatically link a PR with its corresponding JIRA in
https://issues.apache.org/jira
- It will make our code review process cleaner and more efficient when
compared to the Review Board.
- Opens up a lot of opportunities on leveraging the rich set of github
APIs and web hooks to develop tools that can help monitor the open PRs,
trigger a jenkins job to run unit tests, etc..
[ ] +1, Migrate Myriad repository to gitbox
[ ] -1, Keep git-wip + github read-only mirror
Regards,
JP Gilaberte
Re: [Proposal] Migrate to gitbox
Posted by Javi Roman <jr...@gmail.com>.
The gitbox for Myriad is successfully enabled:
https://gitbox.apache.org/repos/asf?p=incubator-myriad.git;a=summary
For committers you will be able of using github mirror (read/write
mode) if you have enabled the Two-factor Authentication [1].
For checking the linking of your github account and GitBox you have to
access to [2].
Happy hacking!
[1] https://blog.github.com/2013-09-03-two-factor-authentication/
[2] https://gitbox.apache.org/setup/
--
Javi Roman
Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman
On Wed, Dec 12, 2018 at 9:13 AM Javi Roman <jr...@gmail.com> wrote:
>
> I'm going to create INFRA ticket for migrating to GitBox.
>
> This vote passed with four +1's.
>
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> Apache Id: javiroman
> On Fri, Sep 14, 2018 at 5:59 PM yuliya Feldman
> <yu...@yahoo.com.invalid> wrote:
> >
> > Thank you Javi for the information.
> > +1 from me.
> > On Thursday, September 13, 2018, 10:45:04 PM PDT, Javi Roman <jr...@gmail.com> wrote:
> >
> > Yuliya closing PRs is only possible by the owner of the PR or by means
> > a commit by other author. When a PR is abandoned by the author (we
> > have some of them) the procedure is open a JIRA ticket to INFRA for
> > closing them. With GitBox we can use GitHub interface for this kind of
> > tasks among others in guess.
> >
> > IMHO changing to GitBox is an enhance in our workflow, even our
> > "father" project Apache Mesos migrated to GitBox some days ago.
> >
> > We can wait a few days a give a result vote for this change, we have 3
> > +1 votes, and one -1 (your vote I understand) by now.
> >
> > Greetings.
> > --
> > Javi Roman
> >
> > Twitter: @javiromanrh
> > GitHub: github.com/javiroman
> > Linkedin: es.linkedin.com/in/javiroman
> > Big Data Blog: dataintensive.info
> > Apache Id: javiroman
> >
> > On Thu, Sep 13, 2018 at 7:30 PM yuliya Feldman
> > <yu...@yahoo.com.invalid> wrote:
> > >
> > > Hello there,
> > > I am trying to figure out what are the real advantages for Myriad in moving it to gitbox
> > > - JIRA linking can be enabled on request to the Apache Infra team, which
> > > will automatically link a PR with its corresponding JIRA in
> > > I believe it is already there
> > > - It will make our code review process cleaner and more efficient when
> > > compared to the Review Board.
> > > I believe we are using github itself for review.
> > > - Opens up a lot of opportunities on leveraging the rich set of github
> > > APIs and web hooks to develop tools that can help monitor the open PRs,
> > > trigger a jenkins job to run unit tests, etc..
> > > Which ones?
> > > Thanks,Yuliya
> > > On Thursday, September 13, 2018, 7:26:35 AM PDT, JP Gilaberte <jp...@apache.org> wrote:
> > >
> > > Hi all,
> > >
> > > I am starting this vote (copy from Ambary folks) to migrate Myriad
> > > project from git-wip
> > > repository to gitbox, which allows a deeper integration with github
> > > features. Moving to gitbox will allow committers to merge, close or edit
> > > pull requests in the github UI.
> > >
> > > Other advantages:
> > >
> > > - JIRA linking can be enabled on request to the Apache Infra team, which
> > > will automatically link a PR with its corresponding JIRA in
> > > https://issues.apache.org/jira
> > > - It will make our code review process cleaner and more efficient when
> > > compared to the Review Board.
> > > - Opens up a lot of opportunities on leveraging the rich set of github
> > > APIs and web hooks to develop tools that can help monitor the open PRs,
> > > trigger a jenkins job to run unit tests, etc..
> > >
> > > [ ] +1, Migrate Myriad repository to gitbox
> > > [ ] -1, Keep git-wip + github read-only mirror
> > >
> > > Regards,
> > > JP Gilaberte
> > >
> >
Re: [Proposal] Migrate to gitbox
Posted by Javi Roman <jr...@gmail.com>.
I'm going to create INFRA ticket for migrating to GitBox.
This vote passed with four +1's.
--
Javi Roman
Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman
On Fri, Sep 14, 2018 at 5:59 PM yuliya Feldman
<yu...@yahoo.com.invalid> wrote:
>
> Thank you Javi for the information.
> +1 from me.
> On Thursday, September 13, 2018, 10:45:04 PM PDT, Javi Roman <jr...@gmail.com> wrote:
>
> Yuliya closing PRs is only possible by the owner of the PR or by means
> a commit by other author. When a PR is abandoned by the author (we
> have some of them) the procedure is open a JIRA ticket to INFRA for
> closing them. With GitBox we can use GitHub interface for this kind of
> tasks among others in guess.
>
> IMHO changing to GitBox is an enhance in our workflow, even our
> "father" project Apache Mesos migrated to GitBox some days ago.
>
> We can wait a few days a give a result vote for this change, we have 3
> +1 votes, and one -1 (your vote I understand) by now.
>
> Greetings.
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> Apache Id: javiroman
>
> On Thu, Sep 13, 2018 at 7:30 PM yuliya Feldman
> <yu...@yahoo.com.invalid> wrote:
> >
> > Hello there,
> > I am trying to figure out what are the real advantages for Myriad in moving it to gitbox
> > - JIRA linking can be enabled on request to the Apache Infra team, which
> > will automatically link a PR with its corresponding JIRA in
> > I believe it is already there
> > - It will make our code review process cleaner and more efficient when
> > compared to the Review Board.
> > I believe we are using github itself for review.
> > - Opens up a lot of opportunities on leveraging the rich set of github
> > APIs and web hooks to develop tools that can help monitor the open PRs,
> > trigger a jenkins job to run unit tests, etc..
> > Which ones?
> > Thanks,Yuliya
> > On Thursday, September 13, 2018, 7:26:35 AM PDT, JP Gilaberte <jp...@apache.org> wrote:
> >
> > Hi all,
> >
> > I am starting this vote (copy from Ambary folks) to migrate Myriad
> > project from git-wip
> > repository to gitbox, which allows a deeper integration with github
> > features. Moving to gitbox will allow committers to merge, close or edit
> > pull requests in the github UI.
> >
> > Other advantages:
> >
> > - JIRA linking can be enabled on request to the Apache Infra team, which
> > will automatically link a PR with its corresponding JIRA in
> > https://issues.apache.org/jira
> > - It will make our code review process cleaner and more efficient when
> > compared to the Review Board.
> > - Opens up a lot of opportunities on leveraging the rich set of github
> > APIs and web hooks to develop tools that can help monitor the open PRs,
> > trigger a jenkins job to run unit tests, etc..
> >
> > [ ] +1, Migrate Myriad repository to gitbox
> > [ ] -1, Keep git-wip + github read-only mirror
> >
> > Regards,
> > JP Gilaberte
> >
>
Re: [Proposal] Migrate to gitbox
Posted by yuliya Feldman <yu...@yahoo.com.INVALID>.
Thank you Javi for the information.
+1 from me.
On Thursday, September 13, 2018, 10:45:04 PM PDT, Javi Roman <jr...@gmail.com> wrote:
Yuliya closing PRs is only possible by the owner of the PR or by means
a commit by other author. When a PR is abandoned by the author (we
have some of them) the procedure is open a JIRA ticket to INFRA for
closing them. With GitBox we can use GitHub interface for this kind of
tasks among others in guess.
IMHO changing to GitBox is an enhance in our workflow, even our
"father" project Apache Mesos migrated to GitBox some days ago.
We can wait a few days a give a result vote for this change, we have 3
+1 votes, and one -1 (your vote I understand) by now.
Greetings.
--
Javi Roman
Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman
On Thu, Sep 13, 2018 at 7:30 PM yuliya Feldman
<yu...@yahoo.com.invalid> wrote:
>
> Hello there,
> I am trying to figure out what are the real advantages for Myriad in moving it to gitbox
> - JIRA linking can be enabled on request to the Apache Infra team, which
> will automatically link a PR with its corresponding JIRA in
> I believe it is already there
> - It will make our code review process cleaner and more efficient when
> compared to the Review Board.
> I believe we are using github itself for review.
> - Opens up a lot of opportunities on leveraging the rich set of github
> APIs and web hooks to develop tools that can help monitor the open PRs,
> trigger a jenkins job to run unit tests, etc..
> Which ones?
> Thanks,Yuliya
> On Thursday, September 13, 2018, 7:26:35 AM PDT, JP Gilaberte <jp...@apache.org> wrote:
>
> Hi all,
>
> I am starting this vote (copy from Ambary folks) to migrate Myriad
> project from git-wip
> repository to gitbox, which allows a deeper integration with github
> features. Moving to gitbox will allow committers to merge, close or edit
> pull requests in the github UI.
>
> Other advantages:
>
> - JIRA linking can be enabled on request to the Apache Infra team, which
> will automatically link a PR with its corresponding JIRA in
> https://issues.apache.org/jira
> - It will make our code review process cleaner and more efficient when
> compared to the Review Board.
> - Opens up a lot of opportunities on leveraging the rich set of github
> APIs and web hooks to develop tools that can help monitor the open PRs,
> trigger a jenkins job to run unit tests, etc..
>
> [ ] +1, Migrate Myriad repository to gitbox
> [ ] -1, Keep git-wip + github read-only mirror
>
> Regards,
> JP Gilaberte
>
Re: [Proposal] Migrate to gitbox
Posted by Javi Roman <jr...@gmail.com>.
Yuliya closing PRs is only possible by the owner of the PR or by means
a commit by other author. When a PR is abandoned by the author (we
have some of them) the procedure is open a JIRA ticket to INFRA for
closing them. With GitBox we can use GitHub interface for this kind of
tasks among others in guess.
IMHO changing to GitBox is an enhance in our workflow, even our
"father" project Apache Mesos migrated to GitBox some days ago.
We can wait a few days a give a result vote for this change, we have 3
+1 votes, and one -1 (your vote I understand) by now.
Greetings.
--
Javi Roman
Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman
On Thu, Sep 13, 2018 at 7:30 PM yuliya Feldman
<yu...@yahoo.com.invalid> wrote:
>
> Hello there,
> I am trying to figure out what are the real advantages for Myriad in moving it to gitbox
> - JIRA linking can be enabled on request to the Apache Infra team, which
> will automatically link a PR with its corresponding JIRA in
> I believe it is already there
> - It will make our code review process cleaner and more efficient when
> compared to the Review Board.
> I believe we are using github itself for review.
> - Opens up a lot of opportunities on leveraging the rich set of github
> APIs and web hooks to develop tools that can help monitor the open PRs,
> trigger a jenkins job to run unit tests, etc..
> Which ones?
> Thanks,Yuliya
> On Thursday, September 13, 2018, 7:26:35 AM PDT, JP Gilaberte <jp...@apache.org> wrote:
>
> Hi all,
>
> I am starting this vote (copy from Ambary folks) to migrate Myriad
> project from git-wip
> repository to gitbox, which allows a deeper integration with github
> features. Moving to gitbox will allow committers to merge, close or edit
> pull requests in the github UI.
>
> Other advantages:
>
> - JIRA linking can be enabled on request to the Apache Infra team, which
> will automatically link a PR with its corresponding JIRA in
> https://issues.apache.org/jira
> - It will make our code review process cleaner and more efficient when
> compared to the Review Board.
> - Opens up a lot of opportunities on leveraging the rich set of github
> APIs and web hooks to develop tools that can help monitor the open PRs,
> trigger a jenkins job to run unit tests, etc..
>
> [ ] +1, Migrate Myriad repository to gitbox
> [ ] -1, Keep git-wip + github read-only mirror
>
> Regards,
> JP Gilaberte
>
Re: [Proposal] Migrate to gitbox
Posted by yuliya Feldman <yu...@yahoo.com.INVALID>.
Hello there,
I am trying to figure out what are the real advantages for Myriad in moving it to gitbox
- JIRA linking can be enabled on request to the Apache Infra team, which
will automatically link a PR with its corresponding JIRA in
I believe it is already there
- It will make our code review process cleaner and more efficient when
compared to the Review Board.
I believe we are using github itself for review.
- Opens up a lot of opportunities on leveraging the rich set of github
APIs and web hooks to develop tools that can help monitor the open PRs,
trigger a jenkins job to run unit tests, etc..
Which ones?
Thanks,Yuliya
On Thursday, September 13, 2018, 7:26:35 AM PDT, JP Gilaberte <jp...@apache.org> wrote:
Hi all,
I am starting this vote (copy from Ambary folks) to migrate Myriad
project from git-wip
repository to gitbox, which allows a deeper integration with github
features. Moving to gitbox will allow committers to merge, close or edit
pull requests in the github UI.
Other advantages:
- JIRA linking can be enabled on request to the Apache Infra team, which
will automatically link a PR with its corresponding JIRA in
https://issues.apache.org/jira
- It will make our code review process cleaner and more efficient when
compared to the Review Board.
- Opens up a lot of opportunities on leveraging the rich set of github
APIs and web hooks to develop tools that can help monitor the open PRs,
trigger a jenkins job to run unit tests, etc..
[ ] +1, Migrate Myriad repository to gitbox
[ ] -1, Keep git-wip + github read-only mirror
Regards,
JP Gilaberte
Re: [Proposal] Migrate to gitbox
Posted by Javi Roman <jr...@gmail.com>.
+1
--
Javi Roman
Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info
Apache Id: javiroman
On Thu, Sep 13, 2018 at 5:25 PM Miguel Angel Fernandez Diaz
<mi...@gmail.com> wrote:
>
> +1
>
> Great idea!
>
> On Thu, Sep 13, 2018, 4:26 PM JP Gilaberte <jp...@apache.org> wrote:
>
> > Hi all,
> >
> > I am starting this vote (copy from Ambary folks) to migrate Myriad
> > project from git-wip
> > repository to gitbox, which allows a deeper integration with github
> > features. Moving to gitbox will allow committers to merge, close or edit
> > pull requests in the github UI.
> >
> > Other advantages:
> >
> > - JIRA linking can be enabled on request to the Apache Infra team, which
> > will automatically link a PR with its corresponding JIRA in
> > https://issues.apache.org/jira
> > - It will make our code review process cleaner and more efficient when
> > compared to the Review Board.
> > - Opens up a lot of opportunities on leveraging the rich set of github
> > APIs and web hooks to develop tools that can help monitor the open PRs,
> > trigger a jenkins job to run unit tests, etc..
> >
> > [ ] +1, Migrate Myriad repository to gitbox
> > [ ] -1, Keep git-wip + github read-only mirror
> >
> > Regards,
> > JP Gilaberte
> >
Re: [Proposal] Migrate to gitbox
Posted by Miguel Angel Fernandez Diaz <mi...@gmail.com>.
+1
Great idea!
On Thu, Sep 13, 2018, 4:26 PM JP Gilaberte <jp...@apache.org> wrote:
> Hi all,
>
> I am starting this vote (copy from Ambary folks) to migrate Myriad
> project from git-wip
> repository to gitbox, which allows a deeper integration with github
> features. Moving to gitbox will allow committers to merge, close or edit
> pull requests in the github UI.
>
> Other advantages:
>
> - JIRA linking can be enabled on request to the Apache Infra team, which
> will automatically link a PR with its corresponding JIRA in
> https://issues.apache.org/jira
> - It will make our code review process cleaner and more efficient when
> compared to the Review Board.
> - Opens up a lot of opportunities on leveraging the rich set of github
> APIs and web hooks to develop tools that can help monitor the open PRs,
> trigger a jenkins job to run unit tests, etc..
>
> [ ] +1, Migrate Myriad repository to gitbox
> [ ] -1, Keep git-wip + github read-only mirror
>
> Regards,
> JP Gilaberte
>