Nov 27, 2019 - Emily Chin    

KubeCon EU CFP Support

GitLab's Tech Evangelism team wants to help you get on stage at KubeCon EU!

This blog post is Unfiltered

It’s that time of year: the deadline for proposals to the 2020 KubeCon/ CloudNativeCon Europe is coming up fast. Not to worry though; GitLab’s Technical Evangelism team is here to help.

I’m new to the Cloud Native community but, after attending my very first KubeCon this week in my backyard of San Diego, I couldn’t be more excited to dive in. Listening in on the amazing talks from the cloud native community was energizing, inspiring, and illuminating, and it’s awesome that GitLab wants to empower our community to share their ideas and learnings too. Our team is ready to review your proposals and flesh out any ideas that folks want to submit to the open call for proposals. Let us know how we can help today: the CFP closes on Wednesday, December 4, 2019 at 11:59PM PDT.

GitLab’s community is passionate, vocal, and deeply engaged, and elevating the voices of our users. If we can support with your submissions, feel free to complete this form to get the ideas flowing, or reach out to our Director of Technical Evangelism directly on Twitter – @pritianka.

The call for proposals for GitLab KubeCon Amsterdam closes on December 4! Get more details and submit your talks here.

DISCLAIMER: This blog is intended for user-generated content submitted by the GitLab team. The views and opinions represented in this blog are personal to the author of each respective blog post and do not represent the views or opinions of GitLab unless explicitly stated. All content provided on this blog is for informational purposes only. Neither GitLab nor any of the individual blog contributors ("Contributors") make any representations as to the accuracy or completeness of any information on this site. Neither GitLab nor any Contributors will be liable for any errors or omissions in this information or any losses, injuries, or damages from the display or use of this information. Comments are welcome, and in fact, encouraged. However, GitLab reserves the right to edit or delete any comments submitted to this blog without notice should GitLab determine them to i) be spam or questionable spam; ii) include profanity; iii) include language or concepts that could be deemed offensive, hate speech, credible threats, or direct attacks on an individual or group; or iv) are in any other way a violation of GitLab's Website Terms of Use. GitLab is not responsible for the content in comments. This policy is subject to change at any time.