Hi All, After few weeks and meetings on Friday, we decide to change a little bit the pattern of this meeting. We decided to keep the schedule up and open for anything/anyone, but each times, we will check before the meeting if the agenda [1] is empty. If so, then we won't make it, or we would use this schedule for another topic. This has been decided like that for few reasons. The main reason is that we repeat and discuss the same status/issues that we previously discuss on our normal scrum and most of the attendees is folks from inside the DFG. So its a kind of a repetition for us and there is no big value in this except when people external of the DFG bring things, like Weshay used to or rdo-cloud folks.
Thank you all. Mathieu [1] https://etherpad.openstack.org/p/tripleo-upgrade-squad-meeting On 11/09/2017 01:23 PM, mathieu bultel wrote: > Hi TripleO, > > As discuss on the last TripleO meeting, the Upgrade squad will stand a > weekly meeting each Friday to discuss and share about the Upgrade > related topics. > > Every body who are interested is welcome to join us and fell free to > raise any questions/issues/concerns. > > Tomorrow will be our first session and it will be more CI oriented. > > We will use this etherpad to track the discussions and the status: > > https://etherpad.openstack.org/p/tripleo-upgrade-squad-meeting > > For the next meetings, I will setup agenda for each of those with the > following topics: Bugs, CI and Features (Specs), but everybody can add > his own items in the agenda. > > Mathieu > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
