Re: Which merge option to use on the Import Julia binding PR?

2018-10-05 Thread Pedro Larroy
Thanks for the efforts, looks like you guys achieved a good solution,
congratulations for the merge to everyone involved.

Pedro.



On Thu, Oct 4, 2018 at 5:47 PM Carin Meier  wrote:

> Micheal,
>
> Thanks. You were right! I could merge.
>
> The PR shows up now as merged
> https://github.com/apache/incubator-mxnet/pull/10149
> My merge commit is here
> https://github.com/apache/incubator-mxnet/commits/master
>
> Thanks again for the help.
>
> - Carin
>
>
>
> On Thu, Oct 4, 2018 at 8:09 PM Michael Wall  wrote:
>
> > I would try the merge locally and then inspect the result closely to make
> > sure it looks like what you want.  If it looks good, you could try
> pushing
> > to master.  If you can't push, then we know but I "think" protected just
> > means you can't force push in this case based on
> > https://issues.apache.org/jira/browse/INFRA-15233 which links to
> > https://home.apache.org/~pono/mxnet.png.  Maybe I have only tried that
> > with
> > repo that own though.
> >
> > I did find at least one ticket where a team asked for merge commits to be
> > enabled, https://issues.apache.org/jira/browse/INFRA-16690.  But I think
> > they intend for it to stay that way.  Is that what the community would
> want
> > for the MXNet repo?  Or would you want to enable it for this and disable
> it
> > again?
> >
> >
> > On Thu, Oct 4, 2018 at 7:29 PM Carin Meier  wrote:
> >
> > > Micheal,
> > >
> > > Thanks for catching up and helping us with this.
> > > I do see the "view command line instructions". I just assumed that
> master
> > > was a protected branch and I would not be able to push to it.
> > > Honestly, I'm a bit scared if it isn't :)
> > >
> > > What do you suggest? Should I try to merge and push to master?
> > >
> > > On Thu, Oct 4, 2018 at 7:19 PM Michael Wall  wrote:
> > >
> > > > Just now looking at this.  The button is disabled for merge commit as
> > you
> > > > have mentioned.  Before I go to INFRA, is the command line an option?
> > Do
> > > > you see "or view command line instructions" beside the green squash
> and
> > > > merge button?
> > > >
> > > > On Thu, Oct 4, 2018 at 9:09 AM Carin Meier 
> > wrote:
> > > >
> > > > > Thank you Mike!
> > > > >
> > > > > On Thu, Oct 4, 2018 at 8:54 AM Michael Wall 
> > wrote:
> > > > >
> > > > > > Hi Carin,
> > > > > >
> > > > > > I will take a look at this tonight.  I am not tracking
> everything,
> > > so I
> > > > > > want to go back and make sure I understand what is being asked.
> > > Then I
> > > > > am
> > > > > > happy to submit an INFRA ticket.
> > > > > >
> > > > > > Mike
> > > > > >
> > > > > > On Thu, Oct 4, 2018 at 8:36 AM Carin Meier  >
> > > > wrote:
> > > > > >
> > > > > > > I just found out that since we are a podling, we should route
> all
> > > our
> > > > > > Infra
> > > > > > > tickets through one of our mentors and link the dev list
> > discussion
> > > > in
> > > > > > > JIRA.
> > > > > > >
> > > > > > > Is there a mentor that is willing to help us navigate this
> > process
> > > to
> > > > > get
> > > > > > > the PR merged?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Carin
> > > > > > >
> > > > > > > On Tue, Oct 2, 2018 at 8:42 AM Carin Meier <
> carinme...@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Marco - Thanks for the "dry run" idea. It will give everyone
> a
> > > > clear
> > > > > > idea
> > > > > > > > of the process and what the expected results will look like.
> > > > > > > >
> > > > > > > > - I took my fork of the repo and synced my master branch.
> > > > > > > > - @iblis17 made a copy of the branch of the Julia import PR
> and
> > > > > > submitted
> > > > > > > > it to my repo
> > > > > > > > - I merged it with the "Merge" option through the web
> > interface.
> > > > > > > >
> > > > > > > > Here is a gif of the process of merging:
> > > > > > > > http://g.recordit.co/DzBcFtnjmV.gif
> > > > > > > > Here is the result of the repo:
> > > > > > > > https://github.com/gigasquid/incubator-mxnet
> > > > > > > >
> > > > > > > > Please everyone take a look and validate that this looks ok.
> > > > > > > >
> > > > > > > > If there are no objections, Marco - could you please take the
> > > lead
> > > > in
> > > > > > > > requesting the actions from INFRA?
> > > > > > > >
> > > > > > > > It will be great to *finally* get this PR in  :)
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Carin
> > > > > > > >
> > > > > > > > <
> > > > https://github.com/gigasquid/incubator-mxnet/commits?author=iblis17
> > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Sep 29, 2018 at 10:02 PM Chiyuan Zhang <
> > > plus...@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Sorry, here is the image: https://imgur.com/V5wd2XB
> > > > > > > >>
> > > > > > > >> And here is the github document on the 3 different merge
> > options
> > > > for
> > > > > > the
> > > > > > > >> web UI button:
> > > > > > > >> https://help.github.com/articles/about-pull-request-merges/
> > > > > > > >>
> >

