-
Notifications
You must be signed in to change notification settings - Fork 526
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
KubeCon + CloudNativeCon Barcelona, Spain, May 20 – 23, 2019 #127
Comments
CFP is closed already I think for this
…On Thu, Jan 31, 2019 at 7:41 AM Sarah Allen ***@***.***> wrote:
May 20 – 23, 2019
Fira Gran Via, Barcelona, Spain
https://events.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2019/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#127>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AdwPwByX8S71Wq4zTj3u0b5VBhiMbbBJks5vIw6QgaJpZM4ackrT>
.
|
Suggest an evening meeting on Tuesday, as seems to conflict less with other things... |
@ultrasaurus if there's no one else volunteering to organize this in person meeting I can arrange something. @justincormack Tues evening works very well for me |
@fntlnz that would be fabulous! Tues works for me too :) |
So, I will find a place to have all of us doing a Dinner together on Tues 21. Will post here details about it. |
would be also great to send out a calendar invitation after the place is sorted out :) |
@hannibalhuang yes! https://forms.gle/iBFFuaNRbtWjHX7E9 I'll collect the names and book the restaurant for us! |
The restaurant confirmed the reservation for our dinner! We will meet there at 7.45pm! Address: Ocaña, Plaça Reial, 13-15, 08002 Barcelona |
Let's remember to take photos at dinner. I always forget! |
Here are other photos coming from the tweets at the kubecon. |
Let's close this @ultrasaurus ? |
May 20 – 23, 2019
Fira Gran Via, Barcelona, Spain
https://events.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2019/
Moved links to talks to #173
The text was updated successfully, but these errors were encountered: