Hi Naveen, Can we clarify that how JIRA improved the project? One key Apache spirit is about transparent, but I didn't see the current way we are using JIRA improves it. Comparing to Spark, one major problem is that we have 10x less active contributors. Even PyTorch is 3x more active (#commits, #LOC #contributors) than us. If JIRA makes contributing harder, we should consider a better approach.
Best Mu On Fri, Jun 8, 2018 at 10:35 AM, Naveen Swamy <[email protected]> wrote: > -1 (binding) > > The very reason why JIRA was suggested so that the project is more open on > the features that are worked on. There are 900+ issues, that once in a > while gets closed without any reason has happened already once. > There is already integration with GitHub PRs, please check it out. > > Features pop into the code-base without any discussion, they also get > removed without any discussion. PRs come in when the feature is complete, > not giving others opportunity to understand/contribute or have a say. > > If this project embraces the true Apache spirit and follow successful > practices we could get lot more people excited about this project. Many > successful Apache projects use JIRA, look at Apache Spark which has 1250+ > contributors and built a community of 500,000 people around the world. > > -Naveen > > > On Fri, Jun 8, 2018 at 10:27 AM, Eric Xie <[email protected]> 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. > > > > Thanks, > > Eric > > >
