[openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

Markus Zoeller mzoeller at de.ibm.com
Wed Jan 20 16:14:14 UTC 2016

Due to other meetings which merged since the announcement, 
the IRC meeting patch [1] I pushed proposes now: 
    Tuesday 1000 UTC #openstack-meeting beweekly-odd 
    Tuesday 1700 UTC #openstack-meeting beweekly-even

February the 9th at 1000 UTC will be the first kickoff meeting.
I'll have an agenda ready until then [2]. Feel free to ping me in IRC
or here on the ML when you have questions.

[1] https://review.openstack.org/#/c/270281/
[2] https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam

Regards, Markus Zoeller (markus_z)

Markus Zoeller/Germany/IBM at IBMDE wrote on 01/13/2016 01:24:06 PM:
> From: Markus Zoeller/Germany/IBM at IBMDE
> To: "OpenStack Development Mailing List" 
<openstack-dev at lists.openstack.org>
> Date: 01/13/2016 01:25 PM
> Subject: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting
> Hey folks,
> I'd like to revive the nova-bugs-team IRC meeting. As I want to chair
> those meetings in my "bug czar" role, the timeslots are bound to my
> timezone (UTC+1). The two bi-weekly alternating slots I have in mind
> are: 
> * Tuesdays, 10:00 UTC biweekly-odd  (to get folks to the east of me) 
> * Tuesdays, 16:00 UTC biweekly-even (to get folks to the west of me) 
> By choosing these slots, the concluded action items of this meeting can
> be finished until the next nova meeting of the same week on Thursday.
> The "early" and "late" timeslot is diametrical to the slots of the nova
> meeting to allow you to attend one of those meetings for your timezone.
>                    Day       odd week   even week
> -----------------  --------  ---------  ---------
> nova meeting       Thursday  21:00 UTC  14:00 UTC
> nova bugs meeting  Tuesday   10:00 UTC  16:00 UTC
> Let me know if you think these slots are not reasonable. My goal is
> to have the first kick-off meeting at the 9th of February at 10:00 UTC.
> The scope of the team meeting:
> * discuss and set the report-priority of bugs since the last meeting 
>   if not yet done.
> * decide action items for bug reports which need further attention
> * expire bugs which are hit by the expiration-policy unless someone 
>   disagrees.
> * get one or more volunteers for the rotating bug-skimming-duty. 
>   Get feedback from the volunteers from the previous week if there 
>   are noteworthy items.
> * check if new problem areas are emerging
> * discuss process adjustments/changes if necessary
> * spreading knowledge and discuss open points
> Review [1] contains my (WIP) proposal of the process I have in mind.
> This still needs concensus, but this is not the focus in this post.
> The first meeting(s) can be used as a kick-off to discuss items in
> that proposal.
> References:
> [1] Nova docs: "Bug Process": https://review.openstack.org/#/c/266453
> Regards, Markus Zoeller (markus_z)
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list