Re: [openstack-dev] [Neutron] Bug deputy process

[Gary Kotton]

From: "Armando M." <arma...@gmail.com<mailto:arma...@gmail.com>>
Reply-To: OpenStack List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Saturday, December 5, 2015 at 1:27 AM
To: OpenStack List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Bug deputy process



On 4 December 2015 at 15:15, Carl Baldwin 
<c...@ecbaldwin.net<mailto:c...@ecbaldwin.net>> wrote:
On Thu, Dec 3, 2015 at 9:29 AM, Kyle Mestery 
<mest...@mestery.com<mailto:mest...@mestery.com>> wrote:
> One concern I have is ensuring we rotate people, because it does take some
> time, and if the same handful of rotate, they will burn out. So I actively
> encourage more people to volunteer, you don't even have to be a Neutron core
> reviewer to do this!

It is about time for me to step up and do a week.  Is there a waiting
list or schedule you can add me to?

No waiting list. We usually find out who wants to volunteer at the irc meeting 
and I update list [1].

Thanks for volunteering.

[1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy

[Gary] Why wait, just add your name to the table :). I Think that we should 
also clean it up and maybe just leave the last two weeks. Armando can write in 
his black book who has done it



Carl

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 4 December 2015 at 15:15, Carl Baldwin  wrote:

> On Thu, Dec 3, 2015 at 9:29 AM, Kyle Mestery  wrote:
> > One concern I have is ensuring we rotate people, because it does take
> some
> > time, and if the same handful of rotate, they will burn out. So I
> actively
> > encourage more people to volunteer, you don't even have to be a Neutron
> core
> > reviewer to do this!
>
> It is about time for me to step up and do a week.  Is there a waiting
> list or schedule you can add me to?
>

No waiting list. We usually find out who wants to volunteer at the irc
meeting and I update list [1].

Thanks for volunteering.

[1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy


>
> Carl
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Carl Baldwin]

On Thu, Dec 3, 2015 at 9:29 AM, Kyle Mestery  wrote:
> One concern I have is ensuring we rotate people, because it does take some
> time, and if the same handful of rotate, they will burn out. So I actively
> encourage more people to volunteer, you don't even have to be a Neutron core
> reviewer to do this!

It is about time for me to step up and do a week.  Is there a waiting
list or schedule you can add me to?

Carl

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Rossella Sblendido]

Hi Armando,

On 12/02/2015 07:49 PM, Armando M. wrote:

Hi neutrinos,

It's been a couple of months that the Bug deputy process has been in
place [1,2]. Since the beginning of Mitaka we have collected the
following statistics (for neutron and neutronclient):

Total bug reports: 373

  * Fix committed: 144
  * Unassigned: 73
  o New: 17
  o Incomplete: 20
  o Confirmed: 27
  o Triaged: 6


At first, it is clear that we do not fix issues nearly as fast as they
come in, but at least we managed to keep the number of
unassigned/unvetted bugs relatively small, so kudos to you all who
participated in this experiment. I don't have data based on older
releases, so I can't see whether we've improved or worsened, and I'd
like to ask for feedback from the people who played with this first
hand, especially on the amount of time that has taken them to do deputy
duty for their assigned week.


my feedback is very positive. I think the new process is good, thanks 
for setting it up! During my week I was looking at newly filed bugs 
every day and triaged them. This took around 1 or 2 hours a day. But it 
was a quiet week...so the load was not super high.


cheers,

Rossella



  * ihrachys
  * regXboi
  * markmcclain
  * mestery
  * mangelajo
  * garyk
  * rossella_s
  * dougwig

Many thanks,
Armando

