-
Notifications
You must be signed in to change notification settings - Fork 299
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
FOSDEM 2019 #1412
Comments
Something came up unfortunately, can't make it this time. |
@mwiget That's one more good reason to book a Snabb Lunch in Switzerland soon! cc @alexandergall @sleinen |
Yes! Looking forward to another Snabb Lunch. |
I'll be giving a talk at Saturday 13:00 with one of my students: https://fosdem.org/2019/schedule/event/writing_network_drivers_in_high_level_languages/ See https://github.com/ixy-languages/ixy-languages, might be of interest to some of you? Edit: our talk will be mostly about Rust due to time constraints |
I am arriving fairly late on Friday, and already commited for dinner on Sat but let me know where you will be and will see how to meet up... |
I'm arriving on Friday evening. I'm staying at Alma Hotel (near Grand Place), together with a few more igalians (although I think Andy is staying somewhere else). See you on Saturday at the SDN room! |
(What hardware interface will Ixy target next? i40e? fm10k? ConnectX? AVF? other? That's what I'd love to hear your thoughts about over a beer @emmericp.) |
Updated the text above based on the notion that at least @lukego @petebristow and @eugeneia will meet up at JAM Hotel in the evening e.g. for pizza and a few beers like last year. Everybody welcome! |
Recordings are available: Luke's talk: https://fosdem.org/2019/schedule/event/how_connectx_device_driver_works/ |
FOSDEM 2019 is this weekend!
This issue is to help keep track of who is attending and where we can find each other. Please leave comments if you're coming and if you know where you will be! I'll update the summary.
Attending:
Talks:
Friday evening:
Saturday evening:
cc @mwiget @justincormack @emmericp.
The text was updated successfully, but these errors were encountered: