-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DockerCon, San Francisco, CA, Apr 30 - May 2, 2019 #151
Comments
I think Wednesday (May 1) and Thursday (May 2) evenings are good times outside the conference schedule. I'm not as familiar with SF compared to others here, so I'm open to suggestions on places to get dinner. |
We have an open source security summit on Thursday as part of DockerCon, if anyone from the SIG needs a ticket let me know and I will sort it out... |
Let's set the date as May 1 (Wednesday) then? @justincormack, I'd like to join in on that! |
I can make it on Wed or Thurs (with Thursday slightly preferred)... I think the open source security summit is just a related Dockercon event, looks like 10a-noon so I don't think it will collide with evening gathering. Some location options:
If we want to go a little farther, two of my fave restaurants, both "french vietnamese" Open to suggestions from other locals or food preferences from visitors |
Thursday is better for me, I have another event on Wednesday at 8.30ish. There are always lots of dockercon events at thirsty bear as its next to moscone so I might be tired of it by then. osha thai/mikkeller/slanted door are all lovely, havent tried le coloniel before... |
Lets do Thursday evening then. I agree on the no reservations being a plus :), unless we have dietary restrictions. Tentatively let's set it as Thursday May 2, 7:30pm at Mikkeller. |
Sounds great but I am flying back to the UK on Thursday |
Meeting up @ DockerCon was awesome! |
I think there are going to be a few of us at DockerCon and also in the area, let's meet up in the evening.
EDIT: Thursday May 2, 7:30pm at Mikkeller.
The text was updated successfully, but these errors were encountered: