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
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
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.
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
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.
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
I am unable to comment on certain GitHub issues and see a locked Icon,
wondering if anyone has experienced this and know why?
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
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
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
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
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
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
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
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
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
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
17 matches
Mail list logo