Hi, I am not a big fan of JIRA either. But I would like to raise this issue of committing to a decision after a VOTE has passed. I saw in PRs that there was a disregard for JIRA and ignoring requests on PRs to link to JIRA. Because of this, JIRA was not given a fair chance to be tried out as a project management tool and eventually hardly being used. If we don't work on this as a community, VOTEs also tend to loose their meaning.
Anirudh On Fri, Jun 8, 2018 at 11:00 AM, Eric Xie <[email protected]> wrote: > I think the number of issues become less of a problem if we label them > timely, which is already improving. > > Thanks, > Eric > > On 2018/06/08 17:55:28, Tianqi Chen <[email protected]> wrote: > > I would suggest we have a separate discussion issue about transparency. > > First of all, I agree that transparency is important. > > > > This can be achieved by public roadmaps, RFCs, that do not have > > particularly tie to JIRA or github issues. Having a clear guideline on > that > > would be great, and it is great to see more RFCs in the dev list. > > > > In terms of issues themselves, I think one problem we are facing is > > overflowing amount of issues. One way to minimize this would be to > redirect > > more questions to forums, and only keep issues that are actionable and > > encourage the committers who opens the issue to fix them timely. > > > > Tianqi > > > > 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 > > > > > > > > > >
