Re: Unable to comment on GitHub issue

[Sheng Zha]

Locking a conversation wouldn't limit a committer from commenting. "While a 
conversation is locked, only people with write access and repository owners and 
collaborators can add comments." [1]

Unless the apache organization has the blocking setting, blocking by a person 
shouldn't limit one from commenting on issues in mxnet repo either. The 
organization that owns the repo needs to explicitly block the person to be able 
to prevent one from commenting on an issue in the repo of that organization. [2]

-sz

[1] https://help.github.com/en/articles/locking-conversations
[2] 
https://help.github.com/en/articles/blocking-a-user-from-your-personal-account

On 2019/05/09 23:33:00, Aaron Markham  wrote: 
> I just locked one of the issues I created:
> https://github.com/apache/incubator-mxnet/issues/14918
> Are you sure you don't have the unlock button on the right side?
> You should see this:
> 
> aaronmarkham locked as off topic and limited conversation to
> collaborators 24 seconds from now
> 
> Then to the right of that:
> 
>  Unlock conversation
>  Pin issue
> 
> On Thu, May 9, 2019 at 4:27 PM Naveen Swamy  wrote:
> >
> > I don't see the option, another possible explanation someone must have 
> > blocked me, if that is the case it goes against the ethos of Open source.
> > Apache infra should override that setting for Apache projects. Anyway I 
> > created this Jira.
> > https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-18356
> >
> > -Naveen
> >
> > > On May 9, 2019, at 4:19 PM, Aaron Markham  
> > > wrote:
> > >
> > > A new feature: https://help.github.com/en/articles/locking-conversations
> > > So someone must have locked it. I can see the option on the right hand
> > > side column, all the way at the bottom. You will probably have the
> > > ability to unlock it from there too.
> > >
> > >> On Thu, May 9, 2019 at 3:42 PM Chaitanya Bapat  
> > >> wrote:
> > >>
> > >> Any specific issues you could give the links to? So I could verify if
> > >> that's the case with me.
> > >>
> > >>> On Thu, 9 May 2019 at 14:44, Naveen Swamy  wrote:
> > >>>
> > >>> I am unable to comment on certain GitHub issues and see a locked Icon,
> > >>> wondering if anyone has experienced this and know why?
> > >>>
> > >>
> > >>
> > >> --
> > >> *Chaitanya Prakash Bapat*
> > >> *+1 (973) 953-6299*
> > >>
> > >> [image: https://www.linkedin.com//in/chaibapat25]
> > >> [image: 
> > >> https://www.facebook.com/chaibapat]
> > >> [image:
> > >> https://twitter.com/ChaiBapchya] [image:
> > >> https://www.linkedin.com//in/chaibapat25]
> > >> 
> 

Re: [DISCUSS] AWS Credits for External Contributors

[Chaitanya Bapat]

Sure. I'll use the AWS Educate route (Google Colab or AWS SageMaker would
be great for an MXNet User, but I wanted to build and test. Moreover, for
memory profiling, need access to an instance with GPU more than anything
else). But anyway, I'll use AWS Educate.

Thanks for the quick response.

On Thu, 9 May 2019 at 19:08, Aaron Markham 
wrote:

> One option is Amazon Educate. https://aws.amazon.com/education/awseducate/
> Last I checked, you can get $75/month AWS credit as a student or
> educator. If you belong to an educational organization, your org can
> apply on your behalf and get anyone with that org's domain easier
> access to the credits. Or something like that.
>
> Another route is you might be able to load your test/work into a
> notebook and run it on Google Colab. Vandana has this neat DCGAN with
> MXNet notebook running there.
>
> https://colab.research.google.com/github/vandanavk/mxnet-gluon-gan/blob/dcgan/dcgan/dcgan.ipynb
>
> Will either of those work for you?
>
> Cheers,
> Aaron
>
> On Thu, May 9, 2019 at 11:30 AM Chaitanya Bapat 
> wrote:
> >
> > Hello MXNet community,
> >
> > I was curious to know if there is any possibility of AWS Credits
> > provisioned for external contributors of Apache MXNet. It would be a
> great
> > incentive for more external contributions and in turn more external
> > contributors.
> >
> > Background -
> > Today, while trying to work on Anirudh's Memory profiling for MXNet PR, I
> > realized I am short of AWS credits on my personal account. My personal
> > computer (Mac 2017) doesn't have Nvidia GPU and hence I'm a bit stuck.
> >
> > I don't know if there are others who have faced a similar situation. If
> > that's the case, maybe we can find a solution through free AWS Credits.
> >
> > Thanks,
> > Chai
> >
> > --
> > *Chaitanya Prakash Bapat*
> > *+1 (973) 953-6299*
> >
> > [image: https://www.linkedin.com//in/chaibapat25]
> > [image:
> https://www.facebook.com/chaibapat]
> > [image:
> > https://twitter.com/ChaiBapchya]  >[image:
> > https://www.linkedin.com//in/chaibapat25]
> > 
>


-- 
*Chaitanya Prakash Bapat*
*+1 (973) 953-6299*

[image: https://www.linkedin.com//in/chaibapat25]
[image: https://www.facebook.com/chaibapat]
[image:
https://twitter.com/ChaiBapchya] [image:
https://www.linkedin.com//in/chaibapat25]

Re: Unable to comment on GitHub issue

[Naveen Swamy]

I don't see the option, another possible explanation someone must have blocked 
me, if that is the case it goes against the ethos of Open source.
Apache infra should override that setting for Apache projects. Anyway I created 
this Jira.
https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-18356

-Naveen

> On May 9, 2019, at 4:19 PM, Aaron Markham  wrote:
> 
> A new feature: https://help.github.com/en/articles/locking-conversations
> So someone must have locked it. I can see the option on the right hand
> side column, all the way at the bottom. You will probably have the
> ability to unlock it from there too.
> 
>> On Thu, May 9, 2019 at 3:42 PM Chaitanya Bapat  wrote:
>> 
>> Any specific issues you could give the links to? So I could verify if
>> that's the case with me.
>> 
>>> On Thu, 9 May 2019 at 14:44, Naveen Swamy  wrote:
>>> 
>>> I am unable to comment on certain GitHub issues and see a locked Icon,
>>> wondering if anyone has experienced this and know why?
>>> 
>> 
>> 
>> --
>> *Chaitanya Prakash Bapat*
>> *+1 (973) 953-6299*
>> 
>> [image: https://www.linkedin.com//in/chaibapat25]
>> [image: https://www.facebook.com/chaibapat]
>> [image:
>> https://twitter.com/ChaiBapchya] [image:
>> https://www.linkedin.com//in/chaibapat25]
>> 

Re: Unable to comment on GitHub issue

[Aaron Markham]

A new feature: https://help.github.com/en/articles/locking-conversations
So someone must have locked it. I can see the option on the right hand
side column, all the way at the bottom. You will probably have the
ability to unlock it from there too.

On Thu, May 9, 2019 at 3:42 PM Chaitanya Bapat  wrote:
>
> Any specific issues you could give the links to? So I could verify if
> that's the case with me.
>
> On Thu, 9 May 2019 at 14:44, Naveen Swamy  wrote:
>
> > I am unable to comment on certain GitHub issues and see a locked Icon,
> > wondering if anyone has experienced this and know why?
> >
>
>
> --
> *Chaitanya Prakash Bapat*
> *+1 (973) 953-6299*
>
> [image: https://www.linkedin.com//in/chaibapat25]
> [image: https://www.facebook.com/chaibapat]
> [image:
> https://twitter.com/ChaiBapchya] [image:
> https://www.linkedin.com//in/chaibapat25]
> 

Re: [DISCUSS] AWS Credits for External Contributors

[Aaron Markham]

One option is Amazon Educate. https://aws.amazon.com/education/awseducate/
Last I checked, you can get $75/month AWS credit as a student or
educator. If you belong to an educational organization, your org can
apply on your behalf and get anyone with that org's domain easier
access to the credits. Or something like that.

Another route is you might be able to load your test/work into a
notebook and run it on Google Colab. Vandana has this neat DCGAN with
MXNet notebook running there.
https://colab.research.google.com/github/vandanavk/mxnet-gluon-gan/blob/dcgan/dcgan/dcgan.ipynb

Will either of those work for you?

Cheers,
Aaron

On Thu, May 9, 2019 at 11:30 AM Chaitanya Bapat  wrote:
>
> Hello MXNet community,
>
> I was curious to know if there is any possibility of AWS Credits
> provisioned for external contributors of Apache MXNet. It would be a great
> incentive for more external contributions and in turn more external
> contributors.
>
> Background -
> Today, while trying to work on Anirudh's Memory profiling for MXNet PR, I
> realized I am short of AWS credits on my personal account. My personal
> computer (Mac 2017) doesn't have Nvidia GPU and hence I'm a bit stuck.
>
> I don't know if there are others who have faced a similar situation. If
> that's the case, maybe we can find a solution through free AWS Credits.
>
> Thanks,
> Chai
>
> --
> *Chaitanya Prakash Bapat*
> *+1 (973) 953-6299*
>
> [image: https://www.linkedin.com//in/chaibapat25]
> [image: https://www.facebook.com/chaibapat]
> [image:
> https://twitter.com/ChaiBapchya] [image:
> https://www.linkedin.com//in/chaibapat25]
> 

Re: Unable to comment on GitHub issue

[Chaitanya Bapat]

Any specific issues you could give the links to? So I could verify if
that's the case with me.

On Thu, 9 May 2019 at 14:44, Naveen Swamy  wrote:

> I am unable to comment on certain GitHub issues and see a locked Icon,
> wondering if anyone has experienced this and know why?
>


-- 
*Chaitanya Prakash Bapat*
*+1 (973) 953-6299*

[image: https://www.linkedin.com//in/chaibapat25]
[image: https://www.facebook.com/chaibapat]
[image:
https://twitter.com/ChaiBapchya] [image:
https://www.linkedin.com//in/chaibapat25]

Unable to comment on GitHub issue

[Naveen Swamy]

I am unable to comment on certain GitHub issues and see a locked Icon,
wondering if anyone has experienced this and know why?

[DISCUSS] AWS Credits for External Contributors

[Chaitanya Bapat]

Hello MXNet community,

I was curious to know if there is any possibility of AWS Credits
provisioned for external contributors of Apache MXNet. It would be a great
incentive for more external contributions and in turn more external
contributors.

Background -
Today, while trying to work on Anirudh's Memory profiling for MXNet PR, I
realized I am short of AWS credits on my personal account. My personal
computer (Mac 2017) doesn't have Nvidia GPU and hence I'm a bit stuck.

I don't know if there are others who have faced a similar situation. If
that's the case, maybe we can find a solution through free AWS Credits.

Thanks,
Chai

-- 
*Chaitanya Prakash Bapat*
*+1 (973) 953-6299*

[image: https://www.linkedin.com//in/chaibapat25]
[image: https://www.facebook.com/chaibapat]
[image:
https://twitter.com/ChaiBapchya] [image:
https://www.linkedin.com//in/chaibapat25]

Re: [Announcement] New Committer - Zach Kimberg

[Chaitanya Bapat]

Congratulations Zachary! Way to go!

On Thu, 9 May 2019 at 14:01, Carin Meier  wrote:

> Congrats!
>
> On Thu, May 9, 2019 at 1:41 PM Per da Silva  wrote:
>
> > Nice one! Congratulations =)
> >
> > On Thu, May 9, 2019 at 7:38 PM Jake Lee  wrote:
> >
> > > Congrat!
> > >
> > > On Thu, May 9, 2019 at 10:37 AM Yuan Tang 
> > wrote:
> > >
> > > > Welcome!
> > > >
> > > > On Thu, May 9, 2019 at 1:36 PM Marco de Abreu <
> marco.g.ab...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Welcome!
> > > > >
> > > > > Hagay Lupesko  schrieb am Do., 9. Mai 2019,
> > 19:33:
> > > > >
> > > > > > Congratulations Zach - well deserved!
> > > > > >
> > > > > > On Thu, May 9, 2019, 13:26 Qing Lan  wrote:
> > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > Please join me in welcoming Zach Kimberg (
> > > https://github.com/zachgk)
> > > > > as
> > > > > > a
> > > > > > > new committer.
> > > > > > >
> > > > > > > He has been solving some important bugs in MXNet JVM with
> respect
> > > to
> > > > > > usage
> > > > > > > improvement, build issues and a lot more. He also created the
> > > Jenkins
> > > > > > based
> > > > > > > publish pipeline for us to have standard way to build and test
> > > > > > > static-linked package conveniently for everyone in the
> community.
> > > > > > Moreover,
> > > > > > > he solved a bunch of License problems we have in MXNet and
> > brought
> > > > > > several
> > > > > > > fixes to let us get 1.4.0 release on time.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Qing
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


-- 
*Chaitanya Prakash Bapat*
*+1 (973) 953-6299*

[image: https://www.linkedin.com//in/chaibapat25]
[image: https://www.facebook.com/chaibapat]
[image:
https://twitter.com/ChaiBapchya] [image:
https://www.linkedin.com//in/chaibapat25]

Re: [Announcement] New Committer - Zach Kimberg

[Carin Meier]

Congrats!

On Thu, May 9, 2019 at 1:41 PM Per da Silva  wrote:

> Nice one! Congratulations =)
>
> On Thu, May 9, 2019 at 7:38 PM Jake Lee  wrote:
>
> > Congrat!
> >
> > On Thu, May 9, 2019 at 10:37 AM Yuan Tang 
> wrote:
> >
> > > Welcome!
> > >
> > > On Thu, May 9, 2019 at 1:36 PM Marco de Abreu  >
> > > wrote:
> > >
> > > > Welcome!
> > > >
> > > > Hagay Lupesko  schrieb am Do., 9. Mai 2019,
> 19:33:
> > > >
> > > > > Congratulations Zach - well deserved!
> > > > >
> > > > > On Thu, May 9, 2019, 13:26 Qing Lan  wrote:
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > Please join me in welcoming Zach Kimberg (
> > https://github.com/zachgk)
> > > > as
> > > > > a
> > > > > > new committer.
> > > > > >
> > > > > > He has been solving some important bugs in MXNet JVM with respect
> > to
> > > > > usage
> > > > > > improvement, build issues and a lot more. He also created the
> > Jenkins
> > > > > based
> > > > > > publish pipeline for us to have standard way to build and test
> > > > > > static-linked package conveniently for everyone in the community.
> > > > > Moreover,
> > > > > > he solved a bunch of License problems we have in MXNet and
> brought
> > > > > several
> > > > > > fixes to let us get 1.4.0 release on time.
> > > > > >
> > > > > > Thanks,
> > > > > > Qing
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [Announcement] New Committer - Zach Kimberg

[Yuan Tang]

Welcome!

On Thu, May 9, 2019 at 1:36 PM Marco de Abreu 
wrote:

> Welcome!
>
> Hagay Lupesko  schrieb am Do., 9. Mai 2019, 19:33:
>
> > Congratulations Zach - well deserved!
> >
> > On Thu, May 9, 2019, 13:26 Qing Lan  wrote:
> >
> > > Hi All,
> > >
> > > Please join me in welcoming Zach Kimberg (https://github.com/zachgk)
> as
> > a
> > > new committer.
> > >
> > > He has been solving some important bugs in MXNet JVM with respect to
> > usage
> > > improvement, build issues and a lot more. He also created the Jenkins
> > based
> > > publish pipeline for us to have standard way to build and test
> > > static-linked package conveniently for everyone in the community.
> > Moreover,
> > > he solved a bunch of License problems we have in MXNet and brought
> > several
> > > fixes to let us get 1.4.0 release on time.
> > >
> > > Thanks,
> > > Qing
> > >
> >
>

Re: [Announcement] New Committer - Zach Kimberg

[Jake Lee]

Congrat!

On Thu, May 9, 2019 at 10:37 AM Yuan Tang  wrote:

> Welcome!
>
> On Thu, May 9, 2019 at 1:36 PM Marco de Abreu 
> wrote:
>
> > Welcome!
> >
> > Hagay Lupesko  schrieb am Do., 9. Mai 2019, 19:33:
> >
> > > Congratulations Zach - well deserved!
> > >
> > > On Thu, May 9, 2019, 13:26 Qing Lan  wrote:
> > >
> > > > Hi All,
> > > >
> > > > Please join me in welcoming Zach Kimberg (https://github.com/zachgk)
> > as
> > > a
> > > > new committer.
> > > >
> > > > He has been solving some important bugs in MXNet JVM with respect to
> > > usage
> > > > improvement, build issues and a lot more. He also created the Jenkins
> > > based
> > > > publish pipeline for us to have standard way to build and test
> > > > static-linked package conveniently for everyone in the community.
> > > Moreover,
> > > > he solved a bunch of License problems we have in MXNet and brought
> > > several
> > > > fixes to let us get 1.4.0 release on time.
> > > >
> > > > Thanks,
> > > > Qing
> > > >
> > >
> >
>

Re: [Announcement] New Committer - Zach Kimberg

[Per da Silva]

Nice one! Congratulations =)

On Thu, May 9, 2019 at 7:38 PM Jake Lee  wrote:

> Congrat!
>
> On Thu, May 9, 2019 at 10:37 AM Yuan Tang  wrote:
>
> > Welcome!
> >
> > On Thu, May 9, 2019 at 1:36 PM Marco de Abreu 
> > wrote:
> >
> > > Welcome!
> > >
> > > Hagay Lupesko  schrieb am Do., 9. Mai 2019, 19:33:
> > >
> > > > Congratulations Zach - well deserved!
> > > >
> > > > On Thu, May 9, 2019, 13:26 Qing Lan  wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > Please join me in welcoming Zach Kimberg (
> https://github.com/zachgk)
> > > as
> > > > a
> > > > > new committer.
> > > > >
> > > > > He has been solving some important bugs in MXNet JVM with respect
> to
> > > > usage
> > > > > improvement, build issues and a lot more. He also created the
> Jenkins
> > > > based
> > > > > publish pipeline for us to have standard way to build and test
> > > > > static-linked package conveniently for everyone in the community.
> > > > Moreover,
> > > > > he solved a bunch of License problems we have in MXNet and brought
> > > > several
> > > > > fixes to let us get 1.4.0 release on time.
> > > > >
> > > > > Thanks,
> > > > > Qing
> > > > >
> > > >
> > >
> >
>

Re: [Announcement] New Committer - Zach Kimberg

[Marco de Abreu]

Welcome!

Hagay Lupesko  schrieb am Do., 9. Mai 2019, 19:33:

> Congratulations Zach - well deserved!
>
> On Thu, May 9, 2019, 13:26 Qing Lan  wrote:
>
> > Hi All,
> >
> > Please join me in welcoming Zach Kimberg (https://github.com/zachgk) as
> a
> > new committer.
> >
> > He has been solving some important bugs in MXNet JVM with respect to
> usage
> > improvement, build issues and a lot more. He also created the Jenkins
> based
> > publish pipeline for us to have standard way to build and test
> > static-linked package conveniently for everyone in the community.
> Moreover,
> > he solved a bunch of License problems we have in MXNet and brought
> several
> > fixes to let us get 1.4.0 release on time.
> >
> > Thanks,
> > Qing
> >
>

Re: [Announcement] New Committer - Zach Kimberg

[Hagay Lupesko]

Congratulations Zach - well deserved!

On Thu, May 9, 2019, 13:26 Qing Lan  wrote:

> Hi All,
>
> Please join me in welcoming Zach Kimberg (https://github.com/zachgk) as a
> new committer.
>
> He has been solving some important bugs in MXNet JVM with respect to usage
> improvement, build issues and a lot more. He also created the Jenkins based
> publish pipeline for us to have standard way to build and test
> static-linked package conveniently for everyone in the community. Moreover,
> he solved a bunch of License problems we have in MXNet and brought several
> fixes to let us get 1.4.0 release on time.
>
> Thanks,
> Qing
>

[Announcement] New Committer - Zach Kimberg

[Qing Lan]

Hi All,

Please join me in welcoming Zach Kimberg (https://github.com/zachgk) as a new 
committer.

He has been solving some important bugs in MXNet JVM with respect to usage 
improvement, build issues and a lot more. He also created the Jenkins based 
publish pipeline for us to have standard way to build and test static-linked 
package conveniently for everyone in the community. Moreover, he solved a bunch 
of License problems we have in MXNet and brought several fixes to let us get 
1.4.0 release on time.

Thanks,
Qing

Re: [RESULTS] [VOTE] Release Apache MXNet (incubating) version 1.4.1.rc0

[Hen]

Noting that I am a belated +1 on the release.

I had one item regarding dataset licensing that I’d like to see improved
for the next release, but I don’t believe it would have been a blocker.

Hen

On Sat, May 4, 2019 at 00:00 Junru Shao  wrote:

> Dear MXNet community,
>
> I'm happy to announce the results of the vote.
>
> This vote passes with 12 +1 votes (3 binding), no 0 votes, and 1 -1 vote.
> +1 votes
> * Sheng Zha / binding
> * Qing Lan / binding
> * Carin Meier / binding
> * Aaron Markham
> * Pedro Larroy
> * Lai Wei
> * Damien Stanton
> * Kellen Sunderland
> * Yuxi Hu
> * Joshua Z. Zhang
> * Philip Hyunsu Cho
> * Aston Zhang
>
> 0 votes
> * No votes
>
> -1 votes
> * Anirudh Subramanian
>
> Vote thread can be found here [1]. The list of members can be found here
> [2].
>
> I'll continue with the release process and the release announcement will
> follow in the next few days.
>
> Best regards,
> Junru Shao
>
> [1]
>
> https://lists.apache.org/thread.html/6c140f4c180c259dd1b7f4ecf36f2d083ed810cd68b37d7f635f5614@%3Cdev.mxnet.apache.org%3E
> [2] http://incubator.apache.org/projects/mxnet.html
>