mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco de Abreu <>
Subject Re: Vote to stop using JIRA
Date Sat, 09 Jun 2018 08:13:36 GMT

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,

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]
> [2]
>  "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."

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message