[1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy
[2]
http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 3 December 2015 at 07:58, Ihar Hrachyshka  wrote:

> Armando M.  wrote:
>
> Hi neutrinos,
>>
>> It's been a couple of months that the Bug deputy process has been in
>> place [1,2]. Since the beginning of Mitaka we have collected the following
>> statistics (for neutron and neutronclient):
>>
>> Total bug reports: 373
>> • Fix committed: 144
>> • Unassigned: 73
>> • New: 17
>> • Incomplete: 20
>> • Confirmed: 27
>> • Triaged: 6
>>
>> At first, it is clear that we do not fix issues nearly as fast as they
>> come in, but at least we managed to keep the number of unassigned/unvetted
>> bugs relatively small, so kudos to you all who participated in this
>> experiment. I don't have data based on older releases, so I can't see
>> whether we've improved or worsened, and I'd like to ask for feedback from
>> the people who played with this first hand, especially on the amount of
>> time that has taken them to do deputy duty for their assigned week.
>> • ihrachys
>> • regXboi
>> • markmcclain
>> • mestery
>> • mangelajo
>> • garyk
>> • rossella_s
>> • dougwig
>>
>
> My perspective, it is a success. We are better at disseminating
> information about ongoing reported issues.
>
> Timewise, it did not waste more than an hour per day for me, usually less.


Thanks not time wasted, is it? :)


> The trick I use is subscribing to all comments in all neutron bugs in LP.
> That way I don’t need to rely on UI to get the list of bugs reported during
> me on duty.
>
> The thing I would like us to see enhanced is making sure that tags set to
> bugs are actively tracked by corresponding teams. Hint: in my case, I have
> some recurrent todo on each Fri to walk thru all ‘oslo’ bugs. I may do the
> same if/once we get ‘upgrade’ tag. It would be great to be able to
> subscribe to just specific tag for emails, but I don’t know whether it’s
> possible in LP.
>

I think the trick is to provide a subscription name, and you can subscribe
just to a single tag. That's how I have the RFE bugs stand out in my pile.

Cheers,
Armando


>
> So kudos for setting the process and thanks everyone involved so far,
>
> Ihar
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 2 December 2015 at 17:38, Sean M. Collins  wrote:

> I was not a deputy - but I had been subscribed to launchpad bugs for
> years, but had a procmail filter set so it went into a folder that prior
> to this new initiative, had remained unread for years. As part of this
> new effort I try and spend at least 15 minutes a day checking the folder
> and working on bugs where I think I can contribute productively.
>
> So - I think it has been effective. It's made me pay attention to it. :)
>

Let's hope you continue to do so, your input is very valuable!


>
> --
> Sean M. Collins
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 3 December 2015 at 01:42, Rossella Sblendido  wrote:

> Hi Armando,
>
> On 12/02/2015 07:49 PM, Armando M. wrote:
>
>> Hi neutrinos,
>>
>> It's been a couple of months that the Bug deputy process has been in
>> place [1,2]. Since the beginning of Mitaka we have collected the
>> following statistics (for neutron and neutronclient):
>>
>> Total bug reports: 373
>>
>>   * Fix committed: 144
>>   * Unassigned: 73
>>   o New: 17
>>   o Incomplete: 20
>>   o Confirmed: 27
>>   o Triaged: 6
>>
>>
>> At first, it is clear that we do not fix issues nearly as fast as they
>> come in, but at least we managed to keep the number of
>> unassigned/unvetted bugs relatively small, so kudos to you all who
>> participated in this experiment. I don't have data based on older
>> releases, so I can't see whether we've improved or worsened, and I'd
>> like to ask for feedback from the people who played with this first
>> hand, especially on the amount of time that has taken them to do deputy
>> duty for their assigned week.
>>
>
> my feedback is very positive. I think the new process is good, thanks for
> setting it up! During my week I was looking at newly filed bugs every day
> and triaged them. This took around 1 or 2 hours a day. But it was a quiet
> week...so the load was not super high.
>

I wonder if the 'needs-attention' tag has been useful as a tool to draw
attention on bugs that have been aging, unassigned and unconfirmed for a
while.


>
> cheers,
>
> Rossella
>
>
>>   * ihrachys
>>   * regXboi
>>   * markmcclain
>>   * mestery
>>   * mangelajo
>>   * garyk
>>   * rossella_s
>>   * dougwig
>>
>> Many thanks,
>> Armando
>>
>> [1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy
>> [2]
>>
>> http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Ihar Hrachyshka]

Armando M.  wrote:


