Re: Jira and/or feature collision

2017-09-12 Thread Naveen Swamy
+1 for using Apache JIRA to track MXNet projects. On Mon, Sep 11, 2017 at 11:01 AM, Chris Olivier wrote: > Are there any objections to using the Apache JIRA for mxnet development > tracking? If not, how do we get it set up? > > On Mon, Sep 11, 2017 at 8:32 AM, Suneel Marthi wrote: > > > I am n

Re: Jira and/or feature collision

2017-09-11 Thread Chris Olivier
Are there any objections to using the Apache JIRA for mxnet development tracking? If not, how do we get it set up? On Mon, Sep 11, 2017 at 8:32 AM, Suneel Marthi wrote: > I am not following, wouldn't a jira be assigned to the guy working on it - > so where is the question of multiple folks work

Re: Jira and/or feature collision

2017-09-11 Thread Chris Olivier
Yes, kind of -- trying to manage new features (both ideas for, WIP, etc) in the sea of github "issues" oesn't seem like it scales very well. In fact, I've tried perusing them and it's difficult. On Mon, Sep 11, 2017 at 1:18 AM, Henri Yandell wrote: > Yes, Apache JIRA is free to use. > > My obse

Re: Jira and/or feature collision

2017-09-11 Thread Bhavin Thaker
Hi Suneel: MXNet does not use Jira currently and hence the question. On Mon, Sep 11, 2017 at 8:32 AM Suneel Marthi wrote: > I am not following, wouldn't a jira be assigned to the guy working on it - > so where is the question of multiple folks working on one feature > > On Mon, Sep 11, 2017 at 5

Re: Jira and/or feature collision

2017-09-11 Thread Suneel Marthi
I am not following, wouldn't a jira be assigned to the guy working on it - so where is the question of multiple folks working on one feature On Mon, Sep 11, 2017 at 5:30 PM, Bhavin Thaker wrote: > +1 : Chris has an important question. > > How do we ensure that a feature/task for a particular Apa

Re: Jira and/or feature collision

2017-09-11 Thread Bhavin Thaker
+1 : Chris has an important question. How do we ensure that a feature/task for a particular Apache project is not worked on by multiple folks at the same time? Is there a recommendation for a tool/process from the Apache group? This also provides a central, consolidated place to know who is work

Re: Jira and/or feature collision

2017-09-11 Thread Joern Kottmann
A good way to coordinate is to use the dev list and/or state on the issues that you are interested in it and are working on it. We use Jira for years at Apache OpenNLP for all the issues we deal with. At GitHub we use the Pull Request feature and synchronize all comments with the corresponding Jir

Re: Jira and/or feature collision

2017-09-11 Thread Henri Yandell
Yes, Apache JIRA is free to use. My observations of GitHub are that roadmaps/wishlist features need better separation from bug reports. Ideally you want a nice big list of ideas for future work, and a list of bug reports and smaller contributions that you're always driving down to zero. One way to

Re: Jira and/or feature collision

2017-09-10 Thread sandeep krishnamurthy
+1 Thanks Chris for bringing up this important topic. I would really like to prioritize this topic and request users and mentors to come up a process or suggestions on how to: 1. Request for contributions from the community. 2. A community member raising feature requests. 3. A community member rea

Jira and/or feature collision

2017-09-09 Thread Chris Olivier
Is Apache JIRA free to use? What do most projects use? While it's natural that some companies have internal priorities which drive their development plans, how do other Apache projects avoid having the same feature developed independently by more than one party, because they isn't know the other wa