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 <bhavintha...@gmail.com> wrote: > +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 working on > what. > > Bhavin Thaker. > > On Mon, Sep 11, 2017 at 5:06 AM Joern Kottmann <kottm...@gmail.com> wrote: > > > 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 Jira issue. > > > > My opinion is that Jira does much more then we actually use/need, and > > is sometimes slightly unresponsive (e.g. takes 1 or 2 seconds to load > > a new page) on the other hand, the GitHub issue tracker ist too simple > > and is missing a few useful features. > > > > Jörn > > > > On Mon, Sep 11, 2017 at 10:18 AM, Henri Yandell <bay...@apache.org> > wrote: > > > 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 do that could be to put > > the > > > new features in JIRA, while keeping GitHub for bug reports, not sure if > > > that's what you were getting to Chris with the question. > > > > > > Hen > > > > > > > > > On Sun, Sep 10, 2017 at 9:23 PM, sandeep krishnamurthy < > > > sandeep.krishn...@gmail.com> wrote: > > > > > >> +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 ready to contribute a feature or bug fix. > > >> 4. A community member actively proposing and driving a big new feature > > for > > >> the project. > > >> > > >> Projects in Github, Tagging Github issues with Call for Contributions > > may > > >> seem very straight forward approach. But, is there any other > > suggestions or > > >> standard practice to drive such efforts? > > >> > > >> This will go a long way in keeping community members informed about > what > > >> next in the project, how can they be part and how they can set future > > >> directions in the project. Also, saving the time and effort in > > duplication > > >> of efforts. > > >> > > >> Regards, > > >> Sandeep > > >> > > >> On Sat, Sep 9, 2017 at 4:48 AM, Chris Olivier <cjolivie...@gmail.com> > > >> wrote: > > >> > > >> > 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 > > >> was > > >> > working on it already? Or coordinate forces (so to speak) on a > large > > >> > feature or initiative? > > >> > > > >> > -Chris > > >> > > > >> > > >> > > >> > > >> -- > > >> Sandeep Krishnamurthy > > >> > > >
