John Garbutt <j...@johngarbutt.com> wrote on 01/22/2016 11:55:52 AM: > From: John Garbutt <j...@johngarbutt.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 01/22/2016 11:57 AM > Subject: Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting > > On 22 January 2016 at 10:08, Markus Zoeller <mzoel...@de.ibm.com> wrote: > > The dates and times are final now [1]. They differ from the previously > > dates in this thread! The first and next meetings will be: > > > > Tuesday 2016-02-09 18:00 UTC #openstack-meeting-4 > > Tuesday 2016-02-23 18:00 UTC #openstack-meeting-4 > > Tuesday 2016-03-01 10:00 UTC #openstack-meeting-4 > > > > I have to cancel the meeting of 2016-02-16 in advance, as I have a > > medical appointment a day before which will knock me out for the week. > > > > The dates make it possible to attend either the "nova-bugs-team" > > or the "nova-team" of the same week as they take turns in "early" > > and "late" time of day. > > > > The agenda can be found in the wiki [2]. > > > > See you there! > > > > References: > > [1] http://eavesdrop.openstack.org/#Nova_Bugs_Team_Meeting > > [2] https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam > > > > Regard, Markus Zoeller (markus_z) > > A big thank you for pushing on this. > > As we head into Mitaka-3, post non-priority feature freeze, its a > great time to push on reviewing bug fixes, and fixing important bugs. > > Thanks, > johnthetubaguy >
This is a short reminder that the first meeting will take place tomorrow: Tuesday 2016-02-09 18:00 UTC #openstack-meeting-4 Agenda: https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam Regards, Markus Zoeller (markus_z) > > > > Markus Zoeller/Germany/IBM@IBMDE wrote on 01/20/2016 05:14:14 PM: > > > >> From: Markus Zoeller/Germany/IBM@IBMDE > >> To: "OpenStack Development Mailing List \(not for usage questions\)" > >> <openstack-dev@lists.openstack.org> > >> Date: 01/20/2016 05:27 PM > >> Subject: Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting > >> > >> 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. > >> > >> References: > >> [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@IBMDE wrote on 01/13/2016 01:24:06 PM: > >> > From: Markus Zoeller/Germany/IBM@IBMDE > >> > To: "OpenStack Development Mailing List" > >> <openstack-dev@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev