Re: [VOTE] Release MXNet version 1.3.0.RC0

[Pigeon Lucky]

+1

On Sat, 1 Sep 2018, 10:59 Roshani Nagmote, 
wrote:

> Hi all,
>
> I would like to propose a vote to release Apache MXNet (incubating) version
> 1.3.0.RC0. Voting will start now (Friday, Aug 31st) and end at 7:00 PM
> PDT, Wednesday, Sept 5th.
>
> Link to release notes:
> https://github.com/apache/incubator-mxnet/releases
>
> Link to release candidate 1.3.0.rc0:
> *https://github.com/apache/incubator-mxnet/releases/tag/1.3.0.rc
> 0*
>
> View this page, click on "Build from Source", and use the source code
> obtained from 1.3.0.rc0 tag:
> https://mxnet.incubator.apache.org/install/index.html
>
> Please remember to TEST first before voting accordingly:
>
> +1 = approve
> +0 = no opinion
> -1 = disapprove (provide reason)
>
> Thanks,
> Roshani
>

Re: Vote to stop using JIRA

[Pigeon Lucky]

+0.5
I think we can separate our JIRA issue to two groups, one is a simpler
group to the new who wants to contribute to MXNET but haven't become a
contributer yet and will be published in the github issue, another for only
contributer to access, which of course will have some more harder to answer
or codding questions and will be published at JIRA.
For example, the simple one can be documents, bug fix or new ideas, the the
harder one can be new idea implementation.

On 9 Jun 2018 4:13 p.m., "Marco de Abreu" 
wrote:

> Hi,
>
> thanks for your feedback!
>
> I think the big problem is that we have nobody who maintains JIRA properly.
> If we had a dedicated person who owns that system, I'm sure we could excell
> at it's usage and it would provide better value. About the plugins, I have
> to agree that we can just request assistance from Apache INFRA - that's
> what they are here for.
>
> Eric, we can't use GitHub the way you think you can. All features are
> restricted to committers only. Nobody who's not a committer can change a
> project plan, add tasks, change the status or do anything at all. JIRA -
> with proper configuration - would allow this. I think we have to focus on
> getting JIRA to work with the use cases we have and then we can revisit it.
> But so far, unfortunately there has been nobody to step up.
>
> I'd like to invite any non-committer to step up and help us with that
> system. We are able to grant any permissions even to non-committers, so
> that should not be a problem.
>
> Best regards,
> Marco
>
> Yasser Zamani  schrieb am Sa., 9. Juni 2018,
> 07:36:
>
> >
> >
> > On 6/8/2018 9:57 PM, Eric Xie wrote:
> > > Hi,
> > >
> > > Since all of MXNet's development happens on Github, I think it's
> > sufficient to use Github Issues and Github Projects for tracking. There
> are
> > also many other plugins you can add to Github if issues and projects are
> > not enough.
> > >
> > > It's very easy to cross reference PRs and issues for tracking. In
> > comparison, JIRA is an outdated system with very little features and no
> > integration with Github. I think using it achieves nothing but additional
> > overhead.
> >
> > -1 as I afraid it may violate "Apache Way". Microsoft is going to buy
> > GitHub. What happens to Apache histories if one day he decided to drop
> > GitHub data including Apache projects histories?! or decided to change
> > usage license or payment?! and etc!
> >
> > However, I found it seems was legally OK in 2016 [1] BUT I think we must
> > ask again also "general@incubator and/or community@apache and/or board
> > rather than at legal-discuss" [1]. (at least informs them about the
> > state of the art).
> >
> > I personally prefer to stick together with Apache INFRA Team and ask
> > them to automate any overhead work instead. e.g. they already have a
> > nice JIRA and GitHub PR connection [2].
> >
> > Regards.
> >
> > [1]
> >
> > https://lists.apache.org/thread.html/2890619eb1ca049f057c95a3378efc
> 7be5d54d646c693d2e2560c103@%3Clegal-discuss.apache.org%3E
> > [2]
> >
> > https://github.com/openzipkin/openzipkin.github.io/issues/
> 51#issuecomment-250877803
> >  "For our project, a PR should have a corresponding JIRA issue -- we use
> > GH PR templates to tell contributors what to do . For issue tracking we
> > use Apache JIRA. Apache has webhooks in Github that detects the "JIRA
> > token" in a PR title (for example, the token for this PR is CB-11860 and
> > this makes any GH comments in the PR reflect back to the JIRA issue (but
> > not vice versa), and it is also sent to a project mailing list as well."
> >
>

Re: home page highlights section updates

[Pigeon Lucky]

+1
Thanks, ITSA a great idea!

On 7 Jun 2018 3:50 a.m., "Corston-Oliver, Simon" 
wrote:

> +1
>
> I've been meaning to post a digest of the tutorials, blogs, videos posted
> during May but a continually updated feed in a visible place as discussed
> below would be great
>
> On 6/4/18, 9:47 AM, "Lane, Thom"  wrote:
>
> Cheers Aaron. My vote would be for something more like Wireframe 2.
>
> Would be great if we could add thumbnail images to these too, to draw
> more attention and also make the boxes a little less empty.
>
> As Sandeep already mentioned, connecting to our Medium/Twitter/YouTube
> streams would be a great way to get fresh content on the website, but we'd
> probably want an extra category for this. One possibility is;
>
> 1) News/Announcements (new versions, apis, toolkits, etc)
> 2) Social (mostly Twitter, since we tweet about our Medium posts and
> YouTube videos)
> 3) Tutorials and Examples (combined)
>
> On 6/1/18, 2:58 PM, "Aaron Markham"  wrote:
>
> Hi everyone, happy Friday,
>
> I've mocked up a couple of modifications for the highlights on the
> home
> page.
> The goal is to expose more news, more tutorials, and other
> interesting
> things people have been working on. If you've contributed something
> interesting and want to highlight it, you should be able to
> suggest an
> update to the page.
> It would be great to have variety and fresh content on the site.
>
> Here are a couple of ideas with screenshots that shouldn't be to
> hard to
> implement:
> https://cwiki.apache.org/confluence/display/MXNET/
> Website+Interface+Updates
>
> You can reply with feedback here or make comments on the wiki!
> What are
> your thoughts on:
> 1) getting fresh content on the site
> 2) highlighting contributors and their contributions
> 3) flow on changes and what kind of approvals are expected for
> swapping out
> highlights
> 4) UX ideas that are not too challenging to implement or maintain
> and work
> well with mobile
>
> Cheers,
> Aaron
>
>
>
>
>