Re: Create a Jira board for C/C++ API project

2018-10-05 Thread Naveen Swamy
Thanks for making the effort to bring tasks and feature improvements under
a managed boards in JIRA.  This will help in users/contributors to quickly
look through the stories/tasks and contribute to the project that they are
interested in.

We were able to create JIRA boards/filter and share it across the project
earlier. since the last few months I am unable to share the boards that I
create with the project( there was possibly an upgrade to JIRA that removed
access).  Now it looks like it needs global permission to create shared
boards and filter.[1]

We will need to create ticket to Apache INFRA to grant access. Can one of
the mentors help create INFRA ticket?

[1]
https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html

Thanks, Naveen

On Fri, Oct 5, 2018 at 11:14 AM Davydenko, Denis <
dzianis.davydze...@gmail.com> wrote:

> Hello, MXNet community,
>
>
>
> As part of mine and couple of my team mates day job we are working on
> contributing towards C++ and C APIs that MXNet exposes. We would like to
> propose to create a separate board in jira in order to make it easier to
> track work around MXNet C/C++ APIs. Very similar to
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=211
> (which we are using for managing development of Scala and Java APIs) but
> bound to show C/C++ sprints and work items. This will also give a better
> exposure to C/C++ API work for users to be aware of where these APIs moving
> as well as will make it easier to manage work on those APIs between
> multiple contributors.
>
>
>
> --
>
> Thanks,
>
> Denis
>
>


Create a Jira board for C/C++ API project

2018-10-05 Thread Davydenko, Denis
Hello, MXNet community,

 

As part of mine and couple of my team mates day job we are working on 
contributing towards C++ and C APIs that MXNet exposes. We would like to 
propose to create a separate board in jira in order to make it easier to track 
work around MXNet C/C++ APIs. Very similar to 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=211 (which we 
are using for managing development of Scala and Java APIs) but bound to show 
C/C++ sprints and work items. This will also give a better exposure to C/C++ 
API work for users to be aware of where these APIs moving as well as will make 
it easier to manage work on those APIs between multiple contributors.

 

--

Thanks,

Denis



Re: MXNet Podling Report - October

2018-10-05 Thread Michael Wall
Looks good to me. Not sure that Justin is subscribed to the dev so
including him explicitly here.  Thanks Haibin.

Mike

On Thu, Oct 4, 2018 at 8:12 PM Haibin Lin  wrote:

> Hi Justin and Michael,
>
> I updated the report with the links to the tutorial summaries:
> June -
>
> https://lists.apache.org/thread.html/52f88e9dc7a6a2a1dfa5ad41c469fe2cdd1209a0be2eb345bc2f9a96@%3Cuser.mxnet.apache.org%3E
> July -
>
> https://lists.apache.org/thread.html/dea9184350f2fe87ce450722ead28072f763196045f39859190f83f8@%3Cuser.mxnet.apache.org%3E
> August - https://discuss.mxnet.io/t/apache-mxnet-digest-august-2018/1863
>
> Justin, the length of the permanent link is longer than 76 characters.
> Would this be an issue?
>
> Best,
> Haibin
>
>
>
> On Thu, Oct 4, 2018 at 1:16 PM Haibin Lin 
> wrote:
>
> > Hi Justin,
> >
> > Thanks for the notice. I've reformatted the MXNet section to have at most
> > 76 characters per line. Sorry about the last minute update.
> >
> > Best,
> > Haibin
> >
> > On Thu, Oct 4, 2018 at 12:59 PM Justin Mclean 
> wrote:
> >
> >> Hi,
> >>
> >> I noticed you have edited the report after the due date and have broken
> >> the formatting a little after I formatted it. Each line must have a
> maximum
> >> of 76 characters, would you mind fixing your section of the report?
> >>
> >> Thanks,
> >> Justin
> >>
> >
>