Leave it the way it was. Sent from my iPhone
> On Sep 19, 2013, at 8:49 AM, Joe Bowser <bows...@gmail.com> wrote: > > On second thought, I don't know if I like this proposal. > > Right now, everything Android gets assigned to me. Most people don't > think I'm a real person when this stuff gets assigned, or they > instantly hate me because I spend my time triaging the bugs as they > come in. We do need someone to go through, read these issues, close > the poorly written ones that have duplicates (i.e. Everything to do > with WebSQL that's not written by Peter, ironically). This chews up a > lot of my time. > > What WOULD be good is if people would be more aggressive with the JIRA > issues. Even if you don't have time to fix the issue, just pinging > people and letting them know that we haven't forgot about them goes a > long way. I think that leaving everything unassigned is going to make > it look like we're abandoning Cordova, which isn't the case. > > That being said, we should rotate who handles the firehose. > >> On Thu, Sep 19, 2013 at 8:36 AM, purplecabbage <purplecabb...@gmail.com> >> wrote: >> 12 hours? >> I think we have to wait longer before moving on a proposal. >> >> Sent from my iPhone >> >>> On Sep 19, 2013, at 7:29 AM, Andrew Grieve <agri...@chromium.org> wrote: >>> >>> Okay, I've made the change. Let's try it out :) >>> >>> I think start/stop is good if you've actually started working on something, >>> but it's different from "this new bug has been looked at by someone". >>> >>> >>> >>> >>>> On Thu, Sep 19, 2013 at 2:51 AM, Anis KADRI <anis.ka...@gmail.com> wrote: >>>> >>>> What about the start/stop progress? >>>> >>>> On Wed, Sep 18, 2013 at 9:03 PM, Ian Clelland <iclell...@chromium.org> >>>> wrote: >>>>> +1 >>>>> >>>>> Also, if you are a component "owner", it's pretty simple in JIRA to add a >>>>> dashboard widget that shows you all unassigned bugs in your component. >>>>> >>>>> Ian >>>>> >>>>> >>>>>> On Wed, Sep 18, 2013 at 11:49 PM, Joe Bowser <bows...@gmail.com> wrote: >>>>>> >>>>>> +1 >>>>
