Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Markus Zoeller]

Nova needs another volunteer for the weekly "bug skimming duty".
Please add your name(s) to the wiki [1] or mention it on the Nova
team IRC meeting on Thursday. If there are questions during your
duty you can ping me every time in IRC (I'm in UTC+1).

Thanks to cihand, auggy and rpodolyaka for their work in the last
2 weeks!

References:
[1] 
https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty

Regards, Markus Zoeller (markus_z)


Markus Zoeller/Germany/IBM@IBMDE wrote on 01/07/2016 12:06:31 PM:
> From: Markus Zoeller/Germany/IBM@IBMDE
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 01/07/2016 12:07 PM
> Subject: [openstack-dev] [nova][bugs] help needed: volunteers for bug 
> skimming (1 week)
> 
> The bug triage is an important first step to improve the quality
> of Nova. Every code contributor should be aware of it and can 
> contribute without any special permissions [1]. We need more 
> volunteers to do this. If you want to be one of them for 1 week, 
> raise your hand in this thread or add your name in the wiki [2]. 
> At best we will have at least 1 person until today's Nova meeting 
> at 21:00 UTC [3]. When you volunteer, I will be available in IRC 
> for requests, too.
> 
> Regards, Markus Zoeller (markus_z)
> 
> References:
> [1] 
> 
https://wiki.openstack.org/wikiBugTriage#Task_1:_Confirm_new_bugs_.28anyone.29

> [2] 
> https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
> [3] https://wiki.openstack.org/wiki/Meetings/Nova
> 
> 
> 
__
> 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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Fahri Cihan Demirci]

On Mon, Jan 11, 2016 at 11:21:29AM +0100, Markus Zoeller wrote:
> Augustina Ragwitz <aragw...@pobox.com> wrote on 01/08/2016 07:50:23 PM:
> 
> > From: Augustina Ragwitz <aragw...@pobox.com>
> > To: "OpenStack Development Mailing List (not for usage questions)" 
> > <openstack-dev@lists.openstack.org>
> > Date: 01/08/2016 08:00 PM
> > Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers for 
> > bug skimming (1 week)
> > 
> > I signed up for the week before the Nova Midcycle meeting. Even though 
> > I'm still new, I feel capable of at least getting the tags mostly right. 
> 
> > When I'm not quite sure which tag it would fall under, I search for 
> > similar bugs and see how they were tagged.
> 
> Thanks for signing up! 
> That's a valid approach.
> 
> > I did have one clarifying question, what exactly are the expectations of 
> 
> > the bug skimming duty? I assumed it was just tagging bugs to get them 
> > into the appropriate queues for triaging. Do we also need to confirm the 
> 
> > bugs once they've been tagged or does that fall under "triage" and not 
> > "skimming"?
> > 
> > Thanks!
> > Augustina
> 
> In short, do as much as possible before the expertise of the subteams
> is needed. Also, if you spot potential critical bugs, shout out in the 
> #openstack-nova channel (for me or one of the core reviewers [1]).
> 
> As a longer clarification, the duty includes:
> * Switch the bug to "incomplete" when crucial information is missing
>   and ask the reporter to provide more information. This includes:
> * steps to reproduce
> * the version of Nova and the novaclient (or os-client)
> * logs (on debug level)
> * environment details depending on the bug
> * libvirt/kvm versions, VMWare version, ...
> * storage type (ceph, LVM, GPFS, ...) 
> * network type (nova-network or neutron)
>   I subscribe myself to bugs when I switch them to "incomplete" to see
>   when responses come in. See "You are not directly subscribed to this 
>   bug's notifications." on the right hand side of a Launchpad bug report.
> * Close as "invalid" if it is a support request or feature request.
> * Switch to "confirm" if you could reproduce the described issue. This
>   is not always possible for you because of missing resources like a 
>   ceph storage or something like that. 
> * Add a tag (or more tags) if the report allows you to narrow down the
>   area which potentially contains the issue. This should be the entry
>   point for subteams to dig deeper to find the root cause and potential
>   solutions.
> * Bring critical bugs to the attention of the other contributors. The
>   #openstack-nova channel and/or a ML post is useful.
> 
> I usually explained in a comment *why* I changed a status and which
> next steps I expect from whom. For example, if I switch to "incomplete",
> tell the reporter to add this and that piece of information and to switch
> the bug back to "new" when the reporter has done this. Another example, 
> if it was a feature request, I switched to "invalid" and added the links
> to the blueprint process.
> 
> I used the term "skimming" because each day there are new bugs where
> nobody took a look at. They "float" on top of all the other bug reports 
> which should have been looked at before. 
> 
> I see the whole process in 3 levels:
> * level 1: bug skimming duty => keep the input sane, prepares the
>report for level 2
> * level 2: subteam digs deeper, finds the issue, proposes solution 
>ideas for level 3
> * level 3: contributor provides a change in gerrit based on level 2
> 
> Does this clarify some of the open questions?

Thank you for these guidelines. Regarding reports which may be considered as 
feature requests; there are some reports which were in that vein and were 
marked with 'Wishlist' importance. Therefore I assumed that classifying feature 
requests as wishlist items was a valid approach. Was that wrong? Should marking 
those types of reports as 'Invalid' be the way to go? Thank you.

Best regards,

Fahri Cihan Demirci

> 
> References:
> [1] Nova core reviewers list:
> https://review.openstack.org/#/admin/groups/25,members
> 
> Regards, Markus Zoeller (markus_z)
> 
> 
> 
> __
> 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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Markus Zoeller]

Fahri Cihan Demirci <cih...@skyatlas.com> wrote on 01/12/2016 09:58:10 AM:

> From: Fahri Cihan Demirci <cih...@skyatlas.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 01/12/2016 10:01 AM
> Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers for 
> bug skimming (1 week)
> 
> On Mon, Jan 11, 2016 at 11:21:29AM +0100, Markus Zoeller wrote:
> > Augustina Ragwitz <aragw...@pobox.com> wrote on 01/08/2016 07:50:23 
PM:
> > 
> > > From: Augustina Ragwitz <aragw...@pobox.com>
> > > To: "OpenStack Development Mailing List (not for usage questions)" 
> > > <openstack-dev@lists.openstack.org>
> > > Date: 01/08/2016 08:00 PM
> > > Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers 
for 
> > > bug skimming (1 week)
> > > 
> > > I signed up for the week before the Nova Midcycle meeting. Even 
though 
> > > I'm still new, I feel capable of at least getting the tags mostly 
right. 
> > 
> > > When I'm not quite sure which tag it would fall under, I search for 
> > > similar bugs and see how they were tagged.
> > 
> > Thanks for signing up! 
> > That's a valid approach.
> > 
> > > I did have one clarifying question, what exactly are the 
expectations of 
> > 
> > > the bug skimming duty? I assumed it was just tagging bugs to get 
them 
> > > into the appropriate queues for triaging. Do we also need to confirm 
the 
> > 
> > > bugs once they've been tagged or does that fall under "triage" and 
not 
> > > "skimming"?
> > > 
> > > Thanks!
> > > Augustina
> > 
> > In short, do as much as possible before the expertise of the subteams
> > is needed. Also, if you spot potential critical bugs, shout out in the 

> > #openstack-nova channel (for me or one of the core reviewers [1]).
> > 
> > As a longer clarification, the duty includes:
> > * Switch the bug to "incomplete" when crucial information is missing
> >   and ask the reporter to provide more information. This includes:
> > * steps to reproduce
> > * the version of Nova and the novaclient (or os-client)
> > * logs (on debug level)
> > * environment details depending on the bug
> > * libvirt/kvm versions, VMWare version, ...
> > * storage type (ceph, LVM, GPFS, ...) 
> > * network type (nova-network or neutron)
> >   I subscribe myself to bugs when I switch them to "incomplete" to see
> >   when responses come in. See "You are not directly subscribed to this 

> >   bug's notifications." on the right hand side of a Launchpad bug 
report.
> > * Close as "invalid" if it is a support request or feature request.
> > * Switch to "confirm" if you could reproduce the described issue. This
> >   is not always possible for you because of missing resources like a 
> >   ceph storage or something like that. 
> > * Add a tag (or more tags) if the report allows you to narrow down the
> >   area which potentially contains the issue. This should be the entry
> >   point for subteams to dig deeper to find the root cause and 
potential
> >   solutions.
> > * Bring critical bugs to the attention of the other contributors. The
> >   #openstack-nova channel and/or a ML post is useful.
> > 
> > I usually explained in a comment *why* I changed a status and which
> > next steps I expect from whom. For example, if I switch to 
"incomplete",
> > tell the reporter to add this and that piece of information and to 
switch
> > the bug back to "new" when the reporter has done this. Another 
example, 
> > if it was a feature request, I switched to "invalid" and added the 
links
> > to the blueprint process.
> > 
> > I used the term "skimming" because each day there are new bugs where
> > nobody took a look at. They "float" on top of all the other bug 
reports 
> > which should have been looked at before. 
> > 
> > I see the whole process in 3 levels:
> > * level 1: bug skimming duty => keep the input sane, prepares the
> >report for level 2
> > * level 2: subteam digs deeper, finds the issue, proposes solution 
> >ideas for level 3
> > * level 3: contributor provides a change in gerrit based on level 2
> > 
> > Does this clarify some of the open questions?
> 
> Thank you for these guidelines. Regarding reports which may be 
> 

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Fahri Cihan Demirci]

On Tue, Jan 12, 2016 at 06:39:22PM +0100, Markus Zoeller wrote:
> Fahri Cihan Demirci <cih...@skyatlas.com> wrote on 01/12/2016 09:58:10 AM:
> 
> > From: Fahri Cihan Demirci <cih...@skyatlas.com>
> > To: "OpenStack Development Mailing List (not for usage questions)" 
> > <openstack-dev@lists.openstack.org>
> > Date: 01/12/2016 10:01 AM
> > Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers for 
> > bug skimming (1 week)
> > 
> > On Mon, Jan 11, 2016 at 11:21:29AM +0100, Markus Zoeller wrote:
> > > Augustina Ragwitz <aragw...@pobox.com> wrote on 01/08/2016 07:50:23 
> PM:
> > > 
> > > [... snipped for easier viewing ...]
> > > 
> > > Does this clarify some of the open questions?
> > 
> > Thank you for these guidelines. Regarding reports which may be 
> > considered as feature requests; there are some reports which were in 
> > that vein and were marked with 'Wishlist' importance. Therefore I 
> > assumed that classifying feature requests as wishlist items was a 
> > valid approach. Was that wrong? Should marking those types of reports 
> > as 'Invalid' be the way to go? Thank you.
> 
> Nova is too complex to specify a new feature in a few sentences in
> a bug report. I tend to close those as "invalid" with links to the
> blueprint process. The (WIP) proposal [1]  I have pushed today also
> wants to omit the usage of the "wishlist" prio but there is not yet
> concensus about it.

Ok, understood, thank you. For what it's worth, the draft already does a good 
job of summarizing the bug skimming proccess for someone not familiar with the 
workflow.

> 
> [1] https://review.openstack.org/#/c/266453/
> 
> Regards, Markus Zoeller (markus_z)
> 
> > Best regards,
> > 
> > Fahri Cihan Demirci
> > 
> > > 
> > > References:
> > > [1] Nova core reviewers list:
> > > https://review.openstack.org/#/admin/groups/25,members
> > > 
> > > Regards, Markus Zoeller (markus_z)
> 
> 
> 
> 
> __
> 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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Markus Zoeller]

Augustina Ragwitz <aragw...@pobox.com> wrote on 01/08/2016 07:50:23 PM:

> From: Augustina Ragwitz <aragw...@pobox.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 01/08/2016 08:00 PM
> Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers for 
> bug skimming (1 week)
> 
> I signed up for the week before the Nova Midcycle meeting. Even though 
> I'm still new, I feel capable of at least getting the tags mostly right. 

> When I'm not quite sure which tag it would fall under, I search for 
> similar bugs and see how they were tagged.

Thanks for signing up! 
That's a valid approach.

> I did have one clarifying question, what exactly are the expectations of 

> the bug skimming duty? I assumed it was just tagging bugs to get them 
> into the appropriate queues for triaging. Do we also need to confirm the 

> bugs once they've been tagged or does that fall under "triage" and not 
> "skimming"?
> 
> Thanks!
> Augustina

In short, do as much as possible before the expertise of the subteams
is needed. Also, if you spot potential critical bugs, shout out in the 
#openstack-nova channel (for me or one of the core reviewers [1]).

As a longer clarification, the duty includes:
* Switch the bug to "incomplete" when crucial information is missing
  and ask the reporter to provide more information. This includes:
* steps to reproduce
* the version of Nova and the novaclient (or os-client)
* logs (on debug level)
* environment details depending on the bug
* libvirt/kvm versions, VMWare version, ...
* storage type (ceph, LVM, GPFS, ...) 
* network type (nova-network or neutron)
  I subscribe myself to bugs when I switch them to "incomplete" to see
  when responses come in. See "You are not directly subscribed to this 
  bug's notifications." on the right hand side of a Launchpad bug report.
* Close as "invalid" if it is a support request or feature request.
* Switch to "confirm" if you could reproduce the described issue. This
  is not always possible for you because of missing resources like a 
  ceph storage or something like that. 
* Add a tag (or more tags) if the report allows you to narrow down the
  area which potentially contains the issue. This should be the entry
  point for subteams to dig deeper to find the root cause and potential
  solutions.
* Bring critical bugs to the attention of the other contributors. The
  #openstack-nova channel and/or a ML post is useful.

I usually explained in a comment *why* I changed a status and which
next steps I expect from whom. For example, if I switch to "incomplete",
tell the reporter to add this and that piece of information and to switch
the bug back to "new" when the reporter has done this. Another example, 
if it was a feature request, I switched to "invalid" and added the links
to the blueprint process.

I used the term "skimming" because each day there are new bugs where
nobody took a look at. They "float" on top of all the other bug reports 
which should have been looked at before. 

I see the whole process in 3 levels:
* level 1: bug skimming duty => keep the input sane, prepares the
   report for level 2
* level 2: subteam digs deeper, finds the issue, proposes solution 
   ideas for level 3
* level 3: contributor provides a change in gerrit based on level 2

Does this clarify some of the open questions?

References:
[1] Nova core reviewers list:
https://review.openstack.org/#/admin/groups/25,members

Regards, Markus Zoeller (markus_z)



__
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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Augustina Ragwitz]

I signed up for the week before the Nova Midcycle meeting. Even though 
I'm still new, I feel capable of at least getting the tags mostly right. 
When I'm not quite sure which tag it would fall under, I search for 
similar bugs and see how they were tagged.


I did have one clarifying question, what exactly are the expectations of 
the bug skimming duty? I assumed it was just tagging bugs to get them 
into the appropriate queues for triaging. Do we also need to confirm the 
bugs once they've been tagged or does that fall under "triage" and not 
"skimming"?


Thanks!
Augustina

__
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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Anthony Chow]

Cool.

And how or where did you sign up for this skimming duty?

thanks and have a nice weekend,

anthony.

On Fri, Jan 8, 2016 at 12:01 PM, Augustina Ragwitz 
wrote:

> On 2016-01-08 11:27, Anthony Chow wrote:
>
>> There is an URL for the duty:
>>
>> https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
>> [3]
>>
>
> Right, I read the wiki and it wasn't clear to me. Here's what the wiki
> says:
>
> "Since Nova is such an active project with a high number of incoming bug
> reports, we have a separate process for categorizing bugs and distributing
> the load of triage to a larger group of people."
>
> and
>
> "To help make sure that the triage queue stays under control, the
> following table lists the people that have committed to regularly triaging
> bugs for a given tag."
>
> The term "skimming" implies something done quickly at a surface level
> (like skimming off the fat or skimming a book). So I'm just asking, as part
> of "skimming" duty, are we also confirming the bugs, (confirming looks like
> it falls under the "Triaging" step), or is "skimming" just about tagging
> and getting the bugs into the triaging queues?
>
> Thanks!
>
> Augustina
>
>
>
> __
> 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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Augustina Ragwitz]

I think I just answered my own question ;) I looked at the blog post 
Markus provided in another part of this thread and it looks like 
"Skimming Duty" means both tag the bugs and the triaging step of 
confirming them such that they should no longer be in "New" status after 
you've touched them. I was confused because when I was looking at bugs 
in Launchpad, many had been tagged but left as "New" thus my need for 
clarification. Markus' blog post [1] is more clear than than the wiki on 
the triage expectations.


Also, Anthony, you can follow the instructions in Markus' original post. 
Just edit the wiki page and add your name to the table. The best irc 
channel for nova issues is #openstack-nova. You might want to see the 
Nova How to Get Involved document [2].


[1] 
http://markuszoeller.github.io/posts/openstack-bugs/#status-and-contributor-responsibility

[2] http://docs.openstack.org/developer/nova/how_to_get_involved.html

__
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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Anthony Chow]

thanks so much. :)

On Fri, Jan 8, 2016 at 12:33 PM, Augustina Ragwitz 
wrote:

> I think I just answered my own question ;) I looked at the blog post
> Markus provided in another part of this thread and it looks like "Skimming
> Duty" means both tag the bugs and the triaging step of confirming them such
> that they should no longer be in "New" status after you've touched them. I
> was confused because when I was looking at bugs in Launchpad, many had been
> tagged but left as "New" thus my need for clarification. Markus' blog post
> [1] is more clear than than the wiki on the triage expectations.
>
> Also, Anthony, you can follow the instructions in Markus' original post.
> Just edit the wiki page and add your name to the table. The best irc
> channel for nova issues is #openstack-nova. You might want to see the Nova
> How to Get Involved document [2].
>
> [1]
> http://markuszoeller.github.io/posts/openstack-bugs/#status-and-contributor-responsibility
> [2] http://docs.openstack.org/developer/nova/how_to_get_involved.html
>
> __
> 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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Augustina Ragwitz]

On 2016-01-08 11:27, Anthony Chow wrote:

There is an URL for the duty:

https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
[3]


Right, I read the wiki and it wasn't clear to me. Here's what the wiki 
says:


"Since Nova is such an active project with a high number of incoming bug 
reports, we have a separate process for categorizing bugs and 
distributing the load of triage to a larger group of people."


and

"To help make sure that the triage queue stays under control, the 
following table lists the people that have committed to regularly 
triaging bugs for a given tag."


The term "skimming" implies something done quickly at a surface level 
(like skimming off the fat or skimming a book). So I'm just asking, as 
part of "skimming" duty, are we also confirming the bugs, (confirming 
looks like it falls under the "Triaging" step), or is "skimming" just 
about tagging and getting the bugs into the triaging queues?


Thanks!

Augustina



__
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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Anthony Chow]

There is an URL for the duty:

https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty

BTW: how or where do you sign up?

Have a nice weekend and happy bug hunting.

anthony.

On Fri, Jan 8, 2016 at 10:50 AM, Augustina Ragwitz 
wrote:

> I signed up for the week before the Nova Midcycle meeting. Even though I'm
> still new, I feel capable of at least getting the tags mostly right. When
> I'm not quite sure which tag it would fall under, I search for similar bugs
> and see how they were tagged.
>
> I did have one clarifying question, what exactly are the expectations of
> the bug skimming duty? I assumed it was just tagging bugs to get them into
> the appropriate queues for triaging. Do we also need to confirm the bugs
> once they've been tagged or does that fall under "triage" and not
> "skimming"?
>
> Thanks!
> Augustina
>
> __
> 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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Markus Zoeller]

Anthony Chow <vcloudernb...@gmail.com> wrote on 01/07/2016 07:02:04 PM:

> From: Anthony Chow <vcloudernb...@gmail.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 01/07/2016 07:04 PM
> Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers for 
> bug skimming (1 week)
> 
> Sounds like the volunteer has to be working with Nova for sometime so 
> as to know how to properly tag the bug otherwise I am interested.
> 
> anthony.
> 

The more you know about Nova the easier is the bug triage. 
The more bug triage you do, the more you know about Nova.
My understanding of the current process is summarized in [1].

To have some numbers, there are 2-5 new bugs each day, which
takes me in sum 0.5-1.5 hours to triage per day (I'm with Nova
for 3 cycles).