Hi neutrinos,

It's been a couple of months that the Bug deputy process has been in  
place [1,2]. Since the beginning of Mitaka we have collected the  
following statistics (for neutron and neutronclient):


Total bug reports: 373
• Fix committed: 144
• Unassigned: 73
• New: 17
• Incomplete: 20
• Confirmed: 27
• Triaged: 6

At first, it is clear that we do not fix issues nearly as fast as they  
come in, but at least we managed to keep the number of  
unassigned/unvetted bugs relatively small, so kudos to you all who  
participated in this experiment. I don't have data based on older  
releases, so I can't see whether we've improved or worsened, and I'd like  
to ask for feedback from the people who played with this first hand,  
especially on the amount of time that has taken them to do deputy duty  
for their assigned week.

• ihrachys
• regXboi
• markmcclain
• mestery
• mangelajo
• garyk
• rossella_s
• dougwig


My perspective, it is a success. We are better at disseminating information  
about ongoing reported issues.


Timewise, it did not waste more than an hour per day for me, usually less.  
The trick I use is subscribing to all comments in all neutron bugs in LP.  
That way I don’t need to rely on UI to get the list of bugs reported during  
me on duty.


The thing I would like us to see enhanced is making sure that tags set to  
bugs are actively tracked by corresponding teams. Hint: in my case, I have  
some recurrent todo on each Fri to walk thru all ‘oslo’ bugs. I may do the  
same if/once we get ‘upgrade’ tag. It would be great to be able to  
subscribe to just specific tag for emails, but I don’t know whether it’s  
possible in LP.


So kudos for setting the process and thanks everyone involved so far,

Ihar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 2 December 2015 at 11:02, Salvatore Orlando 
wrote:

> I only have some historical, anecdotal, and rapidly waning memory of
> previous releases.
> Nevertheless my feeling is that the process has been a success so far.
> In past times it would not have been a surprise if a bug fell under the
> radar until that well known brownish matter hit the proverbial fan.
>
> Also, only 17 bugs are in "new" status out of 373. Which means that - at
> worst - only 4.6% of reported bugs have not yet been analysed by the team.
> I reckon these numbers are rather impressive. Kudos to both the deputies
> and most importantly to Armando who set up the process.
>

Do I hear that you would like to be deputy for one of the forthcoming
weeks? :)


>
> Salvatore
>
>
> On 2 December 2015 at 19:49, Armando M.  wrote:
>
>> Hi neutrinos,
>>
>> It's been a couple of months that the Bug deputy process has been in
>> place [1,2]. Since the beginning of Mitaka we have collected the following
>> statistics (for neutron and neutronclient):
>>
>> Total bug reports: 373
>>
>>- Fix committed: 144
>>- Unassigned: 73
>>   - New: 17
>>   - Incomplete: 20
>>   - Confirmed: 27
>>   - Triaged: 6
>>
>>
>> At first, it is clear that we do not fix issues nearly as fast as they
>> come in, but at least we managed to keep the number of unassigned/unvetted
>> bugs relatively small, so kudos to you all who participated in this
>> experiment. I don't have data based on older releases, so I can't see
>> whether we've improved or worsened, and I'd like to ask for feedback from
>> the people who played with this first hand, especially on the amount of
>> time that has taken them to do deputy duty for their assigned week.
>>
>>- ihrachys
>>- regXboi
>>- markmcclain
>>- mestery
>>- mangelajo
>>- garyk
>>- rossella_s
>>- dougwig
>>
>> Many thanks,
>> Armando
>>
>> [1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy
>> [2]
>> http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Sean M. Collins]

On Thu, Dec 03, 2015 at 10:58:07AM EST, Ihar Hrachyshka wrote:
> The thing I would like us to see enhanced is making sure that tags set to
> bugs are actively tracked by corresponding teams. 

Thanks - you just reminded me to tag two bugs that I had just touched.
:)

-- 
Sean M. Collins

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 3 December 2015 at 10:48, Johnston, Nate  wrote:

> I second that - I don’t have the ability to triage a bug.  But I would be
> happy to take a watch if I could.
>

