Apologies, * On a side note, can we decide on a [email-subject-tag] to help filter these in [Openstack-operators] * Suggestion: [ops-meetups-team]
For the delay that is since rain and Houston, TX fight a lot and rain is winning these days unfortunately. I was tasked with submitting to the ML a request to discuss how do we handle the waiting list for those who are not able to attend the Ops Midcycle due to the cap. Looking at EventBrite [ https://www.eventbrite.com/support/articles/en_US/How_To/how-to-set-up-an-event-waitlist?lg=en_US ] if we are going to do a waitlist, this looks like a great option where basically we get details about the attendees we need and the waitlist is automatically created once the cap is hit. Playing devil’s advocate, my only apprehension to this process is should the waitlist be large, and there is a significant reason for someone who attended a previous Ops Midcycle to need to attend the next, how would that be handled? I am sure there are other potential issues that can be identified. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 6/1/16, 11:33 PM, "Tom Fifield" <t...@openstack.org> wrote: >Hello all, > >Thank you very much to the dozen of you who participated in our second >meeting. We had some fantastic discussion, summarised below (the meeting >overview can be found at [3] and the full log at [4]). > > >==Next Meeting== >Unless there is further discussion, this the next meeting is at: > >==> Tuesday, 14 of Jun at 1400 UTC[1] in #openstack-operators > >[2] will be kept up to date with information about the meeting time and >agenda > > >==August Meetup== >Since there really isn't a lot of time left and we have proposals >already, we decided for this time we would not do the open call. >So, gfa, shintano and I will be working behind the scenes with Bestbuy >(Seattle) and Bloomberg (NYC) a little bit to get further details on >their venues - we will report to the group as soon as we have some >progress so we can make a decision for the August meetup. > > > >==Meetup size== >We had a great discussion on meetup size and it's looking like 150-200 >is the proposal, please participate in Matt Jarvis' thread at: > >http://lists.openstack.org/pipermail/openstack-operators/2016-June/010607.html > > > > >==Waitlist management== >There was a good proposal on how to manage the waitlist (give those that >missed out first go at the next one). mrhillsman will write that up and >send it through to the list shortly. > > > > >Regards, > > >Tom > > >[1] >http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team&iso=20160614T22&p1=241 > >[2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information > >[3] >http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-31-14.01.html > >[4] >http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-31-14.01.log.html > >_______________________________________________ >OpenStack-operators mailing list >OpenStack-operators@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