[1] http://markuszoeller.github.io/posts/openstack-bugs/

Regards, Markus Zoeller (markus_z)

> 
> On Thu, Jan 7, 2016 at 3:06 AM, Markus Zoeller <mzoel...@de.ibm.com> 
wrote:
> The bug triage is an important first step to improve the quality
> of Nova. Every code contributor should be aware of it and can
> contribute without any special permissions [1]. We need more
> volunteers to do this. If you want to be one of them for 1 week,
> raise your hand in this thread or add your name in the wiki [2].
> At best we will have at least 1 person until today's Nova meeting
> at 21:00 UTC [3]. When you volunteer, I will be available in IRC
> for requests, too.
> 
> Regards, Markus Zoeller (markus_z)
> 
> References:
> [1]
> 
https://wiki.openstack.org/wikiBugTriage#Task_1:_Confirm_new_bugs_.28anyone.29

> [2]
> https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
> [3] https://wiki.openstack.org/wiki/Meetings/Nova
> 
> 
> 
__
> 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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Anthony Chow]

I wanted to get involved (or starting to get involve).  What is the system
requirement for bug triage?

So my next step should be to join the Nova bug team by signing up at
https://launchpad.net/~nova-bugs?

I guess the IRC channel is #openstack-nova?  Or I should use #openstack-dev?

Thanks and have a nice weekend,

anthony.

On Fri, Jan 8, 2016 at 1:38 AM, Markus Zoeller <mzoel...@de.ibm.com> wrote:

> Anthony Chow <vcloudernb...@gmail.com> wrote on 01/07/2016 07:02:04 PM:
>
> > From: Anthony Chow <vcloudernb...@gmail.com>
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev@lists.openstack.org>
> > Date: 01/07/2016 07:04 PM
> > Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers for
> > bug skimming (1 week)
> >
> > Sounds like the volunteer has to be working with Nova for sometime so
> > as to know how to properly tag the bug otherwise I am interested.
> >
> > anthony.
> >
>
> The more you know about Nova the easier is the bug triage.
> The more bug triage you do, the more you know about Nova.
> My understanding of the current process is summarized in [1].
>
> To have some numbers, there are 2-5 new bugs each day, which
> takes me in sum 0.5-1.5 hours to triage per day (I'm with Nova
> for 3 cycles).
>
> [1] http://markuszoeller.github.io/posts/openstack-bugs/
>
> Regards, Markus Zoeller (markus_z)
>
> >
> > On Thu, Jan 7, 2016 at 3:06 AM, Markus Zoeller <mzoel...@de.ibm.com>
> wrote:
> > The bug triage is an important first step to improve the quality
> > of Nova. Every code contributor should be aware of it and can
> > contribute without any special permissions [1]. We need more
> > volunteers to do this. If you want to be one of them for 1 week,
> > raise your hand in this thread or add your name in the wiki [2].
> > At best we will have at least 1 person until today's Nova meeting
> > at 21:00 UTC [3]. When you volunteer, I will be available in IRC
> > for requests, too.
> >
> > Regards, Markus Zoeller (markus_z)
> >
> > References:
> > [1]
> >
>
> https://wiki.openstack.org/wikiBugTriage#Task_1:_Confirm_new_bugs_.28anyone.29
>
> > [2]
> > https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
> > [3] https://wiki.openstack.org/wiki/Meetings/Nova
> >
> >
> >
> __
> > 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
>
__
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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Markus Zoeller]

The bug triage is an important first step to improve the quality
of Nova. Every code contributor should be aware of it and can 
contribute without any special permissions [1]. We need more 
volunteers to do this. If you want to be one of them for 1 week, 
raise your hand in this thread or add your name in the wiki [2]. 
At best we will have at least 1 person until today's Nova meeting 
at 21:00 UTC [3]. When you volunteer, I will be available in IRC 
for requests, too.

Regards, Markus Zoeller (markus_z)

References:
[1] 
https://wiki.openstack.org/wikiBugTriage#Task_1:_Confirm_new_bugs_.28anyone.29
[2] 
https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
[3] https://wiki.openstack.org/wiki/Meetings/Nova


__
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