Anyone has the ability to triage bugs, but some don't have full privileges
(like assigning milestones, owner or severity) as they do not belong to the
bugs team [1]; that shouldn't stop you from commenting, adding tags etc.

This team is moderated, and if you want to be more involved, show some good
judgement call, volunteer to be a deputy and we can only be happy for you
to be part of the family :)


[1] https://launchpad.net/~neutron-bugs/

>
> —N.
>
> > On Dec 3, 2015, at 1:42 PM, Smigiel, Dariusz 
> wrote:
> >
> >> From: Kyle Mestery [mailto:mest...@mestery.com]
> > [...]
> >> One concern I have is ensuring we rotate people, because it does take
> some time, and if the same handful of rotate, they will burn out. So I
> actively encourage more people to volunteer, you don't even have to be a
> Neutron core reviewer to do this!
> >
> > Kyle, didn't know that not only core reviewers can do deputy. I thought
> that only selected group of users have an access to bug triaging.
> > Another thing, probably the best users who know how bug is complicated
> or important, are cores.
> >
> > If you have any tips or tricks to do proper deputy, I'm in.
> >
> >> Thanks!
> >> Kyle
> >
> > Thanks, Darek Smigiel (dasm)
> > ITP
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Sean M. Collins]

> One concern I have is ensuring we rotate people, because it does take some
> time, and if the same handful of rotate, they will burn out. So I actively
> encourage more people to volunteer, you don't even have to be a Neutron
> core reviewer to do this!

I actually didn't realize that it didn't require being a core reviewer.
I pushed a patch to our policy docs to help clarify that

https://review.openstack.org/253164

-- 
Sean M. Collins

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Miguel Angel Ajo]

I can only agree with the opinions others already expressed. It’s been a very 
good initiative. Going through the bugs everyday during my week opened my eyes 
to how the end users face bugs, an the kind of issues we have.

I got myself educated into following the incoming bug stream from launchpad 
into my email every time I can, I keep doing it, but as Sean said, only jumping 
for investigation on the pieces of the system I know better.

I encourage others to do it, and I will be happy to do it again when we need it.

Best,
Miguel Ángel Ajo


On Thursday 3 December 2015 at 19:48, Johnston, Nate wrote:

> I second that - I don’t have the ability to triage a bug. But I would be 
> happy to take a watch if I could.
>  
> —N.
>  
> > On Dec 3, 2015, at 1:42 PM, Smigiel, Dariusz  > (mailto:dariusz.smig...@intel.com)> wrote:
> >  
> > > From: Kyle Mestery [mailto:mest...@mestery.com]  
> > [...]
> > > One concern I have is ensuring we rotate people, because it does take 
> > > some time, and if the same handful of rotate, they will burn out. So I 
> > > actively encourage more people to volunteer, you don't even have to be a 
> > > Neutron core reviewer to do this!
> >  
> >  
> > Kyle, didn't know that not only core reviewers can do deputy. I thought 
> > that only selected group of users have an access to bug triaging.
> > Another thing, probably the best users who know how bug is complicated or 
> > important, are cores.
> >  
> > If you have any tips or tricks to do proper deputy, I'm in.
> >  
> > > Thanks!
> > > Kyle
> > >  
> >  
> >  
> > Thanks, Darek Smigiel (dasm)
> > ITP
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> > (mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe)
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >  
>  
>  
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> (mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe)
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>  
>  


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 3 December 2015 at 10:42, Smigiel, Dariusz 
wrote:

> > From: Kyle Mestery [mailto:mest...@mestery.com]
> [...]
> > One concern I have is ensuring we rotate people, because it does take
> some time, and if the same handful of rotate, they will burn out. So I
> actively encourage more people to volunteer, you don't even have to be a
> Neutron core reviewer to do this!
>
> Kyle, didn't know that not only core reviewers can do deputy. I thought
> that only selected group of users have an access to bug triaging.
> Another thing, probably the best users who know how bug is complicated or
> important, are cores.
>
> If you have any tips or tricks to do proper deputy, I'm in.
>

