A quick update on this: I put together a small ethercalc for the QA sessions, you can find it at https://ethercalc.openstack.org/Pike-PTG-QA-Planning.
I felt 30min is too short for most sessions, also considering we will need breaks every now and then, and some grace time for people to come and go, so I allocated 2 x 30min slots to most sessions. If you need a projector please book a room accordingly, and mark it on the schedule so that folks know where to go. Andrea On Wed, Feb 15, 2017 at 2:22 PM Andrea Frittoli <andrea.fritt...@gmail.com> wrote: > On Tue, Feb 14, 2017 at 3:00 PM Ken'ichi Ohmichi <ken1ohmi...@gmail.com> > wrote: > > Hi Andrea, > > Thanks for organizing QA sessions for PTG. > > 2017-02-13 16:16 GMT-08:00 Andrea Frittoli <andrea.fritt...@gmail.com>: > > Hello team, > > > > I did some work on the etherpad  to organise the QA PTG schedule > based on > > the proposed sessions. > > I separated discussion sessions from hands-on type of actives. I thing > the > > former will require a fixed schedule so folks may know when to pop-in to > > attend; the latter may happen more ad-hoc based on who's there an not > busy > > in a session. We can have a final discussion on this in the QA meeting on > > Thursday . > > It is a nice idea to separate discussion sessions from hands-on (code > sprint) sessions. > Now we have 9 discussion sessions which don't require arranging the > time schedule with the other teams. > So I feel it is nice to schedule them in the first day and schedule > hands-on sessions(working items based on discussion sessions and 3 > original hands-on session) in the second day so that we get feedback > and discuss them again during the second day. > That is an idea, I am happy to see the other schedule idea :-) > > > Thanks - that's a good idea. > I would keep the "priorities" session at the end though. > > > > > I haven't fixed the exact schedule yet, I will do it soon; meanwhile > please > > let me know if you think your session will need more or less then 30' > which > > is the standard time I would allocate. > > Discussions that overrun the planned time can go in a parking lot, which > we > > can pick up later at the PTG or during meetings. > > Any session preparation work / existing material, previous discussions, > > links and so can go in the respective etherpad. > > > > I think we have a good set of topics to discuss and code to write, > enough to > > keep us busy for more than the time we have. > > Nonetheless, if you have more topic to propose please continue adding > them > > to the etherpad. > > Yes, it is nice to make us busy in PTG. > > Thanks > Ken Ohmichi > > --- > > >  https://etherpad.openstack.org/p/qa-ptg-pike > >  > > > https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_February_16th_2017_.281700_UTC.29 > > > > > __________________________________________________________________________ > > 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