Open Stack

Hello Again,
  It is nearly the weekend for most of us, with a decision due early next
week if we wish to provide the required time for getting visas. Might I
respectfully ask that people get the word out to other parts of the
operators community so that we have maximum exposure of this poll regarding
venue choice for the next mid-cyle operators meet up? For example I tweeted
a link to the following info in the mailing list archives and I saw a
couple of retweets (thanks!). People with a lot of twitter followers please
consider doing likewise - perhaps someone on the foundation? Other ways of
spreading the link also appreciated, of course.

Thanks!

Chris
---------- Forwarded message ----------
From: Chris Morgan <mihalis68 at gmail.com>
Date: Tue, Jun 14, 2016 at 11:09 AM
Subject: Mid-Cycle Ops Meetup venue choice - please make your voice heard!
To: OpenStack Operators <OpenStack-operators at lists.openstack.org>


[DISCLAIMER AT BOTTOM OF EMAIL]

Hello Everyone,
  There are two possible venues for the next OpenStack Operators Mid-Cycle
meetup. They both seem suitable and the details are listed here :

https://etherpad.openstack.org/p/ops-meetup-venue-discuss

To guide the decision making process and since time is drawing short for
planning an August event, the Ops Meetups Team meeting today on IRC decided
to try putting this issue to a poll. Please record *likely* attendance
preferences for Seattle, NYC (or neither) here :

http://doodle.com/poll/e4heruzps4g94syf

The poll is not binding :)

The Ops Meetups Team is hoping to see a good number of responses within the
next SEVEN DAYS.

Thanks for your attention.

Chris Morgan

Disclaimer: I work for Bloomberg LP, we have offered to be the host in NYC.
However, both proposals seem great to me

-- 
Chris Morgan <mihalis68 at gmail.com>



-- 
Chris Morgan <mihalis68 at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160617/e714fa70/attachment.html>