It's all black and white here:

http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy


Bug triaging is a great way to get familiar with the system and grow into a
more important role.

Have fun!


> > Thanks!
> > Kyle
>
> Thanks, Darek Smigiel (dasm)
> ITP
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Ryan Moats]

I missed this the first time around, but I concur with the comments of the
other deputies -
the effort only took me about an hour or two a day and I think it's been
rather helpful :)

Ryan Moats (regXboi)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Armando M.]

On 3 December 2015 at 14:20, Ryan Moats  wrote:

> I missed this the first time around, but I concur with the comments of the
> other deputies -
> the effort only took me about an hour or two a day and I think it's been
> rather helpful :)
>

Btw, have a look at [1,2] to see if that suits your subscription needs:
whether you want to monitor all changes or a subset of it.

Cheers,
Armando

[1] https://bugs.launchpad.net/neutron/+subscriptions
[2] https://bugs.launchpad.net/python-neutronclient/+subscriptions

>
>
> Ryan Moats (regXboi)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Doug Wiegley]

Roughly an hour a day, and super useful. I’d echo that anyone can volunteer, 
since a lot of the job is reaching out to various folks for input 
(docs/policies/neutron-teams.rst is the map of truth.)

I found a lot of bugs that I care about in the pre-mitaka backlog, that I 
didn’t know existed. This has been an education process for me, and I’ve been 
trying to triage one pre-mitaka bug for every mitaka one.

A rotating RFE deputy from the drivers team might also be useful, so the first 
pass isn’t always the drivers meeting. I tend to pay attention more when it’s 
my “assigned” turn. I shouldn’t, but I do.

Thanks,
doug



> On Dec 3, 2015, at 9:29 AM, Kyle Mestery  wrote:
> 
> On Wed, Dec 2, 2015 at 10:49 AM, Armando M.  > wrote:
> Hi neutrinos,
> 
> It's been a couple of months that the Bug deputy process has been in place 
> [1,2]. Since the beginning of Mitaka we have collected the following 
> statistics (for neutron and neutronclient):
> 
> Total bug reports: 373
> Fix committed: 144
> Unassigned: 73
> New: 17
> Incomplete: 20
> Confirmed: 27
> Triaged: 6
> 
> At first, it is clear that we do not fix issues nearly as fast as they come 
> in, but at least we managed to keep the number of unassigned/unvetted bugs 
> relatively small, so kudos to you all who participated in this experiment. I 
> don't have data based on older releases, so I can't see whether we've 
> improved or worsened, and I'd like to ask for feedback from the people who 
> played with this first hand, especially on the amount of time that has taken 
> them to do deputy duty for their assigned week.
> ihrachys
> regXboi
> markmcclain
> mestery
> mangelajo
> garyk
> rossella_s
> dougwig
> Many thanks,
> Armando
> 
> 
> I've found the process to be super useful. I found that by volunteering to be 
> the bug deputy it forced me to spend about an hour a day going through 
> incoming bugs. But the result is faster triage, and I was able to point some 
> bugs directly at people for quick resolution. Thanks for driving this 
> important initiative!
> 
> One concern I have is ensuring we rotate people, because it does take some 
> time, and if the same handful of rotate, they will burn out. So I actively 
> encourage more people to volunteer, you don't even have to be a Neutron core 
> reviewer to do this!
> 
> Thanks!
> Kyle
>  
> [1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy 
> 
> [2] 
> http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy
>  
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org 
> ?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Smigiel, Dariusz]

> From: Kyle Mestery [mailto:mest...@mestery.com] 
[...]
> One concern I have is ensuring we rotate people, because it does take some 
> time, and if the same handful of rotate, they will burn out. So I actively 
> encourage more people to volunteer, you don't even have to be a Neutron core 
> reviewer to do this!

Kyle, didn't know that not only core reviewers can do deputy. I thought that 
only selected group of users have an access to bug triaging.
Another thing, probably the best users who know how bug is complicated or 
important, are cores.

If you have any tips or tricks to do proper deputy, I'm in.

> Thanks!
> Kyle

Thanks, Darek Smigiel (dasm)
ITP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Johnston, Nate]

I second that - I don’t have the ability to triage a bug.  But I would be happy 
to take a watch if I could.

—N.

> On Dec 3, 2015, at 1:42 PM, Smigiel, Dariusz  
> wrote:
> 
>> From: Kyle Mestery [mailto:mest...@mestery.com] 
> [...]
>> One concern I have is ensuring we rotate people, because it does take some 
>> time, and if the same handful of rotate, they will burn out. So I actively 
>> encourage more people to volunteer, you don't even have to be a Neutron core 
>> reviewer to do this!
> 
> Kyle, didn't know that not only core reviewers can do deputy. I thought that 
> only selected group of users have an access to bug triaging.
> Another thing, probably the best users who know how bug is complicated or 
> important, are cores.
> 
> If you have any tips or tricks to do proper deputy, I'm in.
> 
>> Thanks!
>> Kyle
> 
> Thanks, Darek Smigiel (dasm)
> ITP
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Salvatore Orlando]

I only have some historical, anecdotal, and rapidly waning memory of
previous releases.
Nevertheless my feeling is that the process has been a success so far.
In past times it would not have been a surprise if a bug fell under the
radar until that well known brownish matter hit the proverbial fan.

Also, only 17 bugs are in "new" status out of 373. Which means that - at
worst - only 4.6% of reported bugs have not yet been analysed by the team.
I reckon these numbers are rather impressive. Kudos to both the deputies
and most importantly to Armando who set up the process.

Salvatore


On 2 December 2015 at 19:49, Armando M.  wrote:

> Hi neutrinos,
>
> It's been a couple of months that the Bug deputy process has been in place
> [1,2]. Since the beginning of Mitaka we have collected the following
> statistics (for neutron and neutronclient):
>
> Total bug reports: 373
>
>- Fix committed: 144
>- Unassigned: 73
>   - New: 17
>   - Incomplete: 20
>   - Confirmed: 27
>   - Triaged: 6
>
>
> At first, it is clear that we do not fix issues nearly as fast as they
> come in, but at least we managed to keep the number of unassigned/unvetted
> bugs relatively small, so kudos to you all who participated in this
> experiment. I don't have data based on older releases, so I can't see
> whether we've improved or worsened, and I'd like to ask for feedback from
> the people who played with this first hand, especially on the amount of
> time that has taken them to do deputy duty for their assigned week.
>
>- ihrachys
>- regXboi
>- markmcclain
>- mestery
>- mangelajo
>- garyk
>- rossella_s
>- dougwig
>
> Many thanks,
> Armando
>
> [1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy
> [2]
> http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron] Bug deputy process

[Armando M.]

Hi neutrinos,

It's been a couple of months that the Bug deputy process has been in place
[1,2]. Since the beginning of Mitaka we have collected the following
statistics (for neutron and neutronclient):

Total bug reports: 373

   - Fix committed: 144
   - Unassigned: 73
  - New: 17
  - Incomplete: 20
  - Confirmed: 27
  - Triaged: 6


At first, it is clear that we do not fix issues nearly as fast as they come
in, but at least we managed to keep the number of unassigned/unvetted bugs
relatively small, so kudos to you all who participated in this experiment.
I don't have data based on older releases, so I can't see whether we've
improved or worsened, and I'd like to ask for feedback from the people who
played with this first hand, especially on the amount of time that has
taken them to do deputy duty for their assigned week.

   - ihrachys
   - regXboi
   - markmcclain
   - mestery
   - mangelajo
   - garyk
   - rossella_s
   - dougwig

Many thanks,
Armando

[1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy
[2]
http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Bug deputy process

[Sean M. Collins]

I was not a deputy - but I had been subscribed to launchpad bugs for
years, but had a procmail filter set so it went into a folder that prior
to this new initiative, had remained unread for years. As part of this
new effort I try and spend at least 15 minutes a day checking the folder
and working on bugs where I think I can contribute productively. 

So - I think it has been effective. It's made me pay attention to it. :)

-- 
Sean M. Collins

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev