<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Oct 14, 2014, at 6:00 PM, Lance Bragstad <<a href="mailto:lbragstad@gmail.com">lbragstad@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 14, 2014 at 4:29 PM, Christopher Yeoh <span dir="ltr"><<a href="mailto:cbkyeoh@gmail.com" target="_blank">cbkyeoh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Tue, 14 Oct 2014 10:29:34 -0500<br>
Lance Bragstad <<a href="mailto:lbragstad@gmail.com">lbragstad@gmail.com</a>> wrote:<br>
<br>
> I found a couple of free times available for a weekly meeting if<br>
> people are interested:<br>
><br>
> <a href="https://review.openstack.org/#/c/128332/2" target="_blank">https://review.openstack.org/#/c/128332/2</a><br>
><br>
> Not sure if a meeting time has been hashed out already or not, and if<br>
> it has I'll change the patch accordingly. If not, we can iterate on<br>
> possible meeting times in the review if needed. This was to just get<br>
> the ball rolling if we want a weekly meeting. I proposed one review<br>
> for Thursdays at 2100 and a second patch set for 2000, UTC. That can<br>
> easily change, but those were two times that didn't conflict with the<br>
> existing meeting schedules in #openstack-meeting.<br>
<br>
</span>So UTC 2000 is 7am Sydney, 5am Tokyo and 4am Beijing time which is<br>
pretty early in the day. I'd suggest UTC 0000 if that's not too late for<br>
others who'd like to participate.<br>
<br>
Chris<br></blockquote><div><br></div><div>Unfortunately, we conflict with the I18N Team Meeting at UTC 0000 (in #openstack-meeting). I updated the review for UTC 1000. An alternating schedule would probably work well given the attendance from different times zones. I'll snoop around for another meeting time to alternate with, unless someone has one in mind. </div></div></div></div></blockquote><div><br></div><div>Don’t forget about #openstack-meeting-alt and #openstack-meeting-3 as alternative rooms for the meetings. Those have the meeting bot and are managed on the same wiki page for scheduling.</div><div><br></div><div>Doug</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5"><br>
<br>
><br>
><br>
><br>
> On Tue, Oct 14, 2014 at 3:55 AM, Thierry Carrez<br>
> <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>> wrote:<br>
><br>
> > Jay Pipes wrote:<br>
> > > On 10/13/2014 07:11 PM, Christopher Yeoh wrote:<br>
> > >> I guess we could also start fleshing out in the repo how we'll<br>
> > >> work in practice too (eg once the document is stable what<br>
> > >> process do we have for making changes - two +2's is probably not<br>
> > >> adequate for something like this).<br>
> > ><br>
> > > We can make it work exactly like the openstack/governance repo,<br>
> > > where ttx has the only ability to +2/+W approve a patch for<br>
> > > merging, and he tallies a majority vote from the TC members, who<br>
> > > vote -1 or +1 on a proposed patch.<br>
> > ><br>
> > > Instead of ttx, though, we can have an API working group lead<br>
> > > selected from the set of folks currently listed as committed to<br>
> > > the effort?<br>
> ><br>
> > Yes, the working group should select a "chair" who would fill the<br>
> > same role I do for the TC (organize meetings, push agenda, tally<br>
> > votes on reviews, etc.)<br>
> ><br>
> > That would be very helpful in keeping that diverse group on track.<br>
> > Now you just need some volunteer :)<br>
> ><br>
> > --<br>
> > Thierry Carrez (ttx)<br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>