diff --git a/.circleci/config.yml b/.circleci/config.yml index 8dbd4e10f37..c7d5f3544a0 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -2,7 +2,7 @@ version: 2 jobs: production: docker: - - image: cibuilds/hugo:0.81.0 + - image: cibuilds/hugo:0.88.a auth: username: devopsdaysbuild password: $DOCKERHUB_PASSWORD @@ -14,7 +14,7 @@ jobs: build: docker: - - image: cibuilds/hugo:0.81.0 + - image: cibuilds/hugo:0.88.1 auth: username: devopsdaysbuild password: $DOCKERHUB_PASSWORD diff --git a/FETCH_HEAD b/FETCH_HEAD new file mode 100644 index 00000000000..e69de29bb2d diff --git a/content/events/2020-austin/schedule.md b/content/events/2020-austin/schedule.md index 220e158dd21..ab36ca0dc11 100755 --- a/content/events/2020-austin/schedule.md +++ b/content/events/2020-austin/schedule.md @@ -1,11 +1,11 @@ +++ Title = "Schedule" Type = "event" -Description = "Schedule for DevOpsDays Austin 2020" +Description = "Schedule for DevOpsDays Oslo 2021" +++
- +
\ No newline at end of file diff --git a/content/events/2021-aarhus/location.md b/content/events/2021-aarhus/location.md index 34a9c49146d..b94451de496 100644 --- a/content/events/2021-aarhus/location.md +++ b/content/events/2021-aarhus/location.md @@ -7,13 +7,11 @@ Description = "Location for devopsdays Aarhus 2021"

-We are happy to host DevOpsDays Aarhus at Scandic Aarhus City. +DevOpsDays Aarhus 2021, has been cancelled due to Covid.
+Join us at DevOpsDays Aarhus 2022! -Scandic provides a urban setting in downtown Aarhus. Scandic is close to public transportation. - -Parking can be bought at Scandic, or nearby at Magasin.

- {{< event_map >}} + {{< event_map >}} diff --git a/content/events/2021-aarhus/welcome.md b/content/events/2021-aarhus/welcome.md index 24a15ee0535..940f061aa48 100644 --- a/content/events/2021-aarhus/welcome.md +++ b/content/events/2021-aarhus/welcome.md @@ -8,25 +8,9 @@ Description = "devopsdays Aarhus 2021" {{< event_logo >}} -Due to the COVID-19 situation, we rescheduled the event from June 2020 to the fall of 2021. We will automatically postpone your ticket to these dates, unless you prefer a full refund of course. +Due to the COVID-19 situation, we rescheduled the event from June 2020 to the spring of 2022. We will automatically postpone your ticket to these dates, unless you prefer a full refund of course. -

-
- Dates -
-
- Devopsdays will come to Aarhus {{< event_start >}} - {{< event_end >}} -
-
- -
-
- Location -
-
- {{< event_location >}} -
-
+Join us at DevOpsDays Aarhus 2022! +{{< event_map >}} diff --git a/content/events/2021-baku/registration.md b/content/events/2021-baku/registration.md new file mode 100644 index 00000000000..ee7d26598d2 --- /dev/null +++ b/content/events/2021-baku/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Baku 2021" ++++ + +
+ + diff --git a/content/events/2021-baku/speakers.md b/content/events/2021-baku/speakers.md new file mode 100644 index 00000000000..45156d57bef --- /dev/null +++ b/content/events/2021-baku/speakers.md @@ -0,0 +1,5 @@ ++++ +Title = "Speakers" +Type = "speakers" +Description = "Speakers for devopsdays Baku 2021" ++++ diff --git a/content/events/2021-baku/speakers/behruz.md b/content/events/2021-baku/speakers/behruz.md new file mode 100644 index 00000000000..c0625a06058 --- /dev/null +++ b/content/events/2021-baku/speakers/behruz.md @@ -0,0 +1,18 @@ ++++ +Title = "Bahruz Garamammadov" +linkedin = "https://www.linkedin.com/in/bahruz-garamammadov-61a50832/" +image = "behruz.jpg" +type = "speaker" +linktitle = "bahruz-garamammadov" ++++ + +#### Speaker + +##### Senior Technology Consultant at EY +##### Amsterdam Area, Netherlands + +Senior technology professional with 6+ years of experience in delivering innovative and impactful digital +products in wide-range industries such as FinTech, retail banking, telecommunications and emergency +management. Have solid experience in all phases of product development lifecycle, from strategy and +vision to ideation and prototyping, from requirements management to development and technical +delivery. \ No newline at end of file diff --git a/content/events/2021-baku/speakers/rashad.md b/content/events/2021-baku/speakers/rashad.md new file mode 100644 index 00000000000..54d7f485bcc --- /dev/null +++ b/content/events/2021-baku/speakers/rashad.md @@ -0,0 +1,18 @@ ++++ +Title = "Rashad Farajullayev" +linkedin = "https://www.linkedin.com/in/rashad-farajullayev/" +image = "rashad.jpg" +type = "speaker" +linktitle = "rashad-farajullayev" ++++ + +#### Speaker + +##### Senior Software Engineer at PASHA Bank OJSC + +Architected and developed large enterprise systems by using various technologies. Being in the software +development industry for more than 17 years, bringing an in-depth understanding of architecting and +developing mission critical and security critical systems. Experienced in supporting critical systems in +force majeure situations by analysis, rapid decision making and problem-solving. Several times +successfully applied architectural modifications, optimization, work parallelization and disaster recovery +of critical systems. Consulted as an expert in cybersecurity improvements and incident investigations. \ No newline at end of file diff --git a/content/events/2021-baku/speakers/rufat.md b/content/events/2021-baku/speakers/rufat.md new file mode 100644 index 00000000000..8bd0f3c37b2 --- /dev/null +++ b/content/events/2021-baku/speakers/rufat.md @@ -0,0 +1,18 @@ ++++ +Title = "Rufat Alizade" +linkedin = "https://www.linkedin.com/in/rufat-alizade-39100528/" +image = "rufat.jpg" +type = "speaker" +linktitle = "rufat-alizade" ++++ + +#### Speaker + +##### DevOps Team Lead at Accenture + +Write ARM (Azure Resource Manager) templates with DSC (Desired State Configuration) and +PowerShell scripts. + +Resolve daily tasks from Jira ticket system. + +Troubleshoot and resolve issues with CI/CD \ No newline at end of file diff --git a/content/events/2021-baku/speakers/rustam.md b/content/events/2021-baku/speakers/rustam.md new file mode 100644 index 00000000000..69534bf9643 --- /dev/null +++ b/content/events/2021-baku/speakers/rustam.md @@ -0,0 +1,18 @@ ++++ +Title = "Rustam Aliyev" +linkedin = "https://www.linkedin.com/in/aliyev/" +image = "rustam.jpg" +type = "speaker" +linktitle = "rustam-aliyev" ++++ + +#### Speaker + +##### Senior Software Engineer at Skype +##### London, United Kingdom + +Azure/cloud migration. Development of indirect monetisation (ad) services. + +Responsible for technical aspects of the projects from pre-sales to release, capturing baseline and target +architectures, working closely with R&D and operations. Supporting pre-sales in EMEA region for the +major mobile operators including Orange, T-Mobile, Vodafone, Three, and others. \ No newline at end of file diff --git a/content/events/2021-baku/sponsor.md b/content/events/2021-baku/sponsor.md new file mode 100644 index 00000000000..23f10f0e5d4 --- /dev/null +++ b/content/events/2021-baku/sponsor.md @@ -0,0 +1,7 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor DevOpsDays Baku 2021" ++++ + +The DevOpsDays event mandate is to bring the highest ­quality speakers, experts and the curious together. By sponsoring DevOpsDays, you will be exposing your company’s brand and services to Baku’s top talent in this rapidly growing space. diff --git a/content/events/2021-baku/welcome.md b/content/events/2021-baku/welcome.md new file mode 100644 index 00000000000..1cdba7c4ce7 --- /dev/null +++ b/content/events/2021-baku/welcome.md @@ -0,0 +1,35 @@ ++++ +Title = "DevOpsDays Baku 2021" +Type = "welcome" +aliases = ["/events/2021-baku/"] +Description = "DevOpsDays Baku 2021" ++++ + +
+ {{< event_logo >}} +
+ +
+ +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ +
+
+ Location +
+
+ {{< event_location >}} +
+
+ + + diff --git a/content/events/2021-bogota/speakers/Adarsh-Shah.md b/content/events/2021-bogota/speakers/Adarsh-Shah.md new file mode 100644 index 00000000000..699562bccd8 --- /dev/null +++ b/content/events/2021-bogota/speakers/Adarsh-Shah.md @@ -0,0 +1,9 @@ ++++ +Title = "Adarsh Shah" +Twitter = "@shahadarsh" +image = "Adarsh-Shah.jpg" +type = "speaker" +linktitle = "Adarsh-Shah" + ++++ +Adarsh Shah is the Founder & CEO of CompuZest. He is an Engineering Leader, Coach, Public Speaker, Hands-on Architect & a Change Agent. He is also an organizer for Devopsdays NYC conference & devopsnyc meetup. Adarsh has a keen interest in building systems that add business value. These days, he is excited about working with Machine Learning and Cloud-Native technologies. You can reach him on twitter at @shahadarsh. diff --git a/content/events/2021-bogota/speakers/Amber-Vanderburg.md b/content/events/2021-bogota/speakers/Amber-Vanderburg.md index 2ee0a7d2387..12f55b16bab 100644 --- a/content/events/2021-bogota/speakers/Amber-Vanderburg.md +++ b/content/events/2021-bogota/speakers/Amber-Vanderburg.md @@ -1,6 +1,6 @@ +++ Title = "Amber Vanderburg" -Twitter = "" +Twitter = "@vanderburgamber" image = "Amber-Vanderburg.jpg" type = "speaker" linktitle = "Amber-Vanderburg" diff --git a/content/events/2021-bogota/speakers/Carlos-Chavez.md b/content/events/2021-bogota/speakers/Carlos-Chavez.md new file mode 100644 index 00000000000..be912b022fb --- /dev/null +++ b/content/events/2021-bogota/speakers/Carlos-Chavez.md @@ -0,0 +1,12 @@ ++++ +Title = "Carlos Chavez" +Twitter = "@elnumeroprimo" +image = "Carlos-Chavez.png" +type = "speaker" +linktitle = "Carlos Chavez" + ++++ + +Gerente Regional de DevOps y Agilidad , laboró como Coach de Transformación en Entel Perú empresa de telecomunicaciones donde lideró y participó activamente en iniciativas de transformación y adopción ágil con un enfoque de cambio cultural y tecnológico. +Diseñó e implementó la estrategia de DevOps en la misma empresa y en Belcorp multinacional de belleza con presencia en 14 paises por el año 2013 , Consultor Senior para Deloitte en la práctica de Integración Tecnológica y TS&A Technology Strategy & Architecture. +Formado como coach en el programa de Conscious Business Coaching CBC + de Fred Kofman, Advisor de Leadership Development en Google, ex-Vicepresidente de Desarrollo Ejecutivo en Linkedin y coach de ejecutivos C-Level de empresas en Silicon Valley, como Facebook y Yahoo. \ No newline at end of file diff --git a/content/events/2021-bogota/speakers/Giovanny-Cifuentes.md b/content/events/2021-bogota/speakers/Giovanny-Cifuentes.md new file mode 100644 index 00000000000..76651ef6ed1 --- /dev/null +++ b/content/events/2021-bogota/speakers/Giovanny-Cifuentes.md @@ -0,0 +1,9 @@ ++++ +Title = "Giovanny Cifuentes" +Twitter = "@igacifuentes" +image = "Giovanny-Cifuentes.png" +type = "speaker" +linktitle = "Giovanny-Cifuentes" + ++++ +Agility Consultant, helps teams and organizations take advantage of opportunities and avoid threats by incorporating agility to provide faster value delivery cycles, collaborative environments with a holistic vision, aligning strategy with operation, experimenting to learn reflecting strategic results reshaping corporate culture through training, mentoring, guidance, consulting, and execution. diff --git a/content/events/2021-bogota/speakers/Javier-Galindo.md b/content/events/2021-bogota/speakers/Javier-Galindo.md new file mode 100644 index 00000000000..d16b432c08f --- /dev/null +++ b/content/events/2021-bogota/speakers/Javier-Galindo.md @@ -0,0 +1,9 @@ ++++ +Title = "Javier Galindo" +Twitter = "@hgalind0" +image = "Javier-Galindo.jpg" +type = "speaker" +linktitle = "Javier-Galindo" + ++++ +Javier Galindo, Systems Engineer from the Pontificia Universidad Javeriana, Master in Business Administration from INALDE Business School, founding partner and currently CEO / General Director of ITAC. He has more than twenty years of experience in managing software development projects using Java / JEE / SOA technology in Colombia, Central and South America. diff --git a/content/events/2021-bogota/speakers/Jhonnatan-Gil.md b/content/events/2021-bogota/speakers/Jhonnatan-Gil.md new file mode 100644 index 00000000000..750f4ff8f3d --- /dev/null +++ b/content/events/2021-bogota/speakers/Jhonnatan-Gil.md @@ -0,0 +1,9 @@ ++++ +Title = "Jhonnatan Gil" +Twitter = "@jthan24" +image = "Jhonnatan-Gil.png" +type = "speaker" +linktitle = "Jhonnatan-Gil" + ++++ +I'm a System Engineer and Software Developer. I love Linux and its philosophy. It's very enjoyable sharing all knowledge. Every day I learn around tech and make some PoC's that cleared some questions and so I can design solutions for currents problems. diff --git a/content/events/2021-bogota/speakers/John-Behrens.md b/content/events/2021-bogota/speakers/John-Behrens.md new file mode 100644 index 00000000000..1bc72dcce64 --- /dev/null +++ b/content/events/2021-bogota/speakers/John-Behrens.md @@ -0,0 +1,9 @@ ++++ +Title = "John Behrens" +Twitter = "@webconsultseu" +image = "John-Behrens.jpg" +type = "speaker" +linktitle = "John-Behrens" + ++++ +John Behrens is a freelancer from Hamburg Germany, he is fulfilling different roles in Developer, Tester, Scrum Master, Engineer, Architect, Trainer or Agile Coach. He is mostly willing to use any skill that is needed to help the team and take a project to success. diff --git a/content/events/2021-bogota/speakers/Jose-Aquino.md b/content/events/2021-bogota/speakers/Jose-Aquino.md index 8dbd6992574..ce55533c600 100644 --- a/content/events/2021-bogota/speakers/Jose-Aquino.md +++ b/content/events/2021-bogota/speakers/Jose-Aquino.md @@ -1,6 +1,6 @@ +++ Title = "Jose Aquino" -Twitter = "" +Twitter = "@Josemaquino" image = "Jose-Aquino.jpg" type = "speaker" linktitle = "Jose-Aquino" diff --git a/content/events/2021-bogota/speakers/Jose-Columbie.md b/content/events/2021-bogota/speakers/Jose-Columbie.md new file mode 100644 index 00000000000..d72ed5bfcec --- /dev/null +++ b/content/events/2021-bogota/speakers/Jose-Columbie.md @@ -0,0 +1,9 @@ ++++ +Title = "Jose Columbie" +Twitter = "@jjcolumbie" +image = "Jose-Columbie.jpg" +type = "speaker" +linktitle = "Jose-Columbie" + ++++ +Jose is a Master of Electrical Engineering turned .NET Developer/Architect. DevExpress MVP, Big DevOps advocate and Xamarin Certified. Jose spends most of his time on training, consulting and development of Azure based solutions for enterprise customers. Passionate about performance, data access, application design and DevExpress products, specially XAF and XPO. He is also a tech speaker, blogger and is always pushing to grow the community. Blazor is his new crush. diff --git a/content/events/2021-bogota/speakers/Julian-Jimenez.md b/content/events/2021-bogota/speakers/Julian-Jimenez.md new file mode 100644 index 00000000000..9940a8ad5ef --- /dev/null +++ b/content/events/2021-bogota/speakers/Julian-Jimenez.md @@ -0,0 +1,11 @@ ++++ +Title = "Julian Jimenez" +Twitter = "" +image = "Julian-Jimenez.jpg" +type = "speaker" +linktitle = "Julian-Jimenez" + ++++ +Juli, for friends all over the planet. +A constant learner of agile and digital transformations, current Director of Operations of TRU Startup (4IR, Blockchain), Systems and Computer Engineer, passionate agilist, entrepreneur, lover of soccer and table tennis. +Recently learning about cat care with the new member of the Sakura family. diff --git a/content/events/2021-bogota/speakers/Maria-Tenreiro.md b/content/events/2021-bogota/speakers/Maria-Tenreiro.md new file mode 100644 index 00000000000..317b2284b40 --- /dev/null +++ b/content/events/2021-bogota/speakers/Maria-Tenreiro.md @@ -0,0 +1,15 @@ ++++ +Title = "Maria Tenreiro" +Twitter = "@MariGaby31" +image = "Maria-Tenreiro.png" +type = "speaker" +linktitle = "Maria-Tenreiro" + ++++ +IT Professional focused on Software Quality Assurance (Analysis, design, automation) and Quality Systems. + +My most recent experiences are closely related to: Analysis of Requirements and Business Processes, Design, Automation (scripting) and Execution of Software Tests (Quality Systems), Integrations, Machine Learning, in the framework of Agile Methodologies. + +Convinced of the success that results from teamwork, structured, constant research, with a determined vision in the contribution of values, results and solutions. + +"Intelligence is the ability to adapt to change." .... Stephen Hawking diff --git a/content/events/2021-buffalo/program/dan-lines.md b/content/events/2021-buffalo/program/dan-lines.md new file mode 100644 index 00000000000..e6d71b9abbe --- /dev/null +++ b/content/events/2021-buffalo/program/dan-lines.md @@ -0,0 +1,10 @@ ++++ +Talk_date = "" +Talk_start_time = "" +Talk_end_time = "" +Title = "Promoted From Dev to Team Lead: 8 Things They Didn't Tell Me" +Type = "talk" +Speakers = ["dan-lines"] ++++ + +Three years into my software engineering career, a freight train hit me. I was promoted to dev team lead. This is a common trend in the engineering world - where many times the sole paths to success for excellent engineers are through management paths. However this path is not suited for all devs. \ No newline at end of file diff --git a/content/events/2021-buffalo/speakers/aaron-aldrich.md b/content/events/2021-buffalo/speakers/aaron-aldrich.md index 854abca02b6..594738469c7 100644 --- a/content/events/2021-buffalo/speakers/aaron-aldrich.md +++ b/content/events/2021-buffalo/speakers/aaron-aldrich.md @@ -2,7 +2,7 @@ Title = "Aaron Aldrich" Twitter = "crayzeigh" Website = "http://crayzeigh.com" -image = "aaron-aldrich.jpeg" +image = "aaron-aldrich.png" type = "speaker" linktitle = "aaron-aldrich" diff --git a/content/events/2021-buffalo/speakers/dan-lines.md b/content/events/2021-buffalo/speakers/dan-lines.md new file mode 100644 index 00000000000..d1fdca9b848 --- /dev/null +++ b/content/events/2021-buffalo/speakers/dan-lines.md @@ -0,0 +1,10 @@ ++++ +Title = "Dan Lines" +Twitter = "linknfg182" +Website = "https://devinterrupted.com/" +image = "dan-lines.png" +type = "speaker" +linktitle = "dan-lines" + ++++ +Dan here. A few things about me… First of all, the only thing I find more awkward than writing a bio about myself is asking someone else to write one about me. So first person it is! I’m a software engineer at heart. Two years ago I started a company with another engineer, my co-founder Ori Keren. I pulled the short straw so actually at the moment I’m responsible for customer success, marketing and sales. Which is crazy because I had never done any of those things before LinearB. I wish I had more time to write code but I love being customer facing because I’m learning a lot of new stuff. Before LinearB I was a dev team lead, and VP of Engineering. I’m obsessed with how dev teams work together. Like what makes great culture? And how can engineering leaders be data-driven without being performance tyrants? And why can cars drive themselves but I have to spend 30 minutes every day manually updating my project tickets? :-) More importantly, my partner Lauren and I just had a beautiful baby girl named Leila. We recently moved to sunny Southern California which is a welcome change for this suburban boy from up-state New York. \ No newline at end of file diff --git a/content/events/2021-buffalo/speakers/dewan-ahmed.md b/content/events/2021-buffalo/speakers/dewan-ahmed.md index a3f9ac3cd1c..47bab0e6a36 100644 --- a/content/events/2021-buffalo/speakers/dewan-ahmed.md +++ b/content/events/2021-buffalo/speakers/dewan-ahmed.md @@ -3,7 +3,7 @@ Title = "Dewan Ahmed" Twitter = "DewanAhmed" LinkedIn = "https://www.linkedin.com/in/diahmed" Website = "https://www.dewanahmed.com/" -image = "dewan-ahmed.jpeg" +image = "dewan-ahmed.png" type = "speaker" linktitle = "dewan-ahmed" diff --git a/content/events/2021-buffalo/speakers/jerren-every.md b/content/events/2021-buffalo/speakers/jerren-every.md index 7a63a663634..e79e3d7d155 100644 --- a/content/events/2021-buffalo/speakers/jerren-every.md +++ b/content/events/2021-buffalo/speakers/jerren-every.md @@ -1,6 +1,6 @@ +++ Title = "Jerren Every" -image = "jerren-every.jpeg" +image = "jerren-every.png" type = "speaker" linktitle = "jerren-every" diff --git a/content/events/2021-buffalo/speakers/lynn-catalano.md b/content/events/2021-buffalo/speakers/lynn-catalano.md index 54e332f3495..56bc2c57d3b 100644 --- a/content/events/2021-buffalo/speakers/lynn-catalano.md +++ b/content/events/2021-buffalo/speakers/lynn-catalano.md @@ -1,7 +1,7 @@ +++ Title = "Lynn Catalano" Website = "http://www.lynncatalano.com" -image = "lynn-catalano.jpeg" +image = "lynn-catalano.png" type = "speaker" linktitle = "lynn-catalano" diff --git a/content/events/2021-buffalo/speakers/pj-hagerty.md b/content/events/2021-buffalo/speakers/pj-hagerty.md index 361ca86ef17..045ca635039 100644 --- a/content/events/2021-buffalo/speakers/pj-hagerty.md +++ b/content/events/2021-buffalo/speakers/pj-hagerty.md @@ -2,7 +2,7 @@ Title = "PJ Hagerty" Twitter = "aspleenic" Website = "https://mattermost.com/" -image = "pj-hagerty.jpeg" +image = "pj-hagerty.png" type = "speaker" linktitle = "pj-hagerty" diff --git a/content/events/2021-houston/program/aakash-shah.md b/content/events/2021-houston/program/aakash-shah.md index b5710c7aa40..ec7a684d333 100644 --- a/content/events/2021-houston/program/aakash-shah.md +++ b/content/events/2021-houston/program/aakash-shah.md @@ -6,6 +6,7 @@ Title = "Why all speed and no security makes Infrastructure-as-Code a risky busi Type = "talk" Speakers = ["aakash-shah"] sharing_image = "aakash-shah.png" +slideslive = "38966541" +++ diff --git a/content/events/2021-houston/program/austin-king.md b/content/events/2021-houston/program/austin-king.md index 0240c52fe4e..97a7b4766cb 100644 --- a/content/events/2021-houston/program/austin-king.md +++ b/content/events/2021-houston/program/austin-king.md @@ -6,6 +6,7 @@ Title = "Games We Play to Improve on Incident Response" Type = "talk" Speakers = ["austin-king"] sharing_image = "austin-king.png" +slideslive = "38966533" +++ diff --git a/content/events/2021-houston/program/blessing-richardson.md b/content/events/2021-houston/program/blessing-richardson.md index cc664a43b6d..bf7ff3de60b 100644 --- a/content/events/2021-houston/program/blessing-richardson.md +++ b/content/events/2021-houston/program/blessing-richardson.md @@ -6,6 +6,8 @@ Title = "The Devil is in Delivery" Type = "talk" Speakers = ["blessing-richardson"] sharing_image = "blessing-richardson.png" +slideslive = "38966531" + +++ In the business of crafting software solutions, the delivery experience tends to slide down priority lists. Breaking the cycle of decreasing delivery experience, disappearing tribal knowledge, and bug sprawl requires a new approach. The devil of this process is in the details of delivery. diff --git a/content/events/2021-houston/program/dan-lorenc.md b/content/events/2021-houston/program/dan-lorenc.md index 1ccbac03fbc..28ead0bcea9 100644 --- a/content/events/2021-houston/program/dan-lorenc.md +++ b/content/events/2021-houston/program/dan-lorenc.md @@ -6,6 +6,7 @@ Title = "Zero-Trust Supply Chain Security" Type = "talk" Speakers = ["dan-lorenc"] sharing_image = "dan-lorenc.png" +slideslive = "38966337" +++ diff --git a/content/events/2021-houston/program/ell-marquez.md b/content/events/2021-houston/program/ell-marquez.md index 8d9fca36e99..4f6e5a1db39 100644 --- a/content/events/2021-houston/program/ell-marquez.md +++ b/content/events/2021-houston/program/ell-marquez.md @@ -6,6 +6,7 @@ Title = "Shift Left Security Concerns: DevSecOps is Pronounced DevOps: The Sec i Type = "talk" Speakers = ["ell-marquez"] sharing_image = "ell-marquez.png" +slideslive = "38966542" +++ diff --git a/content/events/2021-houston/program/ernest-mueller.md b/content/events/2021-houston/program/ernest-mueller.md index 572f3f847a8..64e06a19ed1 100644 --- a/content/events/2021-houston/program/ernest-mueller.md +++ b/content/events/2021-houston/program/ernest-mueller.md @@ -6,6 +6,8 @@ Title = "DevOps At A Distance: Helping Remote Work Succeed For Your Organization Type = "talk" Speakers = ["ernest-mueller"] sharing_image = "ernest-mueller.png" +slideslive = "38966543" + +++ Many organizations had to go remote during the pandemic, but it’s becoming clear that remote, or at least hybrid, work is here to stay in many places. But “just adding Zoom” doesn’t make you successful. What have DevOps and the CALMS principles taught us that we can use to make this a successful shift for our organizations? We’ll discuss lessons from leading engineering teams in several remote-native organizations. \ No newline at end of file diff --git a/content/events/2021-houston/program/george-muldoon.md b/content/events/2021-houston/program/george-muldoon.md index 82071fc6b8f..6ef1ea83335 100644 --- a/content/events/2021-houston/program/george-muldoon.md +++ b/content/events/2021-houston/program/george-muldoon.md @@ -6,6 +6,7 @@ Title = "The End of Traditional Authentication" Type = "talk" Speakers = ["george-muldoon"] sharing_image = "george-muldoon.png" +slideslive = "38966327" +++ diff --git a/content/events/2021-houston/program/jeremy-meiss.md b/content/events/2021-houston/program/jeremy-meiss.md index 36d432e8ca9..aaa056a5b19 100644 --- a/content/events/2021-houston/program/jeremy-meiss.md +++ b/content/events/2021-houston/program/jeremy-meiss.md @@ -6,6 +6,8 @@ Title = "DevOps before there was DevOps, 20yr old style" Type = "talk" Speakers = ["jeremy-meiss"] sharing_image = "jeremy-meiss.png" +slideslive = "38966571" + +++ The year is 1996. A bright, resourceful 20 yr old Network Administrator at an ISP is tasked with a mundane, tedious project. Said 20 yr old feels he has a better way, and takes it upon himself to get creative. What follows is a quick journey down memory lane to a time before DevOps was DevOps, through the eyes of a 43yo looking back on his 20yo self. Some of the takeaways here would be that: 1. DevOps principles should be used for good 2. Jeremy should not be asked to build a deck 3. We've learned a lot since 1996, and yet we've forgotten a lot. Let's get nostalgic. diff --git a/content/events/2021-houston/program/jj-asghar.md b/content/events/2021-houston/program/jj-asghar.md index 3c1eaa9589a..739714593bf 100644 --- a/content/events/2021-houston/program/jj-asghar.md +++ b/content/events/2021-houston/program/jj-asghar.md @@ -6,6 +6,8 @@ Title = "Migrating a monolith to Cloud-Native and the stumbling blocks that you Type = "talk" Speakers = ["jj-asghar"] sharing_image = "jj-asghar.png" +slideslive = "38966535" + +++ Have you started your Cloud-Native journey? The first thing you need to do is containerize your applications. Now that you’ve gotten past that first hurdle, I’m here to say there’s more to think about. In this talk, I’ll talk about stumbling blocks that a masked enterprise called AsgharLabs had to deal with, and hopefully shed some light on things you haven’t thought about. \ No newline at end of file diff --git a/content/events/2021-houston/program/mark-peters.md b/content/events/2021-houston/program/mark-peters.md index 5c59e782b44..80950117d77 100644 --- a/content/events/2021-houston/program/mark-peters.md +++ b/content/events/2021-houston/program/mark-peters.md @@ -6,6 +6,7 @@ Title = "Finding a security value chain" Type = "talk" Speakers = ["mark-peters"] sharing_image = "mark-peters.png" +slideslive = "38966529" +++ diff --git a/content/events/2021-houston/program/matthew-ostlind.md b/content/events/2021-houston/program/matthew-ostlind.md index 046d1e9c089..16e95972f62 100644 --- a/content/events/2021-houston/program/matthew-ostlind.md +++ b/content/events/2021-houston/program/matthew-ostlind.md @@ -6,6 +6,7 @@ Title = "Optimizing time to first deployment" Type = "talk" Speakers = ["matthew-ostlind"] sharing_image = "matthew-ostlind.png" +slideslive = "38966564" +++ diff --git a/content/events/2021-houston/program/milecia-mcgregor.md b/content/events/2021-houston/program/milecia-mcgregor.md index af5b4684c8a..604492ae60c 100644 --- a/content/events/2021-houston/program/milecia-mcgregor.md +++ b/content/events/2021-houston/program/milecia-mcgregor.md @@ -6,6 +6,7 @@ Title = "Adding Reproducible Experiments To Your Machine Learning Pipeline" Type = "talk" Speakers = ["milecia-mcgregor"] sharing_image = "milecia-mcgregor.png" +slideslive = "38966549" +++ diff --git a/content/events/2021-houston/program/nick-hodges.md b/content/events/2021-houston/program/nick-hodges.md index 0f291f4384f..ed4972338c0 100644 --- a/content/events/2021-houston/program/nick-hodges.md +++ b/content/events/2021-houston/program/nick-hodges.md @@ -6,6 +6,8 @@ Title = "Don’t Rely on Metrics Alone - Strategies for Continuous Improvement" Type = "talk" Speakers = ["nick-hodges"] sharing_image = "nick-hodges.png" +slideslive = "38966324" + +++ Tracking engineering metrics is viewed as table stakes by most dev leaders. But not all metrics are created equal. And dashboards don't help dev teams improve. Progressive software development organizations are moving beyond top-down metrics to focus on continuous improvement using Software Delivery Intelligence. diff --git a/content/events/2021-houston/program/rob-richardson.md b/content/events/2021-houston/program/rob-richardson.md index 9f23d8bdee1..3cc27cf8c83 100644 --- a/content/events/2021-houston/program/rob-richardson.md +++ b/content/events/2021-houston/program/rob-richardson.md @@ -6,6 +6,8 @@ Title = "Service Mess to Service Mesh" Type = "talk" Speakers = ["rob-richardson"] sharing_image = "rob-richardson.png" +slideslive = "38966538" + +++ In our quest to secure all the things, do we jump in too quickly? We’ll use Istio and Linkerd as example service meshes, and look at the features we would expect from a service mesh. We’ll dive into the day-1 experience with both Istio and Linkerd, and some advanced scenarios of using the service mesh. We’ll compare this to border security with an app gateway, and compare and contrast the security features, complexities, and implementation costs. You’ll leave with a concrete understanding of the benefits and tradeoffs you get when you pull in a service mesh, and be ready to justify the investment. diff --git a/content/events/2021-houston/program/thomas-haver.md b/content/events/2021-houston/program/thomas-haver.md index e35e37b2742..897c55f7106 100644 --- a/content/events/2021-houston/program/thomas-haver.md +++ b/content/events/2021-houston/program/thomas-haver.md @@ -6,6 +6,7 @@ Title = "The Rise and Benefits of Robotic Process Automation" Type = "talk" Speakers = ["thomas-haver"] sharing_image = "thomas-haver.png" +slideslive = "38966326" +++ diff --git a/content/events/2021-houston/program/veer-muchandi.md b/content/events/2021-houston/program/veer-muchandi.md index 43d0f325d79..1f007b040ff 100644 --- a/content/events/2021-houston/program/veer-muchandi.md +++ b/content/events/2021-houston/program/veer-muchandi.md @@ -6,6 +6,7 @@ Title = "What makes up a Modern Application Platform?" Type = "talk" Speakers = ["veer-muchandi"] sharing_image = "veer-muchandi.png" +slideslive = "38966532" +++ diff --git a/content/events/2021-houston/program/vishnu-vasudevan.md b/content/events/2021-houston/program/vishnu-vasudevan.md index 566e8fde8de..11d06bfc66e 100644 --- a/content/events/2021-houston/program/vishnu-vasudevan.md +++ b/content/events/2021-houston/program/vishnu-vasudevan.md @@ -6,6 +6,7 @@ Title = "How to integrate Security & Quality into Your CI/CD Pipelines and What Type = "talk" Speakers = ["vishnu-vasudevan"] sharing_image = "vishnu-vasudevan.png" +slideslive = "38966546" +++ diff --git a/content/events/2021-oslo/conduct.md b/content/events/2021-oslo/conduct.md new file mode 100644 index 00000000000..503c26ac6aa --- /dev/null +++ b/content/events/2021-oslo/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Oslo 2021" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Oslo 2021 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. + +### The Quick Version + +Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. + +### The Less Quick Version + +Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. + +Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. + +Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +_The devopsdays Oslo 2021 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2021-oslo/contact.md b/content/events/2021-oslo/contact.md new file mode 100644 index 00000000000..7c58dd730d7 --- /dev/null +++ b/content/events/2021-oslo/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Oslo 2021" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2021-oslo/location.md b/content/events/2021-oslo/location.md new file mode 100644 index 00000000000..e06cbcc5f5d --- /dev/null +++ b/content/events/2021-oslo/location.md @@ -0,0 +1,18 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays Oslo 2021" ++++ + +The event will be taking place at **Rebel Oslo**. + +Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details. + +{{< event_map >}} + + + diff --git a/content/events/2021-oslo/program.md b/content/events/2021-oslo/program.md new file mode 100644 index 00000000000..5965c6e877f --- /dev/null +++ b/content/events/2021-oslo/program.md @@ -0,0 +1,11 @@ ++++ +Title = "Program" +Type = "event" +Description = "Program for DevOpsDays Oslo 2021" ++++ + +
+
+ +
+
diff --git a/content/events/2021-oslo/propose.md b/content/events/2021-oslo/propose.md new file mode 100644 index 00000000000..4f679d4b8fe --- /dev/null +++ b/content/events/2021-oslo/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Oslo 2021" ++++ + {{< cfp_dates >}} + +
+ +There are three ways to propose a topic at devopsdays: +
    +
  1. A 30-minute talk presented during the conference, usually in the mornings.
    2. +
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table. +
+ +
+ +Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience: + +- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. +- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. +- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience. +- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen. +- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. +- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. + +
+ +How to submit a proposal: Send an email to [{{< email_organizers >}}] with the following information +
    +
  1. Type (presentation, panel discussion, ignite)
    2. +
  2. Proposal Title (can be changed later)
    3. +
  3. Description (several sentences explaining what attendees will learn)
    4. +
diff --git a/content/events/2021-oslo/speakers.md b/content/events/2021-oslo/speakers.md new file mode 100644 index 00000000000..0bc0998bbff --- /dev/null +++ b/content/events/2021-oslo/speakers.md @@ -0,0 +1,9 @@ ++++ +Title = "Speakers" +Type = "speakers" +Description = "Speakers for devopsdays Oslo 2021" ++++ + +
+ +
diff --git a/content/events/2021-oslo/sponsor.md b/content/events/2021-oslo/sponsor.md new file mode 100644 index 00000000000..b2c4d5cb86b --- /dev/null +++ b/content/events/2021-oslo/sponsor.md @@ -0,0 +1,7 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Oslo 2021" ++++ + +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. diff --git a/content/events/2021-oslo/welcome.md b/content/events/2021-oslo/welcome.md new file mode 100644 index 00000000000..bf65ceb42c9 --- /dev/null +++ b/content/events/2021-oslo/welcome.md @@ -0,0 +1,89 @@ ++++ +Title = "devopsdays Oslo 2021" +Type = "welcome" +aliases = ["/events/2021-oslo/"] +Description = "devopsdays Oslo 2021" ++++ + + +
+
+ DevOpsDays Oslo 2021 +
+
+
+
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+
+
+ Location +
+
+ {{< event_location >}} +
+
+ + +
+
+ Speakers +
+
+ {{< event_link page="speakers" text="Check out the speakers!" >}} +
+
+
+
+ Program +
+
+ {{< event_link page="program" text="View the program!" >}} +
+
+
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+
+
+ Twitter +
+
+ {{< event_twitter >}} +
+
+
+
+
diff --git a/content/events/2021-poznan/program/jakub-warczarek.md b/content/events/2021-poznan/program/jakub-warczarek.md index 4220dad53ad..3fe619c62fd 100644 --- a/content/events/2021-poznan/program/jakub-warczarek.md +++ b/content/events/2021-poznan/program/jakub-warczarek.md @@ -5,3 +5,5 @@ Speakers = ["jakub-warczarek"] +++ Save money and time with answers for following questions. Why shouldn't aim for 100% reliability? When speeding up an application two times doesn't improve user experience? And what should wake up on-call engineers? + +Jakub Warczarek is the Principal Architect at Nobl9, where he works on the ultimate SLO platform. During his career he has developed a deep love for open source software, cloud native solutions, distributed systems and proper observability. diff --git a/content/events/2021-tel-aviv/location.md b/content/events/2021-tel-aviv/location.md index 92c3dde885c..6c736a5aff7 100644 --- a/content/events/2021-tel-aviv/location.md +++ b/content/events/2021-tel-aviv/location.md @@ -3,11 +3,7 @@ Title = "Location" Type = "event" Description = "Location for devopsdays Tel Aviv 2021" +++ - -Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details. - - + +

EVENT LOCATION

+

Smolarz Auditorium, Tel Aviv University

+

Dr George Wise St, Tel Aviv-Yafo (link)

 +

+ + +

Transportation

+

Smolarz Auditorium is located inside Tel Aviv University and offers easy transport options and accessibility.
+If you are coming by public transportation, have a look at the Moovit app or website, that can provide the best information for bus, train or other public transport options.
+If you are coming by train, get off at the Tel Aviv University station. From there, exit to the Tel Aviv University side of the station, from there you will have many bus lines that will take you directly to Tel Aviv University. The relevant stop is the Haim Levanon/Dr. George Wise stop. +In Tel Aviv there are many other options for public transportation including Bubble (a ride-sharing service), bicycles and scooters for rent (Birds & Winds), and much more. If you have any questions regarding getting to the venue, please make sure to contact us. +

+ +​ + +

Parking

+

For particpants coming by car, there are multiple parking lots around the Tel Aviv University grounds. We are checking on the possibility for parking discounts.

+ +​ + +

Accommodation

+

Tel Aviv is home to Israel's most prestigious beachfront hotels. The main stretch of hotels is right across from the Tel Aviv Marina. You can find more information about the location of the various hotels here.

+ +​ + +

Leisure

+

Tel Aviv is one of the most culturally diverse cities you will ever see. There is a multitude of sights, tours, and museums that visitors can enjoy during their stay in Israel.

+ +​ + +

For more information on things to do in Tel Aviv, see here.

+ diff --git a/content/events/2021-tel-aviv/program.md b/content/events/2021-tel-aviv/program.md new file mode 100644 index 00000000000..1fcb069c536 --- /dev/null +++ b/content/events/2021-tel-aviv/program.md @@ -0,0 +1,20 @@ ++++ +Title = "Program" +Type = "program" +Description = "Program for devopsdays Tel aviv 2021" +Icons = "false" ++++ + +
+
+
+ The program of the event is under construction meanwhile you can go check the program here +
+
+ Open spaces registration is here. +
+
+ On top of our excellent talks we'll be running four workshop over the course of the two days, registration is form here. +
+
+
diff --git a/content/events/2021-tel-aviv/welcome.md b/content/events/2021-tel-aviv/welcome.md index 2a6a37a5e1d..f9760efa829 100644 --- a/content/events/2021-tel-aviv/welcome.md +++ b/content/events/2021-tel-aviv/welcome.md @@ -65,14 +65,14 @@ Description = "devopsdays Tel Aviv 2021" --> -
-
- Sponsors -
-
- {{< event_link page="sponsor" text="Sponsor the conference!" >}} -
-
+[comment]: <> (
) +[comment]: <> (
) +[comment]: <> ( Sponsors) +[comment]: <> (
) +[comment]: <> (
) +[comment]: <> ( {{< event_link page="sponsor" text="Sponsor the conference!" >}}) +[comment]: <> (
) +[comment]: <> (
)
diff --git a/content/events/2021-washington-dc/welcome.md b/content/events/2021-washington-dc/welcome.md index 0eacd3e2c86..756b35dd065 100644 --- a/content/events/2021-washington-dc/welcome.md +++ b/content/events/2021-washington-dc/welcome.md @@ -12,7 +12,9 @@ Description = "DevOpsDays Washington, D.C. 2021" After a pandemic-induced year off, DevOpsDays DC is returning for a one-day event in November 2021. We'll be virtual this year and hope (fingers crossed) to be back in person in 2022. - You may have noticed we changed our original event dates from September 16-17 to November 4. We share more about that change in this {{< event_link page="announcement" text="announcement" >}}. + We have our program set and registration is open! + + We have two types of tickets available to attend the event. You can register to attend for free. Or you can register as a VIP for $20. For your $20, you get to select a charitable organization to receive a donation from the money from your ticket and you'll get an exclusive DevOpsDays DC 2021 sticker mailed to you that only the VIPs will have.

@@ -33,14 +35,14 @@ Description = "DevOpsDays Washington, D.C. 2021"
--> -
- --> + - - --> + - - --> +
@@ -88,6 +90,5 @@ Description = "DevOpsDays Washington, D.C. 2021"
- + diff --git a/content/events/2021-zurich/program/achim-toeper.md b/content/events/2021-zurich/program/achim-toeper.md index 449d034a802..eb0513eaf3d 100644 --- a/content/events/2021-zurich/program/achim-toeper.md +++ b/content/events/2021-zurich/program/achim-toeper.md @@ -8,7 +8,7 @@ title = "52 years since mankind hit the moon - the hit parade of bringing DevOps type = "talk" speakers = ["achim-toeper"] youtube = "" -vimeo = "" +vimeo = "625196128" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/busra-koken.md b/content/events/2021-zurich/program/busra-koken.md index 77f1e62abae..19a7316554c 100644 --- a/content/events/2021-zurich/program/busra-koken.md +++ b/content/events/2021-zurich/program/busra-koken.md @@ -8,7 +8,7 @@ title = "Whole Wide World of DevOps: Are You Lost Yet?" type = "talk" speakers = ["busra-koken"] youtube = "" -vimeo = "" +vimeo = "625703801" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/christian-jakob.md b/content/events/2021-zurich/program/christian-jakob.md index 1793b8316e4..dacb1e8ad0a 100644 --- a/content/events/2021-zurich/program/christian-jakob.md +++ b/content/events/2021-zurich/program/christian-jakob.md @@ -8,7 +8,7 @@ title = "GitOps in a Nutshell" type = "talk" speakers = ["christian-jakob"] youtube = "" -vimeo = "" +vimeo = "632745404" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/courtney-heba.md b/content/events/2021-zurich/program/courtney-heba.md index b22fb7f388c..d8d98fa7a75 100644 --- a/content/events/2021-zurich/program/courtney-heba.md +++ b/content/events/2021-zurich/program/courtney-heba.md @@ -8,7 +8,7 @@ title = "Building Mobs to Disrupt Silos" type = "talk" speakers = ["courtney-heba", "ankur-marfatia"] youtube = "" -vimeo = "" +vimeo = "625209751" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/daniel-maher.md b/content/events/2021-zurich/program/daniel-maher.md index 1079f4983cc..fb599837189 100644 --- a/content/events/2021-zurich/program/daniel-maher.md +++ b/content/events/2021-zurich/program/daniel-maher.md @@ -8,7 +8,7 @@ title = "Principles of Observability" type = "talk" speakers = ["daniel-maher"] youtube = "" -vimeo = "" +vimeo = "625199803" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/david-patrick-adam.md b/content/events/2021-zurich/program/david-patrick-adam.md index cd50e4389c5..dddc9d2b8fe 100644 --- a/content/events/2021-zurich/program/david-patrick-adam.md +++ b/content/events/2021-zurich/program/david-patrick-adam.md @@ -8,7 +8,7 @@ title = "DevOps Maturity Assessment | A practical approach" type = "talk" speakers = ["david-patrick-adam"] youtube = "" -vimeo = "" +vimeo = "625201010" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/georg-hauzenberger.md b/content/events/2021-zurich/program/georg-hauzenberger.md index ddbe830883f..73e1836edf5 100644 --- a/content/events/2021-zurich/program/georg-hauzenberger.md +++ b/content/events/2021-zurich/program/georg-hauzenberger.md @@ -8,7 +8,7 @@ title = "Digitalization at Swiss Air-Rescue Rega: Four Key Aspects of Agile Tran type = "talk" speakers = ["claudine-clerc", "georg-hauzenberger"] youtube = "" -vimeo = "" +vimeo = "625195787" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/ignite-johan-abildskov.md b/content/events/2021-zurich/program/ignite-johan-abildskov.md index d8fed9cb1b5..11f756b3b25 100644 --- a/content/events/2021-zurich/program/ignite-johan-abildskov.md +++ b/content/events/2021-zurich/program/ignite-johan-abildskov.md @@ -8,7 +8,7 @@ title = "This rock is better than your software" type = "talk" speakers = ["johan-abildskov"] youtube = "" -vimeo = "" +vimeo = "625193249" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/jelena-malic.md b/content/events/2021-zurich/program/jelena-malic.md index 8dcb1ace23f..eace9ad231d 100644 --- a/content/events/2021-zurich/program/jelena-malic.md +++ b/content/events/2021-zurich/program/jelena-malic.md @@ -8,7 +8,7 @@ title = "End-to-End Monitoring at Scale" type = "talk" speakers = ["jelena-malic", "joana-soares-machado"] youtube = "" -vimeo = "" +vimeo = "625233229" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/jessica-fields.md b/content/events/2021-zurich/program/jessica-fields.md index ccc9f8f7742..3c42e6ddccc 100644 --- a/content/events/2021-zurich/program/jessica-fields.md +++ b/content/events/2021-zurich/program/jessica-fields.md @@ -8,7 +8,7 @@ title = "UX Unicorns Do Not Exist: The Myth of the One-Person Usability Team" type = "talk" speakers = ["jessica-fields"] youtube = "" -vimeo = "" +vimeo = "625710283" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/johan-abildskov.md b/content/events/2021-zurich/program/johan-abildskov.md index cd7b4797681..36e649b98ff 100644 --- a/content/events/2021-zurich/program/johan-abildskov.md +++ b/content/events/2021-zurich/program/johan-abildskov.md @@ -8,7 +8,7 @@ title = "Automation is hard and we are doing it wrong" type = "talk" speakers = ["johan-abildskov"] youtube = "" -vimeo = "" +vimeo = "625231844" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/jonathan-smart.md b/content/events/2021-zurich/program/jonathan-smart.md index 6c7f3fae98b..63c3228bb43 100644 --- a/content/events/2021-zurich/program/jonathan-smart.md +++ b/content/events/2021-zurich/program/jonathan-smart.md @@ -8,7 +8,7 @@ title = "Better Value, Sooner, Safer & Happier" type = "talk" speakers = ["jonathan-smart"] youtube = "" -vimeo = "" +vimeo = "625210719" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/justus-graumann.md b/content/events/2021-zurich/program/justus-graumann.md index daf95565122..6464ad18dc6 100644 --- a/content/events/2021-zurich/program/justus-graumann.md +++ b/content/events/2021-zurich/program/justus-graumann.md @@ -8,7 +8,7 @@ title = "DevGreenOps" type = "talk" speakers = ["justus-graumann"] youtube = "" -vimeo = "" +vimeo = "625193431" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/michael-cote.md b/content/events/2021-zurich/program/michael-cote.md index cb326282369..03442c61d00 100644 --- a/content/events/2021-zurich/program/michael-cote.md +++ b/content/events/2021-zurich/program/michael-cote.md @@ -8,7 +8,7 @@ title = "Beyond DevOps metrics – technical, business, and culture metrics for type = "talk" speakers = ["michael-cote"] youtube = "" -vimeo = "" +vimeo = "625214571" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/olowoniwa-gabriel-ayokunle.md b/content/events/2021-zurich/program/olowoniwa-gabriel-ayokunle.md index 44aad613930..519ca146c52 100644 --- a/content/events/2021-zurich/program/olowoniwa-gabriel-ayokunle.md +++ b/content/events/2021-zurich/program/olowoniwa-gabriel-ayokunle.md @@ -4,11 +4,11 @@ Year = "2021" talk_date = "2021-09-07" talk_start_time = "11:30" talk_end_time = "12:00" -title = "Why dread the science of hacking?" +title = "Serverless Trends in 2021" type = "talk" -speakers = ["olowoniwa-gabriel-ayokunle"] +speakers = ["daniel-maher"] youtube = "" -vimeo = "" +vimeo = "625707002" speakerdeck = "" slideshare = "" slides = "" @@ -16,9 +16,3 @@ slides = "" ### Talk -why hack into something when you could just ask for access? Undetectable by firewalls and antivirus software, social engineering relies on human fault to gain access to sensitive spaces; - -Every big organization has a layer by layer defense of data. If all the controls are well placed and active, then also it is vulnerable. One of the biggest failures in this is either you can bypass the controls or start penetrating the layers. Once you penetrate the first layer successfully, the next layer will be easier. Most of the defense mechanisms fail because of Human error or Social Engineering which brings about the conclusion “Human is the weakest chain in security”. - -Let’s focus a little bit on hackers, many view us with the power to hack anything in mere seconds. While that is frequently true on websites due to how cruddy things are programmed, things are getting better. -At the end of this session, I would have successfully explained the science of hacking, misconceptions of hacking, and finally, a quick demo on how the best developers can be victims of hacking. \ No newline at end of file diff --git a/content/events/2021-zurich/program/pj-hagerty.md b/content/events/2021-zurich/program/pj-hagerty.md index 5f1de33f8ea..113cfba5808 100644 --- a/content/events/2021-zurich/program/pj-hagerty.md +++ b/content/events/2021-zurich/program/pj-hagerty.md @@ -8,7 +8,7 @@ title = "DevOps - Philosophy vs Practice" type = "talk" speakers = ["pj-hagerty"] youtube = "" -vimeo = "" +vimeo = "625699929" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/quintessence-anx.md b/content/events/2021-zurich/program/quintessence-anx.md index 5323a3682b8..7264a59ed16 100644 --- a/content/events/2021-zurich/program/quintessence-anx.md +++ b/content/events/2021-zurich/program/quintessence-anx.md @@ -8,7 +8,7 @@ title = "Unquantified Serendipity: Diversity in Development" type = "talk" speakers = ["quintessence-anx"] youtube = "" -vimeo = "" +vimeo = "625712710" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/sebastien-goasguen.md b/content/events/2021-zurich/program/sebastien-goasguen.md index 58fcf1d9b1a..7d039569057 100644 --- a/content/events/2021-zurich/program/sebastien-goasguen.md +++ b/content/events/2021-zurich/program/sebastien-goasguen.md @@ -8,7 +8,7 @@ title = "DevOps in a Cloud-Native World" type = "talk" speakers = ["sebastien-goasguen"] youtube = "" -vimeo = "" +vimeo = "625695076" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/stacy-cashmore.md b/content/events/2021-zurich/program/stacy-cashmore.md index 3ba0699c7fc..b15e90acfc2 100644 --- a/content/events/2021-zurich/program/stacy-cashmore.md +++ b/content/events/2021-zurich/program/stacy-cashmore.md @@ -8,7 +8,7 @@ title = "How to really work as a team - from sleepy to strong pair programming" type = "talk" speakers = ["stacy-cashmore"] youtube = "" -vimeo = "" +vimeo = "625700777" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/program/tobias-hauk.md b/content/events/2021-zurich/program/tobias-hauk.md index 97b7816edb7..50fc09a5472 100644 --- a/content/events/2021-zurich/program/tobias-hauk.md +++ b/content/events/2021-zurich/program/tobias-hauk.md @@ -8,7 +8,7 @@ title = "Why & How the Evolution of Employee Feedback Matters for Everybody" type = "talk" speakers = ["tobias-hauk"] youtube = "" -vimeo = "" +vimeo = "625191800" speakerdeck = "" slideshare = "" slides = "" diff --git a/content/events/2021-zurich/welcome.md b/content/events/2021-zurich/welcome.md index 5ab87c657ea..11ecac8504b 100644 --- a/content/events/2021-zurich/welcome.md +++ b/content/events/2021-zurich/welcome.md @@ -20,9 +20,12 @@ Description = "DevOpsDays Zürich 2021" -
Welcome to the fourth round of DevOpsDays 2021! +
DevOps Days 2021 was great. Check out the photos and videos! +
Photos +
Videos +

First time here? Check out our last events and get hyped!

diff --git a/content/events/2022-aarhus/conduct-fr.md b/content/events/2022-aarhus/conduct-fr.md new file mode 100644 index 00000000000..9e84aa25d11 --- /dev/null +++ b/content/events/2022-aarhus/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays Aarhus 2022" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays Aarhus 2022 doivent accepter le code d'éthique et de déontologie, ou « code de conduite » suivant. Les organisateurs s’attacheront à faire respecter ce code durant l’événement. Nous attendons la coopération de chacun‧e pour assurer un environnement sain pour tous. + + +### La Version Rapide + +Notre conférence tient à être une expérience sans harcèlement pour tous, quel que soit votre sexe, votre identité sexuelle, votre âge, votre orientation sexuelle, votre handicap, votre apparence physique, votre poids, votre race, votre ethnie, votre religion (ou absence de religion), ou vos choix technologiques. + +Nous ne tolérons aucun harcèlement des participant‧e‧s à la conférence, sous quelque forme que ce soit, quelles qu’en soient les circonstances. Les expressions et les images à connotation sexuelle ne sont pas appropriées lors de l'événement. Ceci inclut les conférences, les ateliers, les soirées, Twitter et les autres médias en ligne. + +L'organisation s'engage à prendre des sanctions appropriées pour les personnes qui violent ces règles, jusqu'à l'exclusion sans remboursement et le recours légal. + + +### La Version Moins Rapide + +Le harcèlement comprend les commentaires à l'oral ou à l'écrit ainsi que les gestes offensants sur le sexe, l'identité sexuelle, l'âge, l'orientation sexuelle, le handicap, l'apparence physique, le poids, la race, l'ethnie, la religion, les choix technologiques, les images à connotation sexuelle dans des lieux publics, les intimidations délibérées, la traque, la poursuite, un harcèlement photographique ou vidéo, une suite d'interruptions des conférences et des autres sessions, un contact physique inapproprié et des avances sexuelles non désirées. sans son consentement ou à son insu. + +Les participant‧e‧s à qui il sera demandé d'arrêter tout comportement de harcèlement doivent arrêter immédiatement. + +Les sponsors sont aussi sujet à la politique anti-harcèlement. En particulier, les sponsors ne doivent pas utiliser d'images ou de supports à connotation sexuelle. Ils ne doivent pas non plus se livrer à des activités à connotation sexuelle. L'équipe du stand (y compris les bénévoles) ne doit pas utiliser de vêtements, uniformes ou costumes à connotation sexuelle. Ils ne doivent pas non plus créer un environnement sexualisé. + +Face à un comportement de harcèlement, l'équipe d'organisation de la conférence peut prendre toute action qui lui semble adéquate. Cela va d'un simple avertissement à l'exclusion sans remboursement de la conférence. + +Si vous vous sentez harcelé‧e, si vous pensez que quelqu'un se fait harceler, et plus généralement en cas de problème, merci de contacter immédiatement l’équipe d’organisation de l'événement. + +Les membres de l'organisation sont facilement identifiables grâce à un badge "STAFF". Les membres de l'organisation seront ravi‧e‧s d'aider les participants à contacter la sécurité de l'événement, ou les forces de l'ordre ; à fournir une escorte ainsi qu'à aider de toute autre façon les personnes victimes de harcèlement, pour garantir leur sécurité pendant la durée de l'événement. Nous apprécions votre participation à l'événement. + +Nous attendons de chacun‧e le respect de ces règles dans le bâtiment des conférences et des ateliers, ainsi que pendant les événements sociaux relatifs à la conférence. + + + +Le code de conduite devopsdays Aarhus 2022 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2022-aarhus/conduct-pt-br.md b/content/events/2022-aarhus/conduct-pt-br.md new file mode 100755 index 00000000000..e6e6a3c7de5 --- /dev/null +++ b/content/events/2022-aarhus/conduct-pt-br.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do devopsdays Aarhus 2022" ++++ + + +Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays Aarhus 2022 são requeridos a concordar com o seguinte código de conduta. A organização irá aplicar este código pelo evento. Nós esperamos cooperação de todas as pessoas participando para garantir um ambiente seguro para todas as pessoas. + +### A versão rápida + +Nossa conferência é dedicada a prover um uma experiência de conferência sem assédio para todos, independente de gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias. Nós não toleramos assédio de participantes da conferência de qualquer forma. Linguagem e imagens sexuais não são apropriadas em nenhum local, incluindo palestras, workshops, festas, Twitter e outras mídias online. Violações destas regras poderão causar expulsão da conferência, sem reembolso a critério da equipe organizadora. + +### A versão não tão rápida + +Assédio inclui comentários verbais ofensivos relacionados a gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias, imagens sexuais em espaços públicos, intimidação deliberada, stalking, perseguição, fotografias ou filmagens constrangedoras, interrupção contínua das apresentações ou outros eventos, contato físico inapropriado e atenção sexual indesejada. Participantes que receberem uma solicitação para interromper qualquer comportamento de assédio devem fazer isso imediatamente. + +As políticas antiassédio também se aplicam a representantes de empresas patrocinadoras. Em particular, não devem usar imagens, atividades ou outro material de cunho sexual. As equipes de estandes e tendas (incluindo pessoas voluntárias) não devem utilizar roupas, uniformes ou trajes sexualizados ou criar um ambiente sexualizado de quaisquer formas. + +Se alguém se envolver em comportamento de assédio, a equipe organizadora pode tomar qualquer ação que considerar apropriada, incluindo avisar a pessoa ofensora ou expulsá-la da conferência sem reembolso. + +Se você estiver sofrendo assédio, notar que alguém está sofrendo assédio, ou tenha alguma dúvida, por favor contate alguém da organização imediatamente. + +As pessoas da equipe da conferência podem ser identificadas por crachás distintos da organização. A organização estará disposta a contatar a segurança do hotel/local ou a polícia local, fornecer escolta ou ajudar pessoas que sofrerem assédio para que se sintam seguras durante a conferência. Nós valorizamos a sua participação. + +Esperamos que todas as pessoas participantes sigam estas regras em salas de apresentação e workshops da conferência, além de eventos sociais relacionados. + +_O código de conduta do devopsdays Aarhus 2022 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._ diff --git a/content/events/2022-aarhus/conduct.md b/content/events/2022-aarhus/conduct.md new file mode 100644 index 00000000000..14c6dcd34bb --- /dev/null +++ b/content/events/2022-aarhus/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Aarhus 2022" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Aarhus 2022 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. + +### The Quick Version + +Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. + +### The Less Quick Version + +Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. + +Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. + +Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +_The devopsdays Aarhus 2022 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2022-aarhus/contact.md b/content/events/2022-aarhus/contact.md new file mode 100644 index 00000000000..488aba866bf --- /dev/null +++ b/content/events/2022-aarhus/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Aarhus 2022" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2022-aarhus/location.md b/content/events/2022-aarhus/location.md new file mode 100644 index 00000000000..e5ee53a66c9 --- /dev/null +++ b/content/events/2022-aarhus/location.md @@ -0,0 +1,22 @@ ++++ +Title = "Location for devopsdays Aarhus 2022" +Type = "event" +Description = " " ++++ + + +

The event will be held at Aarhus International Sailing Center (Sejlsportcentret), with a relaxing atmosphere, beautifully located right by the sea.

+

+Limited places available. Secure your ticket today! + +

+
+ + + + + diff --git a/content/events/2022-aarhus/propose.md b/content/events/2022-aarhus/propose.md new file mode 100644 index 00000000000..8b794a2314e --- /dev/null +++ b/content/events/2022-aarhus/propose.md @@ -0,0 +1,30 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Aarhus 2022" ++++ + {{< cfp_dates >}} + +

+ +There are three ways to propose a topic at devopsdays: +
    +
  1. A 30-minute talk presented during the conference, usually in the mornings.
    2. +
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table. +
+ +
+ +Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience: + +- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. +- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. +- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience. +- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen. +- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. +- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. + +
+ +How to submit a proposal: Go to our CFP at Papercall. diff --git a/content/events/2022-aarhus/registration.md b/content/events/2022-aarhus/registration.md new file mode 100644 index 00000000000..0001e98e855 --- /dev/null +++ b/content/events/2022-aarhus/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Aarhus 2022" ++++ + +
+ +Embed registration iframe/link/etc. +
+
diff --git a/content/events/2022-aarhus/sponsor.md b/content/events/2022-aarhus/sponsor.md new file mode 100644 index 00000000000..e899c90c39d --- /dev/null +++ b/content/events/2022-aarhus/sponsor.md @@ -0,0 +1,66 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Aarhus 2022" ++++ + +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. + +
+ +devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. +

+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. +

+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. +

+ + +

diff --git a/content/events/2022-aarhus/welcome.md b/content/events/2022-aarhus/welcome.md new file mode 100644 index 00000000000..833d26695a7 --- /dev/null +++ b/content/events/2022-aarhus/welcome.md @@ -0,0 +1,77 @@ ++++ +Title = "devopsdays Aarhus 2022" +Type = "welcome" +aliases = ["/events/2022-aarhus/"] +Description = "devopsdays Aarhus 2022" ++++ + + + +
+
+

We’re proud to announce that Devopsdays is officially coming to Aarhus, Denmark.

+

Delayed due to the pandemic, we look forward to welcoming the local DevOps scene, inspiring speakers and our sponsors, to a great event. And we have selected a really cool venue, too. + +

Limited seats available, so sign up today! + +

+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ +
+
+ Price +
+
+ 1,799 DKK(excl tax) +
+
+ +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ +
+
+ Venue +
+
+ Aarhus International Sailing Center / Sejlsportscentret Aarhus +
+
+ +

+ +

Already bought a ticket before the pandemic?

+Congratulations! Your ticket is still valid, so you don’t have to do anything. +
+
+
+ {{< event_logo >}} +
+
+
+ + + + + diff --git a/content/events/2022-amsterdam/sponsor.md b/content/events/2022-amsterdam/sponsor.md index 98cab6e41eb..4051a1d3817 100644 --- a/content/events/2022-amsterdam/sponsor.md +++ b/content/events/2022-amsterdam/sponsor.md @@ -4,63 +4,28 @@ Type = "event" Description = "Sponsor devopsdays Amsterdam 2022" +++ -We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. +
+

devopsdays is made possible by our sponsors. If you are interested in joining our band of supporters, please drop us an email at [{{< email_organizers >}}].

+ +
-devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. +devopsdays is a conference organized by volunteers, and depends on sponsorships. We do not have badge scanners, sell keynote slots, nor do we distribute attendee contact lists. However, sponsors have the opportunity to deliver an elevator pitch during the main program, and will get recognition on the website and on social media before, during and after the event. Certain sponsor levels also include a table in the exhibition area of the venue. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees in the chat. Like any other attendee, sponsors have the opportunity to demo products/projects as part of an Open Space session.

-Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. + Hot tip: encourage your engineers to participate in, and interact with the attendees and experts at devopsdays. The in-person devopsdays Amsterdam conference typically attracts around 500 participants.

-The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. -

- + -

diff --git a/content/events/2022-birmingham-uk/conduct-fr.md b/content/events/2022-birmingham-uk/conduct-fr.md new file mode 100644 index 00000000000..83ce364fb0a --- /dev/null +++ b/content/events/2022-birmingham-uk/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays birmingham 2022" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays birmingham 2022 doivent accepter le code d'éthique et de déontologie, ou « code de conduite » suivant. Les organisateurs s’attacheront à faire respecter ce code durant l’événement. Nous attendons la coopération de chacun‧e pour assurer un environnement sain pour tous. + + +### La Version Rapide + +Notre conférence tient à être une expérience sans harcèlement pour tous, quel que soit votre sexe, votre identité sexuelle, votre âge, votre orientation sexuelle, votre handicap, votre apparence physique, votre poids, votre race, votre ethnie, votre religion (ou absence de religion), ou vos choix technologiques. + +Nous ne tolérons aucun harcèlement des participant‧e‧s à la conférence, sous quelque forme que ce soit, quelles qu’en soient les circonstances. Les expressions et les images à connotation sexuelle ne sont pas appropriées lors de l'événement. Ceci inclut les conférences, les ateliers, les soirées, Twitter et les autres médias en ligne. + +L'organisation s'engage à prendre des sanctions appropriées pour les personnes qui violent ces règles, jusqu'à l'exclusion sans remboursement et le recours légal. + + +### La Version Moins Rapide + +Le harcèlement comprend les commentaires à l'oral ou à l'écrit ainsi que les gestes offensants sur le sexe, l'identité sexuelle, l'âge, l'orientation sexuelle, le handicap, l'apparence physique, le poids, la race, l'ethnie, la religion, les choix technologiques, les images à connotation sexuelle dans des lieux publics, les intimidations délibérées, la traque, la poursuite, un harcèlement photographique ou vidéo, une suite d'interruptions des conférences et des autres sessions, un contact physique inapproprié et des avances sexuelles non désirées. sans son consentement ou à son insu. + +Les participant‧e‧s à qui il sera demandé d'arrêter tout comportement de harcèlement doivent arrêter immédiatement. + +Les sponsors sont aussi sujet à la politique anti-harcèlement. En particulier, les sponsors ne doivent pas utiliser d'images ou de supports à connotation sexuelle. Ils ne doivent pas non plus se livrer à des activités à connotation sexuelle. L'équipe du stand (y compris les bénévoles) ne doit pas utiliser de vêtements, uniformes ou costumes à connotation sexuelle. Ils ne doivent pas non plus créer un environnement sexualisé. + +Face à un comportement de harcèlement, l'équipe d'organisation de la conférence peut prendre toute action qui lui semble adéquate. Cela va d'un simple avertissement à l'exclusion sans remboursement de la conférence. + +Si vous vous sentez harcelé‧e, si vous pensez que quelqu'un se fait harceler, et plus généralement en cas de problème, merci de contacter immédiatement l’équipe d’organisation de l'événement. + +Les membres de l'organisation sont facilement identifiables grâce à un badge "STAFF". Les membres de l'organisation seront ravi‧e‧s d'aider les participants à contacter la sécurité de l'événement, ou les forces de l'ordre ; à fournir une escorte ainsi qu'à aider de toute autre façon les personnes victimes de harcèlement, pour garantir leur sécurité pendant la durée de l'événement. Nous apprécions votre participation à l'événement. + +Nous attendons de chacun‧e le respect de ces règles dans le bâtiment des conférences et des ateliers, ainsi que pendant les événements sociaux relatifs à la conférence. + + + +Le code de conduite devopsdays birmingham 2022 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2022-birmingham-uk/conduct-pt-br.md b/content/events/2022-birmingham-uk/conduct-pt-br.md new file mode 100755 index 00000000000..95efb6f1705 --- /dev/null +++ b/content/events/2022-birmingham-uk/conduct-pt-br.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do devopsdays birmingham 2022" ++++ + + +Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays birmingham 2022 são requeridos a concordar com o seguinte código de conduta. A organização irá aplicar este código pelo evento. Nós esperamos cooperação de todas as pessoas participando para garantir um ambiente seguro para todas as pessoas. + +### A versão rápida + +Nossa conferência é dedicada a prover um uma experiência de conferência sem assédio para todos, independente de gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias. Nós não toleramos assédio de participantes da conferência de qualquer forma. Linguagem e imagens sexuais não são apropriadas em nenhum local, incluindo palestras, workshops, festas, Twitter e outras mídias online. Violações destas regras poderão causar expulsão da conferência, sem reembolso a critério da equipe organizadora. + +### A versão não tão rápida + +Assédio inclui comentários verbais ofensivos relacionados a gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias, imagens sexuais em espaços públicos, intimidação deliberada, stalking, perseguição, fotografias ou filmagens constrangedoras, interrupção contínua das apresentações ou outros eventos, contato físico inapropriado e atenção sexual indesejada. Participantes que receberem uma solicitação para interromper qualquer comportamento de assédio devem fazer isso imediatamente. + +As políticas antiassédio também se aplicam a representantes de empresas patrocinadoras. Em particular, não devem usar imagens, atividades ou outro material de cunho sexual. As equipes de estandes e tendas (incluindo pessoas voluntárias) não devem utilizar roupas, uniformes ou trajes sexualizados ou criar um ambiente sexualizado de quaisquer formas. + +Se alguém se envolver em comportamento de assédio, a equipe organizadora pode tomar qualquer ação que considerar apropriada, incluindo avisar a pessoa ofensora ou expulsá-la da conferência sem reembolso. + +Se você estiver sofrendo assédio, notar que alguém está sofrendo assédio, ou tenha alguma dúvida, por favor contate alguém da organização imediatamente. + +As pessoas da equipe da conferência podem ser identificadas por crachás distintos da organização. A organização estará disposta a contatar a segurança do hotel/local ou a polícia local, fornecer escolta ou ajudar pessoas que sofrerem assédio para que se sintam seguras durante a conferência. Nós valorizamos a sua participação. + +Esperamos que todas as pessoas participantes sigam estas regras em salas de apresentação e workshops da conferência, além de eventos sociais relacionados. + +_O código de conduta do devopsdays birmingham 2022 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._ diff --git a/content/events/2022-birmingham-uk/conduct.md b/content/events/2022-birmingham-uk/conduct.md new file mode 100644 index 00000000000..032fd130519 --- /dev/null +++ b/content/events/2022-birmingham-uk/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays birmingham 2022" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays birmingham 2022 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. + +### The Quick Version + +Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. + +### The Less Quick Version + +Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. + +Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. + +Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +_The devopsdays birmingham 2022 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2022-birmingham-uk/contact.md b/content/events/2022-birmingham-uk/contact.md new file mode 100644 index 00000000000..cb6bfba9473 --- /dev/null +++ b/content/events/2022-birmingham-uk/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays birmingham 2022" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2022-birmingham-uk/location.md b/content/events/2022-birmingham-uk/location.md new file mode 100644 index 00000000000..37a4a579713 --- /dev/null +++ b/content/events/2022-birmingham-uk/location.md @@ -0,0 +1,17 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays birmingham 2022" ++++ + +Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details. + + + + + + diff --git a/content/events/2022-birmingham-uk/propose.md b/content/events/2022-birmingham-uk/propose.md new file mode 100644 index 00000000000..409773bada3 --- /dev/null +++ b/content/events/2022-birmingham-uk/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays birmingham 2022" ++++ + {{< cfp_dates >}} + +
+ +There are three ways to propose a topic at devopsdays: +
    +
  1. A 30-minute talk presented during the conference, usually in the mornings.
    2. +
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table. +
+ +
+ +Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience: + +- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. +- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. +- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience. +- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen. +- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. +- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. + +
+ +How to submit a proposal: Send an email to [{{< email_organizers >}}] with the following information +
    +
  1. Type (presentation, panel discussion, ignite)
    2. +
  2. Proposal Title (can be changed later)
    3. +
  3. Description (several sentences explaining what attendees will learn)
    4. +
diff --git a/content/events/2022-birmingham-uk/registration.md b/content/events/2022-birmingham-uk/registration.md new file mode 100644 index 00000000000..fda5dda0b82 --- /dev/null +++ b/content/events/2022-birmingham-uk/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays birmingham 2022" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2022-birmingham-uk/sponsor.md b/content/events/2022-birmingham-uk/sponsor.md new file mode 100644 index 00000000000..3c8b0f7f489 --- /dev/null +++ b/content/events/2022-birmingham-uk/sponsor.md @@ -0,0 +1,67 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays birmingham 2022" ++++ + +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. + +
+ +devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. + +

+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. +

+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. +

+ + +

diff --git a/content/events/2022-birmingham-uk/welcome.md b/content/events/2022-birmingham-uk/welcome.md new file mode 100644 index 00000000000..5533c836283 --- /dev/null +++ b/content/events/2022-birmingham-uk/welcome.md @@ -0,0 +1,42 @@ ++++ +Title = "DevOpsDays Birmingham, UK 2022" +Type = "welcome" +aliases = ["/events/2022-birmingham-uk/"] +Description = "devopsdays birmingham, uk 2022" ++++ + + + +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ + + diff --git a/content/events/2022-boise/conduct-fr.md b/content/events/2022-boise/conduct-fr.md new file mode 100644 index 00000000000..97bf455312e --- /dev/null +++ b/content/events/2022-boise/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays Boise 2022" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays Boise 2022 doivent accepter le code d'éthique et de déontologie, ou « code de conduite » suivant. Les organisateurs s’attacheront à faire respecter ce code durant l’événement. Nous attendons la coopération de chacun‧e pour assurer un environnement sain pour tous. + + +### La Version Rapide + +Notre conférence tient à être une expérience sans harcèlement pour tous, quel que soit votre sexe, votre identité sexuelle, votre âge, votre orientation sexuelle, votre handicap, votre apparence physique, votre poids, votre race, votre ethnie, votre religion (ou absence de religion), ou vos choix technologiques. + +Nous ne tolérons aucun harcèlement des participant‧e‧s à la conférence, sous quelque forme que ce soit, quelles qu’en soient les circonstances. Les expressions et les images à connotation sexuelle ne sont pas appropriées lors de l'événement. Ceci inclut les conférences, les ateliers, les soirées, Twitter et les autres médias en ligne. + +L'organisation s'engage à prendre des sanctions appropriées pour les personnes qui violent ces règles, jusqu'à l'exclusion sans remboursement et le recours légal. + + +### La Version Moins Rapide + +Le harcèlement comprend les commentaires à l'oral ou à l'écrit ainsi que les gestes offensants sur le sexe, l'identité sexuelle, l'âge, l'orientation sexuelle, le handicap, l'apparence physique, le poids, la race, l'ethnie, la religion, les choix technologiques, les images à connotation sexuelle dans des lieux publics, les intimidations délibérées, la traque, la poursuite, un harcèlement photographique ou vidéo, une suite d'interruptions des conférences et des autres sessions, un contact physique inapproprié et des avances sexuelles non désirées. sans son consentement ou à son insu. + +Les participant‧e‧s à qui il sera demandé d'arrêter tout comportement de harcèlement doivent arrêter immédiatement. + +Les sponsors sont aussi sujet à la politique anti-harcèlement. En particulier, les sponsors ne doivent pas utiliser d'images ou de supports à connotation sexuelle. Ils ne doivent pas non plus se livrer à des activités à connotation sexuelle. L'équipe du stand (y compris les bénévoles) ne doit pas utiliser de vêtements, uniformes ou costumes à connotation sexuelle. Ils ne doivent pas non plus créer un environnement sexualisé. + +Face à un comportement de harcèlement, l'équipe d'organisation de la conférence peut prendre toute action qui lui semble adéquate. Cela va d'un simple avertissement à l'exclusion sans remboursement de la conférence. + +Si vous vous sentez harcelé‧e, si vous pensez que quelqu'un se fait harceler, et plus généralement en cas de problème, merci de contacter immédiatement l’équipe d’organisation de l'événement. + +Les membres de l'organisation sont facilement identifiables grâce à un badge "STAFF". Les membres de l'organisation seront ravi‧e‧s d'aider les participants à contacter la sécurité de l'événement, ou les forces de l'ordre ; à fournir une escorte ainsi qu'à aider de toute autre façon les personnes victimes de harcèlement, pour garantir leur sécurité pendant la durée de l'événement. Nous apprécions votre participation à l'événement. + +Nous attendons de chacun‧e le respect de ces règles dans le bâtiment des conférences et des ateliers, ainsi que pendant les événements sociaux relatifs à la conférence. + + + +Le code de conduite devopsdays Boise 2022 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2022-boise/conduct-pt-br.md b/content/events/2022-boise/conduct-pt-br.md new file mode 100755 index 00000000000..861fe246d82 --- /dev/null +++ b/content/events/2022-boise/conduct-pt-br.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do devopsdays Boise 2022" ++++ + + +Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays Boise 2022 são requeridos a concordar com o seguinte código de conduta. A organização irá aplicar este código pelo evento. Nós esperamos cooperação de todas as pessoas participando para garantir um ambiente seguro para todas as pessoas. + +### A versão rápida + +Nossa conferência é dedicada a prover um uma experiência de conferência sem assédio para todos, independente de gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias. Nós não toleramos assédio de participantes da conferência de qualquer forma. Linguagem e imagens sexuais não são apropriadas em nenhum local, incluindo palestras, workshops, festas, Twitter e outras mídias online. Violações destas regras poderão causar expulsão da conferência, sem reembolso a critério da equipe organizadora. + +### A versão não tão rápida + +Assédio inclui comentários verbais ofensivos relacionados a gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias, imagens sexuais em espaços públicos, intimidação deliberada, stalking, perseguição, fotografias ou filmagens constrangedoras, interrupção contínua das apresentações ou outros eventos, contato físico inapropriado e atenção sexual indesejada. Participantes que receberem uma solicitação para interromper qualquer comportamento de assédio devem fazer isso imediatamente. + +As políticas antiassédio também se aplicam a representantes de empresas patrocinadoras. Em particular, não devem usar imagens, atividades ou outro material de cunho sexual. As equipes de estandes e tendas (incluindo pessoas voluntárias) não devem utilizar roupas, uniformes ou trajes sexualizados ou criar um ambiente sexualizado de quaisquer formas. + +Se alguém se envolver em comportamento de assédio, a equipe organizadora pode tomar qualquer ação que considerar apropriada, incluindo avisar a pessoa ofensora ou expulsá-la da conferência sem reembolso. + +Se você estiver sofrendo assédio, notar que alguém está sofrendo assédio, ou tenha alguma dúvida, por favor contate alguém da organização imediatamente. + +As pessoas da equipe da conferência podem ser identificadas por crachás distintos da organização. A organização estará disposta a contatar a segurança do hotel/local ou a polícia local, fornecer escolta ou ajudar pessoas que sofrerem assédio para que se sintam seguras durante a conferência. Nós valorizamos a sua participação. + +Esperamos que todas as pessoas participantes sigam estas regras em salas de apresentação e workshops da conferência, além de eventos sociais relacionados. + +_O código de conduta do devopsdays Boise 2022 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._ diff --git a/content/events/2022-boise/conduct.md b/content/events/2022-boise/conduct.md new file mode 100644 index 00000000000..c1b0bdf0f01 --- /dev/null +++ b/content/events/2022-boise/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Boise 2022" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Boise 2022 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. + +### The Quick Version + +Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. + +### The Less Quick Version + +Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. + +Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. + +Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +_The devopsdays Boise 2022 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2022-boise/contact.md b/content/events/2022-boise/contact.md new file mode 100644 index 00000000000..1ce5f0b3023 --- /dev/null +++ b/content/events/2022-boise/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Boise 2022" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2022-boise/location.md b/content/events/2022-boise/location.md new file mode 100644 index 00000000000..435394ca702 --- /dev/null +++ b/content/events/2022-boise/location.md @@ -0,0 +1,17 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays Boise 2021" ++++ + + + + + + + + diff --git a/content/events/2022-boise/propose.md b/content/events/2022-boise/propose.md new file mode 100644 index 00000000000..f473e30896e --- /dev/null +++ b/content/events/2022-boise/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Boise 2022" ++++ + {{< cfp_dates >}} + +
+ +There are three ways to propose a topic at devopsdays: +
    +
  1. A 30-minute talk presented during the conference, usually in the mornings.
    2. +
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table. +
+ +
+ +Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience: + +- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. +- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. +- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience. +- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen. +- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. +- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. + +
+ +How to submit a proposal: Send an email to [{{< email_organizers >}}] with the following information +
    +
  1. Type (presentation, panel discussion, ignite)
    2. +
  2. Proposal Title (can be changed later)
    3. +
  3. Description (several sentences explaining what attendees will learn)
    4. +
diff --git a/content/events/2022-boise/registration.md b/content/events/2022-boise/registration.md new file mode 100644 index 00000000000..b9320fa0942 --- /dev/null +++ b/content/events/2022-boise/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Boise 2022" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2022-boise/sponsor.md b/content/events/2022-boise/sponsor.md new file mode 100644 index 00000000000..99c3ee73765 --- /dev/null +++ b/content/events/2022-boise/sponsor.md @@ -0,0 +1,66 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Boise 2022" ++++ + +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. + +
+ +devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. +

+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. +

+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. +

+ + +

diff --git a/content/events/2022-boise/welcome.md b/content/events/2022-boise/welcome.md new file mode 100644 index 00000000000..e96dc83a397 --- /dev/null +++ b/content/events/2022-boise/welcome.md @@ -0,0 +1,86 @@ ++++ +Title = "devopsdays Boise 2022" +Type = "welcome" +aliases = ["/events/2022-boise/"] +Description = "devopsdays Boise 2022" ++++ + + + +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ + + + + + + + + + + +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ + +{{< event_twitter >}} + diff --git a/content/events/2022-cairo/conduct.md b/content/events/2022-cairo/conduct.md new file mode 100644 index 00000000000..15647f28a92 --- /dev/null +++ b/content/events/2022-cairo/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Cairo 2022" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Cairo 2022 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. + +### The Quick Version + +Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. + +### The Less Quick Version + +Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. + +Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. + +Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +_The devopsdays Cairo 2022 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2022-cairo/contact.md b/content/events/2022-cairo/contact.md new file mode 100644 index 00000000000..8e49219fada --- /dev/null +++ b/content/events/2022-cairo/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact us" +Type = "event" +Description = "Contact information for devopsdays Cairo 2022" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2022-cairo/local.md b/content/events/2022-cairo/local.md new file mode 100644 index 00000000000..4448ec3ec8e --- /dev/null +++ b/content/events/2022-cairo/local.md @@ -0,0 +1,7 @@ ++++ +Title = "Cairo" +Type = "event" +Description = "About Cairo" ++++ + +Cairo (al-Qāhirah) is the capital of Egypt, located near the [Nile Delta](https://en.wikipedia.org/wiki/Nile_Delta "Nile Delta").  The city's metropolitan area is one of the largest in Africa, the Middle East and the Arab world, and the 15th-largest in the world.  It is associated with ancient Egypt, as the famous Giza pyramid complex and the ancient city of Memphis are located in its geographical area. diff --git a/content/events/2022-cairo/sponsor.md b/content/events/2022-cairo/sponsor.md new file mode 100644 index 00000000000..b1982c31ebd --- /dev/null +++ b/content/events/2022-cairo/sponsor.md @@ -0,0 +1,8 @@ ++++ +Title = "Sponsor the event!" +Type = "event" +Description = "Sponsor devopsdays Cairo 2022" ++++ + + +

We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].

diff --git a/content/events/2022-cairo/welcome.md b/content/events/2022-cairo/welcome.md new file mode 100644 index 00000000000..a0d0a0731d6 --- /dev/null +++ b/content/events/2022-cairo/welcome.md @@ -0,0 +1,95 @@ ++++ +Title = "Welcome to DevOpsDays Cairo 2022" +Type = "welcome" +aliases = ["/events/2022-cairo/"] +Description = "DevOpsDays Cairo 2022" ++++ +
+

DevOpsDays Cairo is a one-day event.
For the 5th consecutive year, SECC/ITIDA are organizing DevOpsDays Cairo 2022 in cooperation with ATOS, DXC Technology and Orange Labs.

+
+
+

Just "Like" our Facebook page, adjust your calender/notifications, and stay tuned!

+
+

+ + +
+ {{< event_logo >}} +
+ +
+
+ Dates +
+
+ {{< event_start >}} +
+
+ + + + + + + + + + + +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ + + diff --git a/content/events/2022-chicago/propose.md b/content/events/2022-chicago/propose.md index c2a0e53f10f..13d723dc55c 100644 --- a/content/events/2022-chicago/propose.md +++ b/content/events/2022-chicago/propose.md @@ -1,35 +1,79 @@ +++ Title = "Propose" Type = "event" -Description = "Propose a talk for devopsdays Chicago 2022" +Description = "Propose a talk for devopsdays Chicago 2019" +++ {{< cfp_dates >}}
-There are three ways to propose a topic at devopsdays: +There are four ways to propose a topic at devopsdays:
    -
  1. A 30-minute talk presented during the conference, usually in the mornings.
    2. -
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. A 30-minute talk presented to the entire conference audience, usually in the mornings.
    4. +
  4. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes talks with slides auto-advancing every 15 seconds (20 slides total).
    5. +
  5. A Workshop presented during the conference, usually in the afternoon. These are 45 minutes long.
  6. Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table.
-Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience: +### General Guidelines: -- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. -- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. -- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience. -- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen. -- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. -- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. +- Be concise, but include as much detail as is necessary to convey your idea. +- Please provide at least three concrete takeaways that the audience will get from your talk +- Multiple entries are welcome. +- Submissions must be made by one of the proposed presenters; **we do not accept proposals submitted on behalf of others** +- All presentations must conform to the code of conduct. +- Proposals must be submitted via [our CFP site](https://sessionize.com/devopsdays-chicago-2022/). If you have questions about our CFP process, please email: [{{< email_organizers >}}] + +### Ideas: +This is what we would like to know. Do you have an answer? + +- The DevOps movement has been around for a few years now: Has it really helped your organization? Are there numbers for this? +- Did the culture of DevOps spread to other parts of your company? If not, why? +- Is DevOps the magic silver bullet which solved all your problems? What are the problems it didn’t solve (although you thought it would)? +- Was there one tool or methodology in particular that was key to your organization's DevOps transformation? Tell us about the role it played and how it moved the needle. +- Were there unexpected problems during your cultural change into DevOps? +- Did the required skill-set of people change after starting to do things DevOps-Style? +- Did people leave because you “went DevOps”? Was this good or bad or both? +- Have there been technical changes after the culture in your team changed? +- Did the change affect the business/sales/marketing side? +- And of course: Has DevOps affected you personally? How do you feel about the change it brought to your work? + +The “classic” DevOps questions are of course not fully answered, either… + +- What is the role of QA/Tester in DevOps, how do we integrate QA in the continuous delivery process +- The impact DevOps has on traditional security/auditing/change control +- The impact of DevOps on HR policies, and the hiring process +- Help prove that DevOps can scale beyond the 5-8 person web startups, we love traditional IT enterprise cases +- With all the automation, data is still a hard thing to handle, how does it affect DBA’s, backup strategies, … + +If you’d like some more specific topic examples… + +- How about release management. +- Integrating security into the DevOps conversation +- How to handle budgets for DevOps initiatives +- DevOps and Working Remotely +- Value Stream Mapping +- Having DevOps make #monitoringsucks less + +Our main criteria to make it to the top selection are: + +- **Broad appeal:** How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. +- **New local presenters:** You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. +- **Under-represented voices:** We want to hear all voices, including those that may speak less frequently at similar events. Whether you’re in a field not typically thought of as a technology field, you’re in a large, traditional organization, or you’re the only person at your organization with your background, we are interested in your unique experience. +- **original content:** We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn’t likely to have already seen. +- **No third-party submissions:** This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you’ve already shown that as a speaker you’re distant from the process. +- **No vendor pitches:** As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. If you’d like to demo your product or service, you should sponsor the event and demo it at your table. +- **Open Space Fodder:** Will this talk help generate discussion during the Open Spaces? + +#### Even more tips + +- We like stories over theory. Examples of what your organization has done are fantastic. +- You don’t need to write out the entire talk in your abstract, but please provide sufficient detail for the selection committee to get a feel for what your talk will include. Show, don’t tell. +- Remember that this is a single-track conference - getting too deep into the weeds of a specific technology might make the content less accessible to all attendees. However, we will consider talks of this nature if they provide something special. +- Consider the tips in [this blog post](https://bridgetkromhout.com/blog/give-actionable-takeaways/) for even more suggestions on crafting a great proposal!
-How to submit a proposal: Send an email to [{{< email_organizers >}}] with the following information -
    -
  1. Type (presentation, panel discussion, ignite)
    2. -
  2. Proposal Title (can be changed later)
    3. -
  3. Description (several sentences explaining what attendees will learn)
    4. -
+How to submit a proposal: How to submit a proposal: Visit our [CFP Site and submit a proposal there](https://sessionize.com/devopsdays-chicago-2022/). If you run into any problems, please don’t hesitate to contact us by email at [{{< email_organizers >}}]. diff --git a/content/events/2022-chicago/sponsor.md b/content/events/2022-chicago/sponsor.md index 9f8429bf1a2..8e1069353dd 100644 --- a/content/events/2022-chicago/sponsor.md +++ b/content/events/2022-chicago/sponsor.md @@ -4,7 +4,9 @@ Type = "event" Description = "Sponsor devopsdays Chicago 2022" +++ -We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. +We greatly value sponsors for this community event. If you are interested in sponsoring, please check out our prospectus or send us an email. + +
@@ -14,53 +16,237 @@ Gold sponsors get a full table and Silver sponsors a shared table where they can

The best thing to do is send engineers to interact with the experts at devopsdays on their own terms.

+
+

Sponsorship Packages

- +
+ + + + +
+ + + +
+ + + + +
+ + + +
+ + + + +
+ + Contact us + + + + Tickets Included + 4 + 2 + 1 + 5 + + + Logo on DevOpsDays Chicago website + + + + + + + Social media shout-out + + + + + + + Logo on marketing materials + + + + + + + Logo on slides at breaks + + + + + + + Logo on participant emails + + + + + + + Booth space in sponsor area (with chair) + + + + + + + Logo on banner in sponsor area + + + + + + + Logo on banner at evening event + + + + + + + Shout-out from MC's at kickoff and again at breaks + + + + + + + Dedicated logo slide during breaks + + + + + + + Dedicated sponsor booth in sponsor area (with chair) + + + + + + + One-minute pitch between talks (includes live-stream audience) + + + + + + -
-There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, send us an email. -
-
-
-
- - - - - - - - - - - - - - + +

Special Sponsorships

+ +All special sponsors will have their logo displayed on the DevOpsDays Chicago website, a tweet before the conference, and a thank you during the conference. We do have some flexabilities with these sponsorships, so just ask! Email us: chicago-sponsors@devopsdays.org. +

+ +
Sponsor FAQ
Answers to questions frequently asked by sponsors                                                 
What dates/times can we set up and tear down?
How do we ship to the venue?
How do we ship from the venue?
Whom should we send?
What should we expect regarding electricity? (how much, any fees, etc)
What should we expect regarding WiFi? (how much, any fees, etc)
How do we order additional A/V equipment?
Additional important details
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SponsorshipPriceDescriptionTickets IncludedNumber Available
Evening Event$15,000Pay for drinks, food and entertainment - get an exclusive space for the night. Can be split by two sponsors42
Lanyard$7,000Your logo and colors around every attendee's credential21
Live Transcription$3,000Your logo by the screen where talks are transcribed21
ASL Interpreter$4,000Your logo by the screen in each video of the translator.21
Transportation$5,000Sponsor a custom Lyft code for participants01
ScholarshipsVariesProvide tickets for under-indexed groups to attend5
+ +
+
+
+
+ Sponsors are responsible for providing high-res logos for use on the website and in promotional materials. The preferred file formats are EPS or AI. +

+ All sponsors attendees must be registered to attend. We offer sponsors 20% off all additional registrations. +

+
+
+ + + + ---> -
diff --git a/content/events/2022-chicago/welcome.md b/content/events/2022-chicago/welcome.md index 536fb587917..9a44fabf74d 100644 --- a/content/events/2022-chicago/welcome.md +++ b/content/events/2022-chicago/welcome.md @@ -68,11 +68,11 @@ The format of DevOpsDays Chicago includes a single track of 30 minute talks in t
- +
   Contact the Organizers diff --git a/content/events/2022-geneva/propose.md b/content/events/2022-geneva/propose.md index 2b9119f8c59..e0e976fb3e4 100644 --- a/content/events/2022-geneva/propose.md +++ b/content/events/2022-geneva/propose.md @@ -5,27 +5,4 @@ Description = "Propose a talk for DevOpsDays Geneva 2022" +++

- -{{< cfp_dates >}} -
- -How to submit a proposal: Fill the Form Only if cannot use the form send an e-mail to {{< email_organizers subject="Talk proposal - DevOpsDays Geneva 2022">}} with the following information: -
    -
  1. Type of talk: Talk 30 min + Open Session 30 min, Talk 30 min or Open Session 45 min
    2. -
  2. A title of less than 250 characters (can be tweeted)
    3. -
  3. A summary of 100-150 words max. (will be in the program and the website)
    4. -
  4. A sentence about you (will serve to introduce you)
    5. -
  5. A photo of you (to be on social networks) - with your agreement of use (optional)
    6. -
  6. If you have filmed presentation please give us the links
    7. -
  7. Please explain in which way your presentation helps people keep up to date in our ever changing world
    8. -
  8. Please share a concrete benefit (Take away) for people taking part to your presentation
    9. -
-
-Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience: - -- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. -- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. -- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience. -- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen. -- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. -- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. +Call for proposals is closed since Monday, Nov 15, 2021 \ No newline at end of file diff --git a/content/events/2022-geneva/sponsor.md b/content/events/2022-geneva/sponsor.md index e50dca54930..98d450421d8 100644 --- a/content/events/2022-geneva/sponsor.md +++ b/content/events/2022-geneva/sponsor.md @@ -44,7 +44,7 @@ We greatly value sponsors for this open event. If you are interested in sponsori | **SPONSORS PACKS** | **EVENT** | **GOLD** | **SILVER** | **BRONZE** | **MUG** | | ------------------------------------------------------------------------- | :-----------: | :-----------: | :-----------: | :-----------: | :---------: | | | **9'000 CHF** | **6'000 CHF** | **3'000 CHF** | **1'500 CHF** | **500 CHF** | -| **Number of sponsors** | **1** | **8** | **8** | **12** | **8** | +| **Number of sponsors** | **Sold Out** | **Sold Out** | **Sold Out** | **12** | **8** | | **Free tickets** including sponsor team | **8** | **5** | **3** | **1** | **0** | | Logo on event **website** | ✔ | ✔ | ✔ | ✔ | | | Logo on **shared slides**, displayed during breaks (rotation) | | | ✔ | ✔ | | diff --git a/content/events/2022-geneva/welcome.md b/content/events/2022-geneva/welcome.md index 6c80155e424..1d1e609d306 100644 --- a/content/events/2022-geneva/welcome.md +++ b/content/events/2022-geneva/welcome.md @@ -94,6 +94,7 @@ Description = "DevOpsDays Geneva 2022" {{< event_link page="contact" text="Get in touch with the organisers" >}}
+
Newsletter diff --git a/content/events/2022-los-angeles/about.md b/content/events/2022-los-angeles/about.md new file mode 100644 index 00000000000..37ecc55b32a --- /dev/null +++ b/content/events/2022-los-angeles/about.md @@ -0,0 +1,19 @@ ++++ +Title = "About" +Type = "event" +Description = "About DevOpsDays Los Angeles 2022" ++++ + +
+ +

+We are proud to announce the 10th Annual DevOpsDaysLA will be held Friday, March 4, 2022. DevOpsDaysLA is an anual event held in Southern California. The conference is volunteer-organized and dedicated to the DevOps community.DevOpsDaysLA is presented in cooperation with the Southern California Linux Expo (SCALE). +
+
+DevOps +
+
+

+"DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality". [Loukides, Mike (7 June 2012). "What is DevOps?", http://radar.oreilly.com/2012/06/what-is-devops.html. O’Reilly Media)] + +
\ No newline at end of file diff --git a/content/events/2022-los-angeles/sponsor.md b/content/events/2022-los-angeles/sponsor.md index 07d83de341a..9d182e58c73 100644 --- a/content/events/2022-los-angeles/sponsor.md +++ b/content/events/2022-los-angeles/sponsor.md @@ -3,10 +3,11 @@ Title = "Sponsor" Type = "event" Description = "Sponsor DevOpsDays Los Angeles 2022" +++ -

DevOpsDayLA - Become A Sponsor

+
+

Become A Sponsor

-Thank you for your interest! Below is an overview of the conference as well as our sponsor packages. Please email the organizing committee at [{{< email_organizers >}}] for additional information or to secure your package. +Thank you for your interest! Below is an overview of the conference as well as our sponsor packages. Please email the organizing committee at {{< email_organizers >}} for additional information or to secure your package.

About DevOpsDayLA

@@ -22,29 +23,21 @@ DevOpsDaysLA, now in its 10th year, is Southern California's only annual confere

There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, send us an email. +

+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. + Note: We do not share attendee lists. -

Packages

- -
- - - - - - - - - - - - - - - - - -
Startup
1000 usd
Silver
2000 usd
Gold
3000 usd
2 included tickets   
logo on event website   
logo on shared slide, rotating during breaks   
logo on all email communication   
logo on its own slide, rotating during breaks   
1 minute pitch to full audience (including streaming audience)   
2 additional tickets (4 in total)   
4 additional tickets (6 in total)   
shared table for swag   
booth/table space   
+

Sponsor Prospectus

+ +

Exclusive Sponsorships

+ +Exclusive Sponsorships + +

Sponsorship Packages

+ +Exclusive Sponsorships +
diff --git a/content/events/2022-los-angeles/volunteer.md b/content/events/2022-los-angeles/volunteer.md new file mode 100644 index 00000000000..9dfea40b791 --- /dev/null +++ b/content/events/2022-los-angeles/volunteer.md @@ -0,0 +1,28 @@ ++++ +Title = "Volunteer" +Type = "event" +Description = "About DevOpsDays Los Angeles 2022" ++++ +
+

Become A Volunteer

+ +

+DevOpsDayLA, now in its 10th year, is Southern California's only annual conference focused on the practice of DevOps - a proven, joint approach that emphasizes the need for collaboration between the Development (Dev) and Operations/IT (Ops) teams within an organization to continually deliver high-quality solutions. The conference provides a relaxed, casual, and diverse environment where experienced professionals, evangelists, agile practitioners, developers, job seekers, business executives, educators, students, and curiosity seekers can connect and attend talks on current topics. DevOpsDayLA sponsors offer job opportunities, demonstrations of the latest tools, and world-class service offerings to facilitate organizations' DevOps journey. The conference typically attracts 800 people. + +

+We are seeking enthusiastic volunteers to help with conference setup, attendee management, and put away. Volunteering offers substantial career development benefits including: + +- Introductions to seasoned technology leaders & professionals +- Opportunities to hear talks +- Exceptional resume experience +- Strong differentiation when applying for internships + +

+The conference will provide volunteers with breakfast, lunch, and snacks throughout the day. They will also receive a special "Thank You" swag gift. + +

+ +
diff --git a/content/events/2022-los-angeles/welcome.md b/content/events/2022-los-angeles/welcome.md index e5d9e2c9131..22f9c9cc97a 100644 --- a/content/events/2022-los-angeles/welcome.md +++ b/content/events/2022-los-angeles/welcome.md @@ -5,9 +5,11 @@ aliases = ["/events/2022-los-angeles/"] Description = "DevOpsDays Los Angeles 2022" +++ - +
+ +
@@ -18,15 +20,6 @@ Description = "DevOpsDays Los Angeles 2022"
- -
Call For Papers @@ -38,61 +31,34 @@ Description = "DevOpsDays Los Angeles 2022"
- - - - - - - +
- Sponsors + Contact
- {{< event_link page="sponsor" text="Sponsor the conference!" >}} + {{< event_link page="contact" text="Get in touch with the organizers" >}}
- Contact + About
- {{< event_link page="contact" text="Get in touch with the organizers" >}} + {{< event_link page="about" text="About DevOpsDayLA" >}}
- + diff --git a/content/events/2022-portland-or/conduct.md b/content/events/2022-portland-or/conduct.md new file mode 100644 index 00000000000..c5b7e24afd6 --- /dev/null +++ b/content/events/2022-portland-or/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Portland, OR 2022" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Portland, OR 2022 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. + +### The Quick Version + +Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. + +### The Less Quick Version + +Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. + +Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. + +Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +_The devopsdays Portland, OR 2022 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2022-portland-or/contact.md b/content/events/2022-portland-or/contact.md new file mode 100644 index 00000000000..b652ba2db89 --- /dev/null +++ b/content/events/2022-portland-or/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Portland, OR 2022" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2022-portland-or/location.md b/content/events/2022-portland-or/location.md new file mode 100644 index 00000000000..0775d3da9fe --- /dev/null +++ b/content/events/2022-portland-or/location.md @@ -0,0 +1,17 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays Portland, OR 2022" ++++ + +Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details. + + + + + + diff --git a/content/events/2022-portland-or/propose.md b/content/events/2022-portland-or/propose.md new file mode 100644 index 00000000000..3cd49fbf56f --- /dev/null +++ b/content/events/2022-portland-or/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Portland, OR 2022" ++++ + {{< cfp_dates >}} + +
+ +There are three ways to propose a topic at devopsdays: +
    +
  1. A 30-minute talk presented during the conference, usually in the mornings.
    2. +
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table. +
+ +
+ +Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience: + +- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool. +- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request. +- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience. +- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen. +- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. +- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product. + +
+ +How to submit a proposal: Send an email to [{{< email_organizers >}}] with the following information +
    +
  1. Type (presentation, panel discussion, ignite)
    2. +
  2. Proposal Title (can be changed later)
    3. +
  3. Description (several sentences explaining what attendees will learn)
    4. +
diff --git a/content/events/2022-portland-or/registration.md b/content/events/2022-portland-or/registration.md new file mode 100644 index 00000000000..651edf6eeba --- /dev/null +++ b/content/events/2022-portland-or/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Portland, OR 2022" ++++ + +
+ +Embed registration iframe/link/etc. +
+
diff --git a/content/events/2022-portland-or/sponsor.md b/content/events/2022-portland-or/sponsor.md new file mode 100644 index 00000000000..a663927ca03 --- /dev/null +++ b/content/events/2022-portland-or/sponsor.md @@ -0,0 +1,66 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Portland, OR 2022" ++++ + +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. + +
+ +devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. +

+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. +

+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. +

+ + +

diff --git a/content/events/2022-portland-or/welcome.md b/content/events/2022-portland-or/welcome.md new file mode 100644 index 00000000000..03179972b2f --- /dev/null +++ b/content/events/2022-portland-or/welcome.md @@ -0,0 +1,87 @@ ++++ +Title = "devopsdays Portland, OR 2022" +Type = "welcome" +aliases = ["/events/2022-portland-or/"] +Description = "devopsdays Portland, OR 2022" ++++ + + + +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ + + + + + + + + + + +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ + + diff --git a/content/events/2022-raleigh/sponsor.md b/content/events/2022-raleigh/sponsor.md index a4acacd94ce..1ef58d2f490 100644 --- a/content/events/2022-raleigh/sponsor.md +++ b/content/events/2022-raleigh/sponsor.md @@ -6,6 +6,8 @@ Description = "Sponsor devopsdays raleigh 2022" We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. +Sponsor package details are here : [Sponsorship Package](https://assets.devopsdays.org/events/2022/raleigh/devopsdaysraleigh2022sponsorshippacket.pdf) +
devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. diff --git a/content/events/2022-vitoria/location.md b/content/events/2022-vitoria/location.md index 5d7fe2df8f7..b53a5499252 100644 --- a/content/events/2022-vitoria/location.md +++ b/content/events/2022-vitoria/location.md @@ -4,10 +4,11 @@ Type = "event" Description = "Location for devopsdays Vitoria 2022" +++ -Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details. - +O evento será sediado no Grand Hall ao lado da Emescan. +
+Endereço: R. Dr. João Carlos de Souza - Barro Vermelho, Vitória - ES, 29045-410 - +{{< event_map >}} +
+

[EN] Sponsorship Proposal

+

+Our partners are encouraged to take an active participation, to engage with participants and to suggest themes for open spaces, which are self-organized sessions open to meaninful discussions. We want our partners to get involved in the event! +

+

+We understand that a greater number of partnerships is beneficial to the event, providing a great opportunity to deep-dive in the DevOps world, to have a better networking and so on and so forth, so we chose to work at quotas with more accessible values for this event. +

+

+Aiming to enhance the participation of institutions in the event, we organized partnership groups. Each one provides a set of benefits to official partners, according to established requirements meeting the corresponding counterpart defined as shown in the table bellow. +

---> -
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
BENEFITSBRONZESILVERGOLDPLATINUM
Institutional video broadcasting
Logo on badge lanyards
Promotional booth
Logo on stage
Logo on marketing materials
Swags distributed inside the participant's folders
Social media action
Featured physical bannersSize ½USize ¾USize 1U
Logo on the event/releases
Social media release
Tickets*24810
ContributionUS$ 600,00US$ 1.000,00US$ 1.500,00US$ 2.000,00
+
+
+

COMMUNITY: Supporters who have contributed some benefit to the public or amount of +up to US$ 200,00 receive the right to be publicized on social media and 1 registration for the event.

+

See more in the full document by clicking

+
diff --git a/content/events/2022-vitoria/welcome.md b/content/events/2022-vitoria/welcome.md index ba4ae4e1551..3b3a0c0735b 100644 --- a/content/events/2022-vitoria/welcome.md +++ b/content/events/2022-vitoria/welcome.md @@ -45,10 +45,25 @@ Description = "devopsdays Vitoria 2022" Sponsors
- {{< event_link page="sponsor" text="Sponsor DevOps Vitoria 2022!" >}} + {{< event_link page="sponsor" text="Apoiei o Devopsdays Vitoria 2022!" >}} +
+ +
+
+ CFP +
+
+ {{< event_link url-key="cfp_link" text="Submeta a sua talk!" >}} +
+
+
+
+ Ingresso +
+
+ {{< event_link url-key="registration_link" text="Adquira seu ingresso!" >}}
-
diff --git a/content/events/2022-zurich/conduct.md b/content/events/2022-zurich/conduct.md new file mode 100644 index 00000000000..1ac38458bb7 --- /dev/null +++ b/content/events/2022-zurich/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Zürich 2022" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Zürich 2022 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. + +### The Quick Version + +Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. + +### The Less Quick Version + +Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. + +Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. + +Conference staff can be identified by distinct staff t-shirts. Conference staff will be happy to help participants contact local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +_The devopsdays Zürich 2022 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2022-zurich/contact.md b/content/events/2022-zurich/contact.md new file mode 100644 index 00000000000..cf9ef2ca27e --- /dev/null +++ b/content/events/2022-zurich/contact.md @@ -0,0 +1,15 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays zurich 2022" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + +**The core devopsdays organizer group** + +{{< list_core >}} diff --git a/content/events/2022-zurich/covid.md b/content/events/2022-zurich/covid.md new file mode 100644 index 00000000000..44fe4f77569 --- /dev/null +++ b/content/events/2022-zurich/covid.md @@ -0,0 +1,40 @@ ++++ +Title = "Covid-19" +Type = "event" +Description = "All information about the Covid-19 measures" ++++ + +
+
+

The COVID-19 situation in Switzerland is improving at this point in time, so that we're go for an in-person event allowing access to everyone who is either vaccinated, tested or convalesced from COVID-19. + This means that only persons with a valid COVID-Certificate and a valid ID (e.g. driving license or passport) are allowed access to the DevOpsDays Zürich 2022. + Data and reports on the epidemiological situation in Switzerland can be found here: Situation in Switzerland +

+ DevOpsDays Zürich 2022 COVID-19 protection concept +
+
+
+
+

Therefore, we plan to hold DevOpsDays Zurich 2022 as an in-person event. However, we will work out a detailed COVID-19 concept for the event which will be updated constantly, to make the situation on site as safe as possible for everyone. The detailed COVID-19 concept will be communicated at a later point in time.

+
+
+
+
+

+ COVID-19 Measures +

Please note that all measures and rules given by the Swiss government apply to DevOpsDays Zurich 2022 and you’ll need to comply with these rules or you cannot attend the event.
Measures and ordinances

+
+
+

+ COVID-19 Travel: +

If you are traveling to Switzerland, please read the following travel information carefully before entering Switzerland and the Swiss government FAQ. +
Entering Switzerland
Questions and answers on entry and stay in Switzerland

+
+
+

+ COVID-19 Refund Policy: +

Your ticket gets refunded when you are not able to travel due to travel restrictions or if you cannot attend due to a COVID-19 injection or suspicion.

+
+
+ + diff --git a/content/events/2022-zurich/diversity.md b/content/events/2022-zurich/diversity.md new file mode 100644 index 00000000000..3e30b9dd2e2 --- /dev/null +++ b/content/events/2022-zurich/diversity.md @@ -0,0 +1,29 @@ ++++ +Title = "Diversity" +Type = "event" +Description = "Diversity for devopsdays zurich 2022" ++++ + +
+
+

At DevOpsDays Zürich we don’t want to be a tech-conference only — instead we want to be a conference focusing on knowledge, networking and a connecting atmospheric vibe, welcoming a range of backgrounds, experiences and opinions.

+

Wether you are a speaker or a participant, maybe something’s missing for you? Would you be happy to have some mentoring on your first conference talk? Would you need some assistance in getting to Winterthur? Would you need childcare to be at the conference? Whatever it is, please do not hesitate to contact us. +

+

+
We might not have a solution in every case or right away – but you can be sure that we are passionate and eager to find one!

+

Here’s among others what we already thought of:

+
    +
  • trying some sort of “diversity in tech”-stream or talk at the conference itself
    • +
  • let participants create their own name badge and show their individual expression
    • +
  • have gender neutral toilets (if feasable with the location)
    • +
  • check the location with zugangsmonitor.ch
    • +
  • have reserved seating for people with mobility issues
    • +
+ sharelogo_medium + Contact us! +

The access monitor documents the accessibility of cultural institutions for people with a visual, mobility or hearing impairment. Here you can find the accessibility of the Alte Kaserne Winterthur.

+ Zugangs Monitor +
+
+ + diff --git a/content/events/2022-zurich/location.md b/content/events/2022-zurich/location.md new file mode 100644 index 00000000000..bb1c9368573 --- /dev/null +++ b/content/events/2022-zurich/location.md @@ -0,0 +1,10 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays zurich 2022" ++++ + +## Alte Kaserne Winterthur +Technikumstrasse 8, 8400 Winterthur, Switzerland + +{{< event_map >}} diff --git a/content/events/2022-zurich/welcome.md b/content/events/2022-zurich/welcome.md new file mode 100644 index 00000000000..a79555598d2 --- /dev/null +++ b/content/events/2022-zurich/welcome.md @@ -0,0 +1,151 @@ ++++ +Title = "DevOpsDays Zürich 2022" +Type = "welcome" +aliases = ["/events/2022-zurich/"] +Description = "DevOpsDays Zürich 2022" ++++ + + + +
+ +
+ + + + + +
+
+

First time here? Check out our last events and get hyped!

+ DevOpsDays 2017 - Where it all started
+ DevOpsDays 2018 - The Continuation
+ DevOpsDays 2019 - The Rising
+ DevOpsDays 2020 - The DevOpsTuesDays
+ DevOpsDays 2021 - DevOpsDays Zürich is stronger than COVID
+
+
+ +
+ +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ + + +
+
+ Location +
+
+ {{< event_location >}} +
+
+ + + +
+
+ Diversity +
+
+ {{< event_link page="diversity" text="We want to create a most diverse conference!" >}} +
+
+ +
+
+ COVID-19 +
+
+ {{< event_link page="covid" text="All information about the Covid-19 measures" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ +
+
+ Homepage +
+
+ DevOpsDays.ch +
+
+ + + diff --git a/data/events/2016-telaviv.yml b/data/events/2016-telaviv.yml index 8b629fbc8fb..4c16b42c6de 100644 --- a/data/events/2016-telaviv.yml +++ b/data/events/2016-telaviv.yml @@ -80,7 +80,7 @@ sponsors: level: silver - id: cloudify-before-20170704 level: silver - - id: cloudinary + - id: cloudinary-before-20211111 level: silver - id: aws-before-20180313 level: silver diff --git a/data/events/2019-amsterdam.yml b/data/events/2019-amsterdam.yml index 2f54812f1ce..06aa0354ce0 100644 --- a/data/events/2019-amsterdam.yml +++ b/data/events/2019-amsterdam.yml @@ -130,7 +130,7 @@ sponsors: level: silver - id: devoteam level: silver - - id: eficode + - id: eficode-before-20211021 level: silver - id: cyberark level: silver diff --git a/data/events/2019-copenhagen.yml b/data/events/2019-copenhagen.yml index d1ac62d9d6f..7d0733211b1 100644 --- a/data/events/2019-copenhagen.yml +++ b/data/events/2019-copenhagen.yml @@ -90,7 +90,7 @@ proposal_email: "proposals-copenhagen-2019@devopsdays.org" # Put your proposal e sponsors: - id: praqma level: gold - - id: eficode + - id: eficode-before-20211021 level: gold - id: redhat-before-20190528 level: gold diff --git a/data/events/2019-geneva.yml b/data/events/2019-geneva.yml index 7eac1f106e2..a6c08ede983 100644 --- a/data/events/2019-geneva.yml +++ b/data/events/2019-geneva.yml @@ -110,7 +110,7 @@ sponsors: level: silver - id: globaz-before-20190121 level: silver - - id: techfirm + - id: techfirm-before-20211001 level: bronze sponsors_accepted: "yes" # Whether you want "Become a XXX Sponsor!" link diff --git a/data/events/2020-geneva.yml b/data/events/2020-geneva.yml index f5a94a4ce21..297155346b8 100644 --- a/data/events/2020-geneva.yml +++ b/data/events/2020-geneva.yml @@ -126,7 +126,7 @@ sponsors: level: silver - id: sword level: silver - - id: techfirm + - id: techfirm-before-20211001 level: gold - id: swissdevjobs level: community diff --git a/data/events/2021-baku.yml b/data/events/2021-baku.yml new file mode 100644 index 00000000000..6f88d49f163 --- /dev/null +++ b/data/events/2021-baku.yml @@ -0,0 +1,112 @@ +name: "2021-baku" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2021" # The year of the event. Make sure it is in quotes. +city: "Baku" # The displayed city name of the event. Capitalize it. +event_twitter: "DevopsDaysBaku" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Baku, the capital city of Azerbaijan, is proud to host the first DevOps Days here in Azerbaijan. Famous for its historical oil resources, Baku is home to many international companies from banks to large corporations. The DevOps community of Baku are very excited for the upcoming event. DevOpsDays Baku will bring together more than 200 development, operations, security, and management professionals from various companies to discuss the processes and tools to enable better organizations and innovative products. The schedule will consist of a mixture of single-track presentations, lightning talks, and the Open Space format that DevOpsDays is known for." # Edit this to suit your preferences +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" + +# All dates are in unquoted YYYY-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2019-01-04T00:00:00+02:00 +# variable: 2019-01-05T23:59:59+02:00 +# Note: we allow YYYY-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) + +startdate: 2021-12-09T10:00:00+04:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2021-12-09T21:00:00+04:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: 2021-08-01T00:00:00+04:00 # start accepting talk proposals. +cfp_date_end: 2021-12-09T00:00:00+04:00 # close your call for proposals. +cfp_date_announce: 2021-08-01T00:00:00+04:00 # inform proposers of status + +cfp_open: "true" +cfp_link: "https://www.papercall.io/devopsdaysbaku2021" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. + +registration_date_start: # start accepting registration. Leave blank if registration is not open yet +registration_date_end: # close registration. Leave blank if registration is not open yet. + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +registration_link: # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location +# +coordinates: "40.4144831, 49.8432936" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "" # Defaults to city, but you can make it the venue name. +# +location_address: "89 Ataturk avenue, Baku, Azerbaijan" #Optional - use the street address of your venue. This will show up on the welcome page if set. + +nav_elements: # List of pages you want to show up in the navigation of your page. + - name: devopsdays.az + url: https://devopsdays.az/ + - name: propose + url: "https://www.papercall.io/devopsdaysbaku2021" + - name: location + # - name: registration + # - name: program + # - name: speakers + - name: sponsor + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Vusal Karimli" + linkedin: "https://www.linkedin.com/in/vusalkarimli/" + image: "vusal.jpg" + - name: "Mammad Karim" + linkedin: "https://www.linkedin.com/in/mammadkarim/" + image: "mammad.jpeg" + - name: "Rashad Eyvazov" + linkedin: "https://www.linkedin.com/in/rashad-eyvazov-b1259226/" + image: "rashad.jpeg" + - name: "Ismayil Musayev" + linkedin: "https://www.linkedin.com/in/ismail-musayev-57470414b/" + image: "ismayil.jpeg" + - name: "Naseh Badalov" + linkedin: "https://www.linkedin.com/in/nasehbadalov/" + image: "naseh.jpg" + - name: "Zaur Baghirov" + linkedin: "https://www.linkedin.com/in/zaur-baghirov-7b020117/" + image: "zaur.jpg" + - name: "Afet Baghirova" + linkedin: "https://www.linkedin.com/in/afet-bagirova-0a576431/" + image: "afet.jpg" + - name: "Fidan Tofidi" + linkedin: "https://www.linkedin.com/in/fidan-tofidi-082159106/" + image: "fidan.jpg" + - name: "Tariyel Aghazada" + linkedin: "https://www.linkedin.com/in/tariyel-aghazada-061265167/" + image: "tariyel.jpg" +organizer_email: "baku@devopsdays.org" # Put your organizer email address here + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +sponsors: + - id: pashabank + level: platinium + # - id: atltech + # level: gold + # - id: innoland + # level: gold + - id: sup + level: platinium + # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. + - id: nextstep + level: gold + +sponsors_accepted: "no" # Whether you want "Become a XXX Sponsor!" link + +# In this section, list the level of sponsorships and the label to use. +# You may optionally include a "max" attribute to limit the number of sponsors per level. For +# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all +# sponsorship for a specific level, it is best to remove the level. +sponsor_levels: + - id: platinium + label: Platinium + - id: gold + label: Gold + - id: silver + label: Silver diff --git a/data/events/2021-birmingham.yml b/data/events/2021-birmingham.yml index ca409da6650..3e38fa1863d 100644 --- a/data/events/2021-birmingham.yml +++ b/data/events/2021-birmingham.yml @@ -5,6 +5,8 @@ event_twitter: "devopsdaysbrum" # Change this to the twitter handle for your eve description: "While our 2021 event will no longer happen, we will return in 2022." # Edit this to suit your preferences ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" event_logo: logo.png +event_group: "Birmingham, UK" + #masthead_background: "background.png" # All dates are in unquoted 2021-MM-DDTHH:MM:SS+TZ:TZ, like this: diff --git a/data/events/2021-buffalo.yml b/data/events/2021-buffalo.yml index 3f41d23e33e..6bc6af9078b 100644 --- a/data/events/2021-buffalo.yml +++ b/data/events/2021-buffalo.yml @@ -119,6 +119,10 @@ sponsors: level: gold - id: aviatrix level: gold + - id: mandtbank + level: captioning + - id: observiq + level: snack sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link @@ -133,9 +137,15 @@ sponsor_levels: - id: silver label: Silver max: 5 + - id: captioning + label: Captioning + max: 1 - id: bronze label: Bronze max: 10 + - id: snack + label: Snack + max: 1 - id: community label: Community @@ -160,15 +170,20 @@ program: date: 2021-10-13 start_time: "15:00" end_time: "15:25" - - title: "ben-greenberg" + - title: "josh-stella" type: talk date: 2021-10-13 start_time: "15:30" end_time: "15:55" + - title: "dan-lines" + type: talk + date: 2021-10-13 + start_time: "16:00" + end_time: "16:25" - title: "Intermission - Drive time to Transit Drive-In" type: custom date: 2021-10-13 - start_time: "16:00" + start_time: "16:30" end_time: "17:30" - title: "Attendee Arrival, In-person Registration, and Dinner" type: custom @@ -238,7 +253,7 @@ program: date: 2021-10-14 start_time: "15:00" end_time: "15:25" - - title: "josh-stella" + - title: "ben-greenberg" type: talk date: 2021-10-14 start_time: "15:30" diff --git a/data/events/2021-minneapolis.yml b/data/events/2021-minneapolis.yml index d0dc290998d..b5fd8d6d695 100644 --- a/data/events/2021-minneapolis.yml +++ b/data/events/2021-minneapolis.yml @@ -134,7 +134,7 @@ sponsors: level: platinum - id: lacework level: gold - - id: launch-darkly + - id: launch-darkly-before-20210928 level: gold - id: skycrafters level: gold diff --git a/data/events/2021-oslo.yml b/data/events/2021-oslo.yml new file mode 100644 index 00000000000..8b5ce031656 --- /dev/null +++ b/data/events/2021-oslo.yml @@ -0,0 +1,106 @@ +--- +name: "2021-oslo" +year: "2021" +city: "Oslo" +event_twitter: "devopsdaysoslo" +description: "Devopsdays is coming to Oslo again!" +# ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" +event_logo: "logo.png" + +# All dates are in unquoted YYYY-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2021-01-04T00:00:00+02:00 +# variable: 2021-01-05T23:59:59+02:00 +# Note: we allow YYYY-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event +# disappearing from the front page during your last day) + +startdate: 2021-11-16T00:00:00+02:00 +enddate: 2021-11-16T23:59:59+02:00 + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: 2021-09-22T12:00:00 # start accepting talk proposals. +cfp_date_end: 2021-11-01T12:00:00 # close your call for proposals. +# cfp_date_announce: 2021-09-07T00:00:00 # inform proposers of status + +cfp_open: "false" +cfp_link: "https://sessionize.com/devopsdays-oslo-2021/" + +registration_date_start: 2021-10-14T00:00:00+02:00 # start accepting registration. Leave blank if registration is not open yet +registration_date_end: 2021-11-15T23:59:59+02:00 # close registration. Leave blank if registration is not open yet. + +# registration_closed: "" # Set this to true if you need to manually close registration before your registration end date +registration_link: "https://ti.to/devopsdaysoslo/2021" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location +coordinates: "59.917514204671214, 10.740498310563055" # The coordinates of your city. Latitude and Longitude. +location: "Rebel" +location_address: "Rebel, Universitetsgata 2, 0164 Oslo" + +nav_elements: # List of pages you want to show up in the navigation of your page. + - name: propose + # - name: livestream + - name: location + - name: registration + - name: program + - name: speakers + - name: sponsor + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Anton Babenko" + twitter: "antonbabenko" + image: "anton-babenko.jpg" + - name: "Lars Tobias Skjong-Børsting" + twitter: "larstobi" + image: "lars-tobias-skjong-borsting.jpg" + - name: "Lande Castberg" + image: "lande-castberg.jpg" + - name: "Anders Bruvik" + twitter: "bruvik" + image: "anders-bruvik.jpg" + employer: "Safespring" + - name: "Tor Magnus Castberg" + twitter: "TMCastberg" + image: "tor-magnus-castberg.jpg" + - name: "Alex Albu" + image: "alexandru-albu.jpg" + - name: "Mike Long" + image: "mike-long.jpg" + twitter: "meekrosoft" + - name: "Recep Cetin" + image: "recep-cetin.jpg" + - name: "Roberth Strand" + employer: "Crayon" + twitter: "roberthtweets" + linkedin: "https://www.linkedin.com/in/roberthstrand" + image: "roberth-strand.jpg" + +organizer_email: "oslo@devopsdays.org" + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +# sponsors: +# - id: samplesponsorname +# level: gold +# url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. +# - id: arresteddevops +# level: community +sponsors: + - id: entur + level: event + - id: eficode + level: event + - id: merkely + level: event + - id: microsoft + level: event + +sponsor_levels: + - id: event + label: Event + +sponsors_accepted: "yes" # Whether you want "Become a X Sponsor!" link diff --git a/data/events/2021-poznan.yml b/data/events/2021-poznan.yml index 0819b64b157..1199221db53 100644 --- a/data/events/2021-poznan.yml +++ b/data/events/2021-poznan.yml @@ -108,18 +108,14 @@ sponsors: - id: trecom level: organizing url: https://www.trecom.pl/en/trecom-develop-and-optimize-your-it-system/ -# - id: nordcloud -# level: gold -# - id: delltechnologies -# level: gold -# - id: trecom -# level: gold -# - id: centuria -# level: gold -# - id: egnyte -# level: silver -# - id: tomtom -# level: silver + - id: riskmethods + level: partner + - id: merixstudio + level: partner + - id: egnyte + level: partner + - id: glaxosmithkline + level: partner # - id: holidaycheck # level: bronze # - id: allegro @@ -264,21 +260,16 @@ program: date: 2021-10-05 start_time: "13:55" end_time: "14:30" - - title: "Coffee break" - type: custom - date: 2021-10-05 - start_time: "14:30" - end_time: "14:50" - - title: "Openspace" - type: open-space + - title: "jj-asghar" + type: talk date: 2021-10-05 start_time: "14:50" - end_time: "15:50" - - title: "Closing day 1" + end_time: "15:25" + - title: "Closing day 2" type: custom date: 2021-10-05 - start_time: "15:50" - end_time: "16:00" + start_time: "15:25" + end_time: "15:30" ignites: - title: "pawel-sztromwasser" @@ -291,4 +282,3 @@ ignites: date: 2021-10-05 - title: "jakub-warczarek" date: 2021-10-05 - \ No newline at end of file diff --git a/data/events/2021-taipei.yml b/data/events/2021-taipei.yml index b69497c03c7..00b39ba5e7c 100644 --- a/data/events/2021-taipei.yml +++ b/data/events/2021-taipei.yml @@ -10,15 +10,15 @@ ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it # variable: 2021-01-05T23:59:59+02:00 # Note: we allow YYYY-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) -startdate: 2021-05-28T00:00:00+08:00 -enddate: 2021-05-28T23:59:59+08:00 +startdate: 2021-11-24T00:00:00+08:00 +enddate: 2021-11-24T23:59:59+08:00 # Leave CFP dates blank if you don't know yet, or set all three at once. cfp_date_start: 2021-01-20T00:00:00+08:00 # start accepting talk proposals. cfp_date_end: 2021-03-04T00:00:00+08:00 # close your call for proposals. cfp_date_announce: 2021-01-20T00:00:00+08:00 # inform proposers of status -cfp_open: "true" +cfp_open: "false" cfp_link: "https://devopsdays.tw/cfs/" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. registration_date_start: # start accepting registration. Leave blank if registration is not open yet diff --git a/data/events/2021-tel-aviv.yml b/data/events/2021-tel-aviv.yml index 82f11b90abf..69a449f9d47 100644 --- a/data/events/2021-tel-aviv.yml +++ b/data/events/2021-tel-aviv.yml @@ -20,26 +20,24 @@ cfp_date_announce: 2021-06-30T00:00:00+02:00 cfp_link: "https://www.papercall.io/devopsdays-tlv-2021" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. -registration_date_start: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. -registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. +registration_date_start: 2021-10-01T00:00:00+02:00 # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. +registration_date_end: 2021-11-25T00:00:00+02:00 # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. registration_closed: "" #set this to true if you need to manually close registration before your registration end date -registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. +registration_link: "https://tlvcommunity.dev/devopsdays/register" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. # Location -# -coordinates: "" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +coordinates: "32.11091901983046, 34.80388762740464" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html location: "Smolarz Auditorium, Tel Aviv University" # Defaults to city, but you can make it the venue name. -# -location_address: "" #Optional - use the street address of your venue. This will show up on the welcome page if set. +location_address: "Dr George Wise St 24, Tel Aviv-Yafo" #Optional - use the street address of your venue. This will show up on the welcome page if set. nav_elements: # List of pages you want to show up in the navigation of your page. - - name: propose + # - name: propose - name: location - # - name: registration - # - name: program + - name: registration + - name: program # - name: speakers - - name: sponsor + # - name: sponsor - name: contact - name: conduct # - name: example @@ -68,7 +66,7 @@ team_members: # Name is the only required field for team members. github: "burdandrei" linkedin: "https://www.linkedin.com/in/burdandrei/" website: "https://mattstratton.com" - image: "andrei-burd.jpg" + image: "andrei-burd.jpeg" - name: "Nati Cohen" employer: "AWS" @@ -81,7 +79,7 @@ team_members: # Name is the only required field for team members. employer: "Palo Alto Networks" github: "hilafish" linkedin: "https://www.linkedin.com/in/hila-fish-863949a/" - website: "https://mattstratton.com" + website: "" image: "hila-fish.jpg" - name: "Gil Zellner" @@ -106,7 +104,7 @@ team_members: # Name is the only required field for team members. image: "viki-slavin.jpg" - name: "Dan Yelovitch" - employer: "Snap, Inc." + employer: "Develeap" github: "devopsdays" linkedin: "https://www.linkedin.com/in/dan-yelovitch-15b92036/" website: "" @@ -150,10 +148,24 @@ team_members: # Name is the only required field for team members. - name: "Roman Roberman" employer: "Wix" github: "" - linkedin: "" + linkedin: "https://www.linkedin.com/in/roman-roberman/" website: "" image: "roman-roberman.jpeg" + - name: "Dotan Horovits" + employer: "Logz.io" + github: "" + linkedin: "https://www.linkedin.com/in/horovits/" + website: "" + image: "dotan-horovits.jpg" + + - name: "Tal Kimhi" + employer: "BigPanda" + github: "" + linkedin: "https://www.linkedin.com/in/talkimhi/" + website: "" + image: "tal-kimhi.jpg" + organizer_email: "tel-aviv@devopsdays.org" # Put your organizer email address here @@ -195,6 +207,8 @@ sponsors: level: community - id: logz level: community + - id: applied-materials + level: community - id: microsoft level: community - id: spot-by-netapp @@ -205,6 +219,16 @@ sponsors: level: community - id: jfrog level: community + - id: next-insurance + level: branding + - id: cloudinary + level: branding + - id: velocitytech + level: branding + - id: profisea + level: branding + - id: snappy + level: branding - id: livecycle level: other - id: aerospike @@ -217,6 +241,18 @@ sponsors: level: other - id: hashicorp level: other + - id: kaltura + level: other + - id: quali + level: community + - id: bridgecrew + level: branding + - id: harness + level: branding + - id: neuralegion + level: branding + - id: icinga + level: branding - id: daily-dev level: media - id: barvazgumi @@ -241,3 +277,169 @@ sponsor_levels: # max: 10 - id: media label: Media Partner +#program: +# - title: "Breakfast Sponsored by Coralogix & Reuniting with Friends in the Hallway Track" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "08:30" +# end_time: "09:30" +# - title: "Opening Welcome" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "09:00" +# end_time: "09:15" +# - title: "test" +# type: talk +# date: 2021-11-24T09:00:00+02:00 +# start_time: "09:15" +# end_time: "09:45" +# - title: "Sponsors" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "09:45" +# end_time: "09:55" +# - title: "test" +# type: talk +# date: 2021-11-24T09:00:00+02:00 +# start_time: "09:55" +# end_time: "10:25" +# - title: "Break" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "10:25" +# end_time: "10:40" +# - title: "test" +# type: talk +# date: 2021-11-24T09:00:00+02:00 +# start_time: "10:40" +# end_time: "11:10" +# - title: "Sponsors" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "11:10" +# end_time: "11:20" +# - title: "test" +# type: talk +# date: 2021-11-24T09:00:00+02:00 +# start_time: "11:20" +# end_time: "11:50" +# - title: "Lunch" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "11:50" +# end_time: "13:00" +# - title: "Ignites" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "13:00" +# end_time: "13:30" +# - title: "Open Space Opening" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "13:30" +# end_time: "14:00" +# - title: "Open Space #1" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "14:00" +# end_time: "14:45" +# - title: "Open Space #2" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "15:00" +# end_time: "15:45" +# - title: "Open Space #3" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "16:00" +# end_time: "16:45" +# - title: "Close Day" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "16:45" +# end_time: "17:00" +# - title: "Evening event" +# type: custom +# date: 2021-11-24T09:00:00+02:00 +# start_time: "19:00" +# end_time: "late" +# - title: "Registration, Breakfast, Sponsors" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "08:00" +# end_time: "09:00" +# - title: "Opening Welcome" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "09:00" +# end_time: "09:15" +# - title: "test" +# type: talk +# date: 2021-11-25T17:30:00+02:00 +# start_time: "09:15" +# end_time: "09:45" +# - title: "Sponsors" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "09:45" +# end_time: "09:55" +# - title: "test" +# type: talk +# date: 2021-11-25T17:30:00+02:00 +# start_time: "09:55" +# end_time: "10:25" +# - title: "Break" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "10:25" +# end_time: "10:40" +# - title: "test" +# type: talk +# date: 2021-11-25T17:30:00+02:00 +# start_time: "10:40" +# end_time: "11:10" +# - title: "Sponsors" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "11:10" +# end_time: "11:20" +# - title: "test" +# type: talk +# date: 2021-11-25T17:30:00+02:00 +# start_time: "11:20" +# end_time: "11:50" +# - title: "Lunch" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "11:50" +# end_time: "13:00" +# - title: "Ignites" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "13:00" +# end_time: "13:30" +# - title: "Open Space Opening" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "13:30" +# end_time: "14:00" +# - title: "Open Space #1" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "14:00" +# end_time: "14:45" +# - title: "Open Space #2" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "15:00" +# end_time: "15:45" +# - title: "Open Space #3" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "16:00" +# end_time: "16:45" +# - title: "Closing" +# type: custom +# date: 2021-11-25T17:30:00+02:00 +# start_time: "16:45" +# end_time: "17:00" diff --git a/data/events/2021-washington-dc.yml b/data/events/2021-washington-dc.yml index 667ef28bbb8..7c5e9486df6 100644 --- a/data/events/2021-washington-dc.yml +++ b/data/events/2021-washington-dc.yml @@ -10,7 +10,7 @@ ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it # variable: 2019-01-05T23:59:59+02:00 # Note: we allow 2021-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) -startdate: 2021-11-04T08:00:00-04:00 +startdate: 2021-11-04T08:30:00-04:00 enddate: 2021-11-04T19:00:00-04:00 # Leave CFP dates blank if you don't know yet, or set all three at once. @@ -18,14 +18,14 @@ cfp_date_start: 2021-07-26T00:00:00-04:00 cfp_date_end: 2021-09-13T23:59:59-04:00 cfp_date_announce: 2021-09-27T23:59:59-04:00 -cfp_open: "true" +cfp_open: "false" cfp_link: "https://devopsdaysdc2021.busyconf.com/proposals/new" -registration_date_start: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. -registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. +registration_date_start: 2021-10-07T00:00:00-04:00 # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. +registration_date_end: 2021-11-05T00:00:00-04:00 # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. registration_closed: "" #set this to true if you need to manually close registration before your registration end date -registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. +registration_link: "https://hopin.com/events/devopsdays-dc-2021" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. # Location # @@ -35,11 +35,13 @@ location: "Washington, D.C." # Defaults to city, but you can make it the venue n location_address: "Online Event! Stay Safe!" #Optional - use the street address of your venue. This will show up on the welcome page if set. nav_elements: # List of pages you want to show up in the navigation of your page. - - name: propose + # - name: propose # - name: location - # - name: registration - # - name: program - # - name: speakers + - name: registration + - name: program + url: https://hopin.com/events/devopsdays-dc-2021#schedule # The url setting is optional, and only if you want the navigation to link off-site + - name: speakers + url: https://hopin.com/events/devopsdays-dc-2021#speakers # The url setting is optional, and only if you want the navigation to link off-site - name: sponsor - name: contact - name: conduct @@ -254,6 +256,8 @@ sponsor_levels: sponsors: - id: excella level: platinum + - id: chef-progress + level: platinum - id: aviatrix level: platinum - id: cloudsmith @@ -262,3 +266,7 @@ sponsors: level: gold - id: pluribus-digital level: gold + - id: fearless-hutch + level: gold + - id: homelight + level: silver diff --git a/data/events/2022-aarhus.yml b/data/events/2022-aarhus.yml new file mode 100644 index 00000000000..e324c7b65a3 --- /dev/null +++ b/data/events/2022-aarhus.yml @@ -0,0 +1,119 @@ +name: "2022-aarhus" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2022" # The year of the event. Make sure it is in quotes. +city: "Aarhus" # The displayed city name of the event. Capitalize it. +event_twitter: "devopsdayscph" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Join us for the first-ever DevOpsDays in Aarhus" # Edit this to suit your preferences +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" + +# All dates are in unquoted 2022-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2019-01-04T00:00:00+02:00 +# variable: 2019-01-05T23:59:59+02:00 +# Note: we allow 2022-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) + +startdate: 2022-01-25 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2022-01-26 # The end date of your event. Leave blank if you don't have a venue reserved yet. + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: # start accepting talk proposals. +cfp_date_end: # close your call for proposals. +cfp_date_announce: # inform proposers of status + +cfp_link: "https://www.papercall.io/devopsdaysaarhus-2022" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. + +registration_date_start: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. +registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location +# +coordinates: "" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "At Sejlsportscentret Aarhus" # Defaults to city, but you can make it the venue name. +# +location_address: "" #Optional - use the street address of your venue. This will show up on the welcome page if set. + +nav_elements: # List of pages you want to show up in the navigation of your page. + - name: propose + - name: register + url: https://www.eventbrite.co.uk/e/devopsdays-aarhus-2022-tickets-92256964063?aff=ebdssbeac + - name: location + # - name: registration + # - name: program + # - name: speakers + - name: sponsor + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Danny Lajer" + employer: "Eficode" + image: "danny-lajer.jpg" +# - name: "Adam Henriques" +# employer: "Eficode" +# image: "adam-henriques.jpg" + - name: "Andy Dyrcz" + employer: "Linkfire" + github: "adyrcz" + image: "andy-dyrcz.jpg" +# - name: "Jasmine Crozier" +# twitter: "jasminecph" +# employer: "Eficode" +# image: "jasmine-crozier.jpg" + - name: "Jeppe Andersen" + twitter: "nocture" + employer: "DataRobot" + image: "jeppe-andersen.jpg" + - name: "Johan Abildskov" + twitter: "randomsort" + employer: "Uber" + image: "johan-abildskov.jpg" + - name: "Rasmus Hald" + twitter: "RasmusHaldDK" + employer: "The LEGO Group" + image: "rasmus-hald.jpg" + - name: "Mads Baggesen" + employer: "Eficode" + image: "mads-baggesen.jpg" + - name: "Johanne Sundtoft" + employer: "Destination Aarhus" + image: "johanne-sundtoft.jpg" + - name: "Peter Andersson" + employer: "Eficode" + image: "peter-andersson.jpg" + - name: "Jonas Vinther" + employer: "Trifork" + image: "jonas-vinther.jpg" + + +organizer_email: "aarhus@devopsdays.org" # Put your organizer email address here + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +sponsors: + - id: eficode + level: gold + + +sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link + +# In this section, list the level of sponsorships and the label to use. +# You may optionally include a "max" attribute to limit the number of sponsors per level. For +# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all +# sponsorship for a specific level, it is best to remove the level. +sponsor_levels: + - id: gold + label: Gold +# max: 10 + - id: silver + label: Silver + max: 0 # This is the same as omitting the max limit. + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2022-amsterdam.yml b/data/events/2022-amsterdam.yml index f9bf0217ec8..86b5ad1f902 100644 --- a/data/events/2022-amsterdam.yml +++ b/data/events/2022-amsterdam.yml @@ -11,15 +11,13 @@ ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it # Note: we allow 2022-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) startdate: 2022-06-22T00:00:00+02:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. -enddate: 2022-06-24T23:59:59+02:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2022-06-24T23:59:59+02:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. # Leave CFP dates blank if you don't know yet, or set all three at once. -cfp_date_start: 2021-10-01T00:00:00+02:00 # start accepting talk proposals. -cfp_date_end: 2022-03-15T23:59:59+02:00 # close your call for proposals. -cfp_date_announce: 2022-04-01T23:59:59+02:00 # inform proposers of status +cfp_date_start: # start accepting talk proposals. +cfp_date_end: # close your call for proposals. +cfp_date_announce: # inform proposers of status - -cfp_open: "false" cfp_link: "" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. registration_date_start: 2022-01-01T00:00:00+02:00 # start accepting registration. Leave blank if registration is not open yet @@ -37,11 +35,11 @@ location_address: "Piet Heinkade 179, 1019 HC Amsterdam" #Optional - use the str masthead_background: "skyline-ams.jpg" nav_elements: # List of pages you want to show up in the navigation of your page. - # - name: propose + # - name: propose - name: location - # - name: registration - # - name: program - # - name: speakers + # - name: registration + # - name: program + # - name: speakers - name: sponsor - name: contact - name: conduct @@ -49,49 +47,68 @@ nav_elements: # List of pages you want to show up in the navigation of your page # icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ # url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site - # These are the same people you have on the mailing list and Slack channel. team_members: # Name is the only required field for team members. - name: "Thomas Krag" linkedin: "https://www.linkedin.com/in/vikingops/" twitter: "vikingopsio" + image: thomas.png - name: "Harm Boertien" linkedin: "https://www.linkedin.com/in/harmboertien/" twitter: "Harm_Ops" + image: harm.jpeg - name: "Yvo van Doorn" linkedin: "https://www.linkedin.com/in/yvovandoorn/" twitter: "yvov" + image: yvo.jpeg - name: "Daniel Paulus" linkedin: "https://www.linkedin.com/in/danielpaulus/" twitter: "dpnl87" website: "https://danielpaulus.com" + image: "daniel.jpg" - name: "Sheela Nistala" linkedin: "https://www.linkedin.com/in/sheelanistala/" twitter: "sheelanistala" + image: "sheela.png" - name: "Floor Drees" linkedin: "https://www.linkedin.com/in/floordrees/" twitter: "FloorDrees" + image: "floor.jpg" - name: "Walter Heck" linkedin: "https://www.linkedin.com/in/walterheck/" twitter: "walterheck" + image: "walter.jpg" + + - name: "Joep Piscaer" + linkedin: "https://www.linkedin.com/in/jpiscaer" + twitter: "jpiscaer" + image: "joep.png" - name: "Jos van Schouten" linkedin: "https://www.linkedin.com/in/josvanschouten/" twitter: "josvanschouten" + image: "jos.png" + + - name: "Sarah Gruneisen" + linkedin: "https://www.linkedin.com/in/sgruneisen/" + twitter: "avagasso" + image: "sarah.jpg" - name: "Peter Nijenhuis" linkedin: "https://www.linkedin.com/in/peter-nijenhuis-%E2%9C%93-lion-0b83751/" twitter: "Peter_Nijenhuis" + image: "peter.jpg" - name: "Sean Bovaird" linkedin: "https://www.linkedin.com/in/sbovaird" twitter: "srbovaird" + image: "sean.jpeg" organizer_email: "amsterdam@devopsdays.org" # Put your organizer email address here @@ -99,33 +116,33 @@ organizer_email: "amsterdam@devopsdays.org" # Put your organizer email address h # Check data/sponsors/ to use sponsors already added by others. sponsors: -sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link +sponsors_accepted: "yes" # Whether you want "Become a XXX Sponsor!" link # In this section, list the level of sponsorships and the label to use. # You may optionally include a "max" attribute to limit the number of sponsors per level. For # unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all # sponsorship for a specific level, it is best to remove the level. sponsor_levels: - - id: BBQ - label: BBQ - max: "1" - - id: coffee - label: Coffee - max: "1" - - id: gold - label: Gold - max: "8" - - id: silver - label: Silver - max: "7" - - id: recharge - label: "Power recharge" - max: "1" - - id: lanyard - label: Lanyard - max: "1" - - id: foodtrucks - label: "Food Trucks" - max: "3" - - id: bronze - label: Bronze + # - id: BBQ + # label: BBQ + # max: "1" + # - id: coffee + # label: Coffee + # max: "1" + # - id: gold + # label: Gold + # max: "8" + # - id: silver + # label: Silver + # max: "7" + # - id: recharge + # label: "Power recharge" + # max: "1" + # - id: lanyard + # label: Lanyard + # max: "1" + # - id: foodtrucks + # label: "Food Trucks" + # max: "3" + # - id: bronze + # label: Bronze diff --git a/data/events/2022-birmingham-uk.yml b/data/events/2022-birmingham-uk.yml new file mode 100644 index 00000000000..2d62ad7c1d8 --- /dev/null +++ b/data/events/2022-birmingham-uk.yml @@ -0,0 +1,97 @@ +name: "2022-birmingham-uk" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2022" # The year of the event. Make sure it is in quotes. +city: "Birmingham, UK" # The displayed city name of the event. Capitalize it. +event_twitter: "devopsdaysbrum" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Devopsdays is coming to birmingham!" # Edit this to suit your preferences +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" +event_logo: logo.png +event_group: "Birmingham, UK" + +# All dates are in unquoted 2022-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2019-01-04T00:00:00+02:00 +# variable: 2019-01-05T23:59:59+02:00 +# Note: we allow 2022-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) + +startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet. + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: # start accepting talk proposals. +cfp_date_end: # close your call for proposals. +cfp_date_announce: # inform proposers of status + +cfp_link: "" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. + +registration_date_start: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. +registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location +# +coordinates: "" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "birmingham" # Defaults to city, but you can make it the venue name. +# +location_address: "" #Optional - use the street address of your venue. This will show up on the welcome page if set. + +nav_elements: # List of pages you want to show up in the navigation of your page. + # - name: propose + # - name: location + # - name: registration + # - name: program + # - name: speakers + - name: sponsor + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Tom Withers" + employer: "Ministry of Justice" + image: "tom-withers.jpg" + twitter: "@tomtucka" + - name: "Alistair Hey" + employer: "Independent Consultant" + image: "alistair-hey.jpg" + twitter: "@alistair_hey" + - name: "Anaïs Urlichs" + employer: "Civo Cloud" + image: "anais-urlichs.jpg" + twitter: "@urlichsanais" + +organizer_email: "birmingham-uk@devopsdays.org" # Put your organizer email address here + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +sponsors: + # - id: samplesponsorname + # level: gold + # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. + # - id: arresteddevops + # level: community + +sponsors_accepted: "yes" # Whether you want "Become a XXX Sponsor!" link + +# In this section, list the level of sponsorships and the label to use. +# You may optionally include a "max" attribute to limit the number of sponsors per level. For +# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all +# sponsorship for a specific level, it is best to remove the level. +sponsor_levels: + - id: platinum + label: Platinum + max: 2 + - id: gold + label: Gold + max: 10 + - id: silver + label: Silver + max: 10 + - id: bronze + label: Bronze + max: 5 + - id: community + label: Community diff --git a/data/events/2022-boise.yml b/data/events/2022-boise.yml index c2b8d70afb7..7eb5833b270 100644 --- a/data/events/2022-boise.yml +++ b/data/events/2022-boise.yml @@ -10,8 +10,8 @@ ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it # variable: 2019-01-05T23:59:59+02:00 # Note: we allow 2022-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) -startdate: #2022-04-06T08:00:00-06:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. -enddate: #2022-04-07T19:00:00-06:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. +startdate: 2022-05-03T08:00:00-06:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2022-05-03T19:00:00-06:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. # Leave CFP dates blank if you don't know yet, or set all three at once. cfp_date_start: # start accepting talk proposals. @@ -24,24 +24,24 @@ registration_date_start: # start accepting registration. Leave blank if registra registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. registration_closed: "" #set this to true if you need to manually close registration before your registration end date -registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. +registration_link: "https://www.eventbrite.com/e/devopsdays-boise-2022-tickets-82046903497" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. # Location # -coordinates: "43.614893,-116.205161" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +coordinates: "43.614828, -116.205104" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html location: "Boise" # Defaults to city, but you can make it the venue name. # -location_address: +location_address: 850 W Front St, Boise, ID 83702 nav_elements: # List of pages you want to show up in the navigation of your page. # - name: propose - # - name: location + - name: location # - name: registration # - name: program # - name: speakers - name: sponsor - name: contact - - name: conduct + # - name: conduct # - name: example # icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ # url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site @@ -51,7 +51,6 @@ nav_elements: # List of pages you want to show up in the navigation of your page team_members: # Name is the only required field for team members. - name: "Robert Meyer" employer: "MedArrive.com" - twitter: "BDArcholite" github: "Robert-R-Meyer" linkedin: "https://www.linkedin.com/in/robertrmeyer/" - name: "Paul Remeis" @@ -59,16 +58,30 @@ team_members: # Name is the only required field for team members. twitter: "PaulRemeis" linkedin: "https://www.linkedin.com/in/paulremeis/" - name: "Jessica Adamson" - employer: "PagerDuty" + employer: "Gremlin" linkedin: "https://www.linkedin.com/in/jladamson/" + - name: "Julie Gunderson" + employer: "Gremlin" + twitter: "Julie_Gund" + linkedin: "https://www.linkedin.com/in/jladamson/" + - name: "Tommy Mouser" + linkedin: "https://www.linkedin.com/in/tommy-mouser-7a28393/" organizer_email: "boise@devopsdays.org" # Put your organizer email address here # List all of your sponsors here along with what level of sponsorship they have. # Check data/sponsors/ to use sponsors already added by others. sponsors: + - id: simplot + level: silver + - id: cradlepoint + level: platinum - id: 2016-intimetec level: platinum + - id: 2016-inuits + level: bronze + - id: clearwater + level: silver sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link diff --git a/data/events/2022-cairo.yml b/data/events/2022-cairo.yml new file mode 100644 index 00000000000..a6657ffaecc --- /dev/null +++ b/data/events/2022-cairo.yml @@ -0,0 +1,114 @@ +name: "2022-cairo" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2022" # The year of the event. Make sure it is in quotes. +city: "Cairo" # The displayed city name of the event. Capitalize it. +event_twitter: "" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Welcome to DevOpsDays Cairo 2022!" # Edit this to suit your preferences +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" + +# All dates are in unquoted YYYY-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2019-01-04T00:00:00+02:00 +# variable: 2019-01-05T23:59:59+02:00 +# Note: we allow YYYY-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) + +startdate: 2022-09-22T00:00:00+02:00 +enddate: 2022-09-22T23:59:59+02:00 + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: 2021-05-24T00:00:00+02:00 # start accepting talk proposals. +cfp_date_end: 2021-07-31T00:00:00+02:00 # close your call for proposals. +cfp_date_announce: # inform proposers of status + +cfp_open: "false" +cfp_link: "https://www.papercall.io/cairo2021" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. + +registration_date_start: # start accepting registration. Leave blank if registration is not open yet +registration_date_end: # close registration. Leave blank if registration is not open yet. + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location + + +coordinates: "" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "" # Defaults to city, but you can make it the venue name. + + +location_address: "Online Event! Stay Safe!" #Optional - use the street address of your venue. This will show up on the welcome page if set. + +nav_elements: # List of pages you want to show up in the navigation of your page. +# - name: propose +# - name: location +# - name: local +# - name: registration +# url: https://www.secc.org.eg/Event_Registration.asp +# - name: agenda +# url: https://assets.devopsdays.org/events/2020/cairo/DevopsDays-Cairo-2020-Agenda.pdf +# - name: speakers + - name: sponsor + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Ahmed Ameen" + employer: "ITIDA - SECC" + linkedin: "https://www.linkedin.com/in/aameen79/" + - name: "Ghada Soliman" + employer: "Orange Labs" + linkedin: "https://www.linkedin.com/in/ghada-soliman-2768063/" + - name: "Mohamed Fawzy" + employer: "DXC Technology" + linkedin: "https://www.linkedin.com/in/mobayomie/" + - name: "Samar Fadl" + employer: "ATOS" + linkedin: "https://www.linkedin.com/in/samar-fadl-13767628/" + - name: "Reham Saleh" + employer: "ITIDA - SECC" + linkedin: "https://www.linkedin.com/in/reham-saleh-30405240/" + - name: "Sherine FaragAllah" + employer: "ITIDA - SECC" + linkedin: "https://www.linkedin.com/in/sherine-faragallah-06a998189/" + + +organizer_email: "cairo@devopsdays.org" # Put your organizer email address here + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +sponsors: + - id: foss + level: community + - id: egyptinnovate + level: community + - id: tiec + level: community + - id: amecse + level: community + + #- id: egyptinnovate + # level: community + # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. + +sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link + +# In this section, list the level of sponsorships and the label to use. +# You may optionally include a "max" attribute to limit the number of sponsors per level. For +# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all +# sponsorship for a specific level, it is best to remove the level. +sponsor_levels: + - id: platinum + label: Platinum + max: 3 + - id: gold + label: Gold + max: 5 + - id: silver + label: Silver + max: 0 # This is the same as omitting the max limit. + - id: community + label: Community + max: 4 diff --git a/data/events/2022-chicago.yml b/data/events/2022-chicago.yml index e1fb3fa4051..ea98a71c2d3 100644 --- a/data/events/2022-chicago.yml +++ b/data/events/2022-chicago.yml @@ -14,9 +14,9 @@ startdate: 2022-05-10T00:00:00-05:00 enddate: 2022-05-11T00:00:00-05:00 # Leave CFP dates blank if you don't know yet, or set all three at once. -cfp_date_start: # start accepting talk proposals. -cfp_date_end: # close your call for proposals. -cfp_date_announce: # inform proposers of status +cfp_date_start: 2021-11-01T00:00:00-05:00 # start accepting talk proposals. +cfp_date_end: 2022-01-31T00:00:00-05:00 # close your call for proposals. +cfp_date_announce: 2022-02-28T00:00:00-05:00 # inform proposers of status cfp_link: "" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. @@ -36,12 +36,12 @@ location: "UIC Forum" # Defaults to city, but you can make it the venue name. location_address: "" #Optional - use the street address of your venue. This will show up on the welcome page if set. nav_elements: # List of pages you want to show up in the navigation of your page. - # - name: propose + - name: propose - name: location # - name: registration # - name: program # - name: speakers - # - name: sponsor + - name: sponsor - name: contact - name: conduct # - name: example @@ -155,8 +155,21 @@ sponsors: # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. - id: arresteddevops level: community + + # Gold Sponsors + - id: teleport + level: gold + - id: trilio + level: gold + + #Silver Sponsors + + + #Bronze Sponsors + - id: env0 + level: bronze -sponsors_accepted : "no" # Whether you want "Become a XXX Sponsor!" link +sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link # In this section, list the level of sponsorships and the label to use. # You may optionally include a "max" attribute to limit the number of sponsors per level. For diff --git a/data/events/2022-dallas.yml b/data/events/2022-dallas.yml index 07d2a20b0ad..443c8a1e4a5 100644 --- a/data/events/2022-dallas.yml +++ b/data/events/2022-dallas.yml @@ -187,7 +187,7 @@ sponsors: # level: gold # - id: xmatters # level: gold - - id: launch-darkly-before-20200828 + - id: launch-darkly level: gold - id: arresteddevops level: media diff --git a/data/events/2022-denver.yml b/data/events/2022-denver.yml index db07eeed068..75e67b667c7 100644 --- a/data/events/2022-denver.yml +++ b/data/events/2022-denver.yml @@ -52,22 +52,17 @@ team_members: # Name is the only required field for team members. - name: "Tavis Aitken" twitter: "tavisto" employer: "Splunk" - - name: "Jason Hand" - twitter: "jasonhand" - employer: "Microsoft" - name: "Beau Christensen" twitter: "beauchristensen" employer: "Splunk" - name: "Nick Huanca" twitter: "NickHuanca" - name: "Carla Murray" - employer: "Oracle Data Cloud" + employer: "Oracle Advertising" twitter: "carlajmurray" - name: "Matt Knox" twitter: "mknox42" employer: "Splunk" - - name: "Lilith Moon Cohen" - twitter: "lilithmooncohen" - name: "Jason Sharp" twitter: "1971hemicuda" - name: "Erin Atkinson" diff --git a/data/events/2022-geneva.yml b/data/events/2022-geneva.yml index 17d5bdd7ea4..7aaf2825af8 100644 --- a/data/events/2022-geneva.yml +++ b/data/events/2022-geneva.yml @@ -16,7 +16,7 @@ enddate: 2022-02-08T17:00:00+01:00 # The end date of your event. Leave blank if # Leave CFP dates blank if you don't know yet, or set all three at once. cfp_date_start: 2021-06-07T08:00:00+01:00 #start accepting talk proposals. -cfp_date_end: 2021-10-15T23:59:00+01:00 # close your call for proposals. +cfp_date_end: 2021-11-15T23:59:00+01:00 # close your call for proposals. cfp_date_announce: 2021-11-15T12:00:00+01:00 # inform proposers of status #cfp_link: "https://cfpdevopsdaysge.hidora.com" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. @@ -35,7 +35,7 @@ location: "Geneva" # Defaults to city, but you can make it the venue name. location_address: "Campus de Battelle, Rue de la Tambourine 17, 1227 Carouge" #Optional - use the street address of your venue. This will show up on the welcome page if set. nav_elements: # List of pages you want to show up in the navigation of your page. - - name: propose +# - name: propose - name: location - name: newsletter - name: registration @@ -52,8 +52,8 @@ nav_elements: # List of pages you want to show up in the navigation of your page # These are the same people you have on the mailing list and Slack channel. team_members: # Name is the only required field for team members. - name: "Matteo Mazzeri" - employer: "ENALEAN" - website: "https://tuleap.org/" + employer: "CKatalyzen" + website: "https://mazzeri.net/" twitter: "matemaz" linkedin: "https://www.linkedin.com/in/mazzeri" image: matteo.jpg @@ -69,9 +69,15 @@ team_members: # Name is the only required field for team members. employer: "Value IT Swiss" website: "https://valueit.ch/" linkedin: "https://www.linkedin.com/in/deniger/" - twitter: "DenigerFrederic" image: fred.jpg bio: "Technical Team Leader with more than 15 years' experience managing complex IT projects in fast-paced environments. Dedicated team player with an in-depth knowledge of agile methodology and the ability to implement DevOps practices to reduce development times and improve quality. Results-focused and adaptable. Track record of delivering successful projects in a variety of sectors e.g. banking, scientific community, international organizations." + - name: "Tim Izzo" + employer: "Octree" + linkedin: "https://www.linkedin.com/in/tim-izzo/" + twitter: 5ika_ + website: "https://octree.ch/" + image: tim.jpg + bio: "Co-founder of Octree, lecturer at CREA and Sunday hacker, Tim Izzo has a history at the crossroads between network engineering, security and development. He is passionate about Open-Source, circular economy and distributed governance. Through his background, he has followed the evolution of DevOps since its inception." - name: "Gaelle Delesderrier" employer: M.I.C.E. spirit website: https://mice-spirit.com @@ -91,8 +97,32 @@ organizer_email: "geneva@devopsdays.org" # Put your organizer email address here # List all of your sponsors here along with what level of sponsorship they have. # Check data/sponsors/ to use sponsors already added by others. sponsors: + - id: techfirm + level: event + - id: hidora + level: gold + - id: camptocamp + level: gold + - id: dynatrace + level: gold + - id: trilio + level: gold + - id: redhat + level: gold + - id: valueitswiss + level: silver + - id: sokube + level: silver + - id: stacksciences + level: silver + - id: dbi-services + level: silver + - id: socraft + level: bronze - id: swissdevjobs level: community + - id: heg-geneva + level: community sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link diff --git a/data/events/2022-los-angeles.yml b/data/events/2022-los-angeles.yml index 4141f5bacf9..db091de0ec8 100644 --- a/data/events/2022-los-angeles.yml +++ b/data/events/2022-los-angeles.yml @@ -24,6 +24,9 @@ registration_date_end: 2022-03-05T00:00:00-08:00 # close registration. Leave bla registration_closed: "" #set this to true if you need to manually close registration before your registration end date registration_link: "https://register.socallinuxexpo.org/reg6/" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. +# Background +masthead_background: "DevOpsDayLA_Banner.jpg" + # Location coordinates: "34.1436537,-118.1452085" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html location: "Pasadena Convention Center" # Defaults to city, but you can make it the venue name. @@ -32,7 +35,6 @@ location_address: "300 E Green St, Pasadena, CA 91101" #Optional - use the stree nav_elements: # List of pages you want to show up in the navigation of your page. # - name: program # - name: speakers - # - name: volunteer - name: venue url: https://www.socallinuxexpo.org/scale/19x/venue - name: registration @@ -40,8 +42,10 @@ nav_elements: # List of pages you want to show up in the navigation of your page - name: CFP url: https://docs.google.com/forms/d/e/1FAIpQLSewxucXuZ5nmZYX-nBitrmnr1ZA-O7oc33kheNvoRw1ufEbgg/viewform - name: sponsor + - name: volunteer - name: contact - name: conduct + - name: about # - name: example # icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ # url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site @@ -88,11 +92,13 @@ organizer_email: "los-angeles@devopsdays.org" # Put your organizer email address # List all of your sponsors here along with what level of sponsorship they have. # Check data/sponsors/ to use sponsors already added by others. sponsors: - # - id: samplesponsorname - # level: gold - # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. - # - id: arresteddevops - # level: community + - id: lightstep + level: gold + - id: blameless + level: silver + - id: scale + level: community + url: https://www.socallinuxexpo.org/scale/19x sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link diff --git a/data/events/2022-portland-or.yml b/data/events/2022-portland-or.yml new file mode 100644 index 00000000000..f5d4b71e905 --- /dev/null +++ b/data/events/2022-portland-or.yml @@ -0,0 +1,92 @@ +name: "2022-portland-or" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2022" # The year of the event. Make sure it is in quotes. +city: "Portland, OR" # The displayed city name of the event. Capitalize it. +event_twitter: "devopsdayspdx" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Devopsdays is coming back to Portland, OR!" # Edit this to suit your preferences +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" + +# All dates are in unquoted 2022-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2019-01-04T00:00:00+02:00 +# variable: 2019-01-05T23:59:59+02:00 +# Note: we allow 2022-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) + +startdate: 2022-09-19T00:00:00-07:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2022-09-21T00:00:00-07:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: # start accepting talk proposals. +cfp_date_end: # close your call for proposals. +cfp_date_announce: # inform proposers of status + +cfp_link: "" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. + +registration_date_start: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. +registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location +# +coordinates: "45.528378, -122.663138" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Oregon Convention Center, Portland, OR" # Defaults to city, but you can make it the venue name. +# +location_address: "777 NE Martin Luther King Jr Blvd, Portland, OR 97232" #Optional - use the street address of your venue. This will show up on the welcome page if set. + +nav_elements: # List of pages you want to show up in the navigation of your page. + # - name: propose + # - name: location + # - name: registration + # - name: program + # - name: speakers + - name: sponsor + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Bill Weiss" + twitter: "billweiss" + - name: "Alastair Drong" + twitter: "dev_dull" + - name: "Joe Nuspl" + twitter: "joenuspl" + - name: "Michelle Carroll" + twitter: "miiiiiche" + - name: "Rich Burroughs" + twitter: "richburroughs" + - name: "Megan Guiney" + twitter: "meganguiney" + - name: "Tiffany Longworth" + - name: "Will Ellett" + - name: "Jason Yee" + twitter: "gitbisect" + +organizer_email: "portland-or@devopsdays.org" # Put your organizer email address here + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +sponsors: + +sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link + +# In this section, list the level of sponsorships and the label to use. +# You may optionally include a "max" attribute to limit the number of sponsors per level. For +# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all +# sponsorship for a specific level, it is best to remove the level. +sponsor_levels: + - id: platinum + label: Platinum + max: 1 + - id: gold + label: Gold + - id: silver + label: Silver + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/data/events/2022-raleigh.yml b/data/events/2022-raleigh.yml index cc30eb796ef..7a8f58c51fd 100644 --- a/data/events/2022-raleigh.yml +++ b/data/events/2022-raleigh.yml @@ -14,11 +14,11 @@ startdate: 2022-04-13T00:00:00-04:00 # The start date of your event. Leave blan enddate: 2022-04-14T23:59:58-04:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. # Leave CFP dates blank if you don't know yet, or set all three at once. -cfp_date_start: # start accepting talk proposals. -cfp_date_end: # close your call for proposals. +cfp_date_start: 2021-10-18T23:59:58-04:00 # start accepting talk proposals. +cfp_date_end: 2021-12-31T23:59:58-04:00 # close your call for proposals. cfp_date_announce: # inform proposers of status -cfp_link: "" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. +cfp_link: "https://forms.gle/aoz6XvtQYtm8HuQY9" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. registration_date_start: 2021-06-20T00:00:00-04:00 # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. registration_date_end: 2022-04-14T23:59:58-04:00 # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. @@ -34,13 +34,13 @@ location: "McKimmon Conference & Training Center" # Defaults to city, but you ca location_address: "1101 Gorman Street, Raleigh, NC 27606" #Optional - use the street address of your venue. This will show up on the welcome page if set. nav_elements: # List of pages you want to show up in the navigation of your page. - # - name: propose + - name: propose - name: location - name: registration url: "https://www.eventbrite.com/e/devopsdays-raleigh-2022-tickets-149971423565?aff=ebdssbdestsearch" # - name: program # - name: speakers - # - name: sponsor + - name: sponsor - name: contact - name: conduct # - name: example diff --git a/data/events/2022-vitoria.yml b/data/events/2022-vitoria.yml index cf21494c694..38990faddc8 100644 --- a/data/events/2022-vitoria.yml +++ b/data/events/2022-vitoria.yml @@ -10,38 +10,40 @@ ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it # variable: 2019-01-05T23:59:59+02:00 # Note: we allow 2022-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) -startdate: 2022-02-05T09:00:00-03:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. -enddate: 2022-02-05T18:00:00-03:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. +startdate: 2022-02-11T09:00:00-03:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2022-02-12T18:00:00-03:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. # Leave CFP dates blank if you don't know yet, or set all three at once. -cfp_date_start: # start accepting talk proposals. -cfp_date_end: # close your call for proposals. -cfp_date_announce: # inform proposers of status +cfp_date_start: 2021-10-14T10:00:00-03:00 # start accepting talk proposals. +cfp_date_end: 2021-11-15T07:00:00-03:00 # close your call for proposals. +cfp_date_announce: 2021-10-14T08:00:00-03:00 # inform proposers of status -cfp_link: "" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. +cfp_open: "true" +cfp_link: "https://www.papercall.io/devopsdaysvitoria2022" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. -registration_date_start: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. -registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. +registration_date_start: 2021-10-18 # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. +registration_date_end: 2022-01-10 # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. registration_closed: "" #set this to true if you need to manually close registration before your registration end date -registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. +registration_link: "https://www.sympla.com.br/devopsdays-vitoria-2022__1375471" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. # Location # -coordinates: "" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html -location: "Vitoria" # Defaults to city, but you can make it the venue name. +coordinates: "-20.2927555,-40.3008919" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Local: Grand Hall - Vitória/ES" # Defaults to city, but you can make it the venue name. # -location_address: "" #Optional - use the street address of your venue. This will show up on the welcome page if set. +location_address: "R. Dr. João Carlos de Souza - Barro Vermelho, Vitória - ES, 29045-410" #Optional - use the street address of your venue. This will show up on the welcome page if set. nav_elements: # List of pages you want to show up in the navigation of your page. # - name: propose - # - name: location - # - name: registration + - name: location +# - name: registration # - name: program # - name: speakers - name: sponsor - name: contact - name: conduct +# - name: zero # - name: example # icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ # url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site @@ -140,22 +142,22 @@ team_members: # Name is the only required field for team members. github: "" twitter: "dodaracaju" image: "igor-macedo.jpg" - - name: "Frederico Boaventura" - employer: "self" - bio: "cat < /dev/urandom > bio" - linkedin: "https://www.linkedin.com/in/igor-macedo/" - website: "https://fboaventura.dev" - github: "fboaventura" - twitter: "fboaventura" - image: "frederico-boaventura.png" - name: "Jandson Mendes" - employer: "" + employer: "Inflor" bio: "" linkedin: "https://www.linkedin.com/in/jandson-oliveira/" website: "" github: "jandsonmendes25" twitter: "jandson_mendes" image: "jandson-mendes.jpg" + - name: "Elayne Lemos" + employer: "Sysvale" + bio: "Analista DevOps na Sysvale Softgroup, bem como voluntária e community staff no Linux Professional Institute. Engenheira de Computação em formação. Apaixonada por desenvolvimento e tecnologias de código aberto. Tendo como áreas de interesse: DevOps, Segurança da Informação e Infraestrutura." + linkedin: "https://linkedin.com/in/elaynelemos" + website: "" + github: "elaynelemos" + twitter: "elaynelemos" + image: "elaynelemos.jpg" organizer_email: "vitoria@devopsdays.org" # Put your organizer email address here @@ -175,13 +177,32 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link # unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all # sponsorship for a specific level, it is best to remove the level. sponsor_levels: + - id: platinum + label: Platinum - id: gold label: Gold -# max: 10 - id: silver label: Silver - max: 0 # This is the same as omitting the max limit. - id: bronze label: Bronze - - id: community - label: Community + +sponsors: + - id: LPI + level: gold + url: https://www.lpi.org/ + - id: linuxtips + level: gold + url: https://www.linuxtips.io/ + - id: spiritsec + level: gold + url: https://www.spiritsec.com/ + - id: globoofficial + level: silver + url: https://www.globo.com/ + - id: willbank + level: platinum + url: https://www.willbank.com.br/ + - id: flexa + level: platinum + url: https://flexa.cloud/ + diff --git a/data/events/2022-zurich.yml b/data/events/2022-zurich.yml new file mode 100644 index 00000000000..23fe44a4a44 --- /dev/null +++ b/data/events/2022-zurich.yml @@ -0,0 +1,165 @@ +name: "2022-zurich" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2022" # The year of the event. Make sure it is in quotes. +city: "Zürich (Winterthur)" # The displayed city name of the event. Capitalize it. +event_twitter: "DevOpsZH" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "DevOpsDays is coming to Zürich!" # Edit this to suit your preferences +ga_tracking_id: "UA-174260535-2" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" +event_group: "Zürich" + +# All dates are in unquoted 2022-MM-DDTHH:MM:SS+TZ:TZ, like this: +# variable: 2022-09-08T00:00:00+02:00 +# variable: 2022-09-09T23:59:59+02:00 +# Note: we allow 2022-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) + +startdate: 2022-05-31T00:00:00+02:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2022-06-01T23:59:59+02:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. + +# Leave CFP dates blank if you don't know yet, or set all three at once. +# cfp_date_start: 2022-02-04T00:00:00+02:00 # start accepting talk proposals. +# cfp_date_end: 2022-05-31T23:59:59+02:00 # close your call for proposals. +# cfp_date_announce: 2022-07-01T00:00:00+02:00 # inform proposers of status + +cfp_open: "false" +# cfp_link: "https://sessionize.com/devopsdayszh-2022/" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. + +# registration_date_start: 2022-02-01T00:00:00+02:00 +# registration_date_end: 2022-09-06T00:00:00+02:00 + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +#registration_link: "https://ti.to/dod/dodzh2020" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. + +# Location +# +coordinates: "47.497854, 8.731663" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "Alte Kaserne Winterthur" # Defaults to city, but you can make it the venue name. +# +location_address: "Technikumstrasse 8, 8400 Winterthur, Switzerland" #Optional - use the street address of your venue. This will show up on the welcome page if set. + +nav_elements: # List of pages you want to show up in the navigation of your page. +# - name: propose +# - name: program +# - name: speakers + - name: location +# - name: registration +# - name: sponsor + - name: diversity + - name: covid + - name: contact + - name: conduct +# - name: example +# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ +# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site + + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Martin Thalmann" + twitter: "martin_thalmann" + employer: "Swisscom AG" + bio: "I’m a passionate DevOps Enthusiast who strongly believes in the power of this movement. I’m currently helping a Swiss telco operator in adapting DevOps principles in a large enterprise. Beside that I’m co-organizer of the [DevOps Enthusiast Meetup in Zurich](https://www.meetup.com/DevOps-Meetup-Zurich/). I do have a background as a Software Engineer and experience in several Line- and Project-Management positions." + github: "" + facebook: "" + linkedin: "https://www.linkedin.com/in/martinthalmann/" + website: "" + image: "martin-thalmann.jpg" + - name: "Dirk Lehmann" + twitter: "doergn" + employer: "SAP" + bio: "

Dirk is a DevOps evangelist and Continuous Delivery expert at SAP.

Since 2001 Dirk worked in various roles at SAP including Development and Operations.
Together with his former team \"TwoGo by SAP\" he established the first Continuous Delivery implementation at SAP, delivering value daily to their customers.

In his current role, Dirk is a Cloud Quality Coach at SAP with focus on Continuous Delivery and DevOps practices.

Dirk is a frequent speaker at international conferences on DevOps and Continuous Delivery.

" + linkedin: "https://www.linkedin.com/in/dirk-lehmann-7712bb125/" + github: "" + facebook: "" + image: "dirk-lehmann.jpg" + - name: "Nadine Biedermann" + employer: "Swisscom AG" + bio: "

Metaphorically, Nadine can conquer the world with her clever quips and her charme. Literally, Nadine's wit and her creativity will enhance your Marketing and Social Media experience of the DevOpsDays 2019.

" + linkedin: "https://www.linkedin.com/in/nadine-biedermann-46436516b" + image: "nadine-biedermann.jpg" + - name: "Romano Roth" + twitter: "RomanoRoth" + employer: "Zühlke Engineering AG" + bio: "

I'm an experienced software consultant and DevOps enthusiast working at Zühlke. My passion is helping companies bringing people, processes and technology together so that they can deliver continuously value to their customers.

" + github: "https://github.com/RomanoRoth" + facebook: "https://www.facebook.com/romanoroth/" + website: "https://www.romanoroth.com" + linkedin: "https://www.linkedin.com/in/romanoroth/" + image: "romano-roth.jpg" + - name: "Carsten Plum" + bio: "

I am passionate about everything agile and human centered. Having started my career in an old school waterfall environment more than 20 years ago as a software engineer and project manager, I am now happy to enable teams and large organisations to establish agile methods and DevOps. I specifically like the combination (and challenges) of technical and cultural aspects.

" + Website: https://www.xing.com/profile/Carsten_Plum2/ + employer: "Federal Office of Information Technology" + github: "" + facebook: "" + linkedin: "https://www.linkedin.com/in/romanoroth/" + image: "carsten-plum.jpg" + - name: "Tobias Weinmann" + bio: "

Having worked as a developer, systems engineer and team lead in IT operations, the ideas and concepts behind DevOps are very close to my heart. As I am passionate about coding since my teenage years, I am fascinated by concepts like Infrastructure as Code, Social Coding, and cloud native technologies trying to get hands-on whenever possible. I enjoy lateral thinking and my basic premise is that we cannot solve our problems with the same thinking we used when we created them (Albert Einstein). In my current role I dedicate all my energy to introducing and spreading DevOps principles and practices in the broader organization.

" + linkedin: "https://www.linkedin.com/in/tobias-weinmann" + twitter: "Wankinobi75" + github: "tweinmann" + employer: "Swiss Re" + image: "tobias-weinmann.jpg" + - name: "Lorena Dütsch" + employer: "Swisscom AG" + bio: "

I love to create visual design, UX & UI Design, infographics, pictograms and so on. With my creativity I will participate in marketing and social media for DevOpsDays 2020.

" + linkedin: "https://www.linkedin.com/in/lorenadütsch" + image: "lorena-duetsch.png" + - name: "Sebastian Zillessen" + bio: "

I am a Senior Software Engineer. Since 2016 I am focusing on agile software development processes, clean code, infrastructure as code and DevOps specific development and release processes. My passion lies in Full stack enterprise application development which I approach with an entrepreneurial mindset.

" + image: "sebastian-zillessen.jpeg" + employer: "Zühlke Engineering AG" + twitter: "sebzill" + linkedin: "https://www.linkedin.com/in/sebastianzillessen/" + - name: "Franziska Bühler" + bio: "

Franziska loves to combine her favorite topics DevOps, IT security and open source software. And that's exactly what she can pursue as an architect at Puzzle ITC! As a former speaker at the DevOpsDays Zurich, organizer of the ModSecurity CRS Meetup Bern and an enthusiastic OWASP member, Franziska also has the opportunity to share her passion with others. When she isn't disassembling highly optimized regexes or automating security, she enjoys spending time with her family.

" + image: "franziska-buehler.jpeg" + employer: "Puzzle ITC" + github: "franbuehler" + twitter: "@bufrasch" + linkedin: "https://www.linkedin.com/in/franziska-buehler-bb037a163/" + - name: "Noëmi Kruesi" + twitter: "" + employer: "Swisscom AG" + bio: "

It is a well-known fact that girls just wanna have fun. It is also known that companies that incorporate DevOps get more done. How do these two facts relate, you ask?

+

Meet Noëmi Krüsi, a girl who gets stuff done. Her strengths and talents lie in design and administration. As a creative allrounder she will be assisting with the design and social media of the DevOpsDays 2018.

" + github: "" + facebook: "" + linkedin: "https://www.linkedin.com/in/noëmi-krüsi-992436127/" + website: "" + image: "noemi-krusi.jpg" + - name: "Tobias Brunner" + twitter: "tobruzh" + employer: "VSHN AG" + bio: "Tobias (aka tobru) is a DevOps Engineer and Partner at VSHN and one of the founding members of VSHN. He loves Open Source and everything about state-of-the-art technologies like Docker, Kubernetes and OpenShift. In his day job he is responsible for the Container Platform team at VSHN, works on the next big thing and brings APPUiO - The Swiss Container Platform - to the next level." + github: "tobru" + facebook: "" + linkedin: "https://www.linkedin.com/in/tobru/" + website: "https://tobru.ch/" + image: "tobias-brunner.jpg" + - name: "Julia Faust" + bio: "

Julia loves to communicate and to bring people and solutions together. As a Financial Controller for the IT development department of a Swiss Telco, she accompanies the transformation into an agile setup from the beginning.

DevOps principles such as \"build it, run it\", autonomy of the team, as well as short and reasonable planning processes motivate her a lot. Julia is thrilled by discussing the basic ideas and causes of agility and to inspire others.

" + image: "julia-faust.jpg" + - name: "David Kilchenmann" + twitter: "@DKilchenmann" + employer: "Puzzle ITC" + bio: "

David is Key Account Manager at Puzzle ITC, an open-source IT company based in Bern, Zurich, Basel & Tübingen(DE). He loves how container technologies changed the way software is developed and run, but still sees a lot of potential within other organizations to adopt a DevOps mindset. At Puzzle he is working in the account management and assists the product development of several open source solutions like Hitobito, APPUiO, PuzzleTime & Liima. Before Puzzle he was leading the Swisscom Software Day for two iterations and promoting the Swisscom software culture within the company.

" + github: "" + facebook: "" + linkedin: "https://www.linkedin.com/in/david-kilchenmann-004aaa68/" + website: "" + image: "david-kilchenmann.jpeg" + - name: "Selina Reist" + employer: "Federal Office of Information Technology" + bio: "

I am an enthusiast for everything visual:photography, movies and animations, pictograms, infofraphics, visual design, graphical recordings, UX-Design. I also like to combine these skills in crossfunctional teams to enable app development, transformation processes and last but not least communicate and teach DevOps practices in large federal organizations

" + image: "selina-reist.jpg" + - name: "Vittorio Boccone" + twitter: "drbokko" + employer: "Dectris Ltd." + bio: "Vittorio grew up in the a world where hardware and software are in perfect equilibrium. At 8 he started customizing and modifying anything with an engine or a CPU. Curious about the nature of things he later became a detector and accelerator physicist. After 13 years at CERN, he's now often seen at Dectris happily developing Dectris X-ray detectors. He's comfortable with any lab equipment, programming language or particle accelerator." + github: "https://github.com/drbokko" + facebook: "" + linkedin: "https://www.linkedin.com/in/vittorio-boccone-1998a94/" + website: "" + image: "vittorio-boccone.jpg" +organizer_email: "zurich@devopsdays.org" # Put your organizer email address here + diff --git a/data/sponsors/applied-materials.yml b/data/sponsors/applied-materials.yml new file mode 100644 index 00000000000..e879c43d4df --- /dev/null +++ b/data/sponsors/applied-materials.yml @@ -0,0 +1,2 @@ +name: "Applied Materials" +url: "https://www.appliedmaterials.com/en-il/company/careers" diff --git a/data/sponsors/blameless.yml b/data/sponsors/blameless.yml new file mode 100644 index 00000000000..121e0133305 --- /dev/null +++ b/data/sponsors/blameless.yml @@ -0,0 +1,3 @@ +name: "Blameless" +url: "https://www.blameless.com/" +twitter: blamelesshq diff --git a/data/sponsors/cloudinary-before-20211111.yml b/data/sponsors/cloudinary-before-20211111.yml new file mode 100644 index 00000000000..8626d2c2188 --- /dev/null +++ b/data/sponsors/cloudinary-before-20211111.yml @@ -0,0 +1,2 @@ +name: "cloudinary" +url: "http://www.cloudinary.com/" diff --git a/data/sponsors/eficode-before-20211021.yml b/data/sponsors/eficode-before-20211021.yml new file mode 100644 index 00000000000..d5c8d647f73 --- /dev/null +++ b/data/sponsors/eficode-before-20211021.yml @@ -0,0 +1,3 @@ +name: "Eficode" +url: "https://www.eficode.com/home" +twitter: "@eficode" diff --git a/data/sponsors/fearless-hutch.yml b/data/sponsors/fearless-hutch.yml new file mode 100644 index 00000000000..cd4073c46f4 --- /dev/null +++ b/data/sponsors/fearless-hutch.yml @@ -0,0 +1,3 @@ +name: "Fearless" +url: "http://www.fearless.tech/" +twitter: "fearlessbmore" diff --git a/data/sponsors/gk8.yml b/data/sponsors/gk8.yml new file mode 100644 index 00000000000..344e9bcc2fc --- /dev/null +++ b/data/sponsors/gk8.yml @@ -0,0 +1,2 @@ +name: "GK8" +url: "https://www.gk8.io/" diff --git a/data/sponsors/glaxosmithkline.yml b/data/sponsors/glaxosmithkline.yml new file mode 100644 index 00000000000..299da1f0bd0 --- /dev/null +++ b/data/sponsors/glaxosmithkline.yml @@ -0,0 +1,2 @@ +name: "GlaxoSmithKline" +url: "https://pl.gsk.com/pl/" diff --git a/data/sponsors/globoofficial.yml b/data/sponsors/globoofficial.yml new file mode 100644 index 00000000000..c70b32f9292 --- /dev/null +++ b/data/sponsors/globoofficial.yml @@ -0,0 +1,2 @@ +name: "globoofficial" +url: "https://www.globo.com.br/" diff --git a/data/sponsors/homelight.yml b/data/sponsors/homelight.yml new file mode 100644 index 00000000000..baef520a2e2 --- /dev/null +++ b/data/sponsors/homelight.yml @@ -0,0 +1,3 @@ +name: "HomeLight" +url: "https://www.homelight.com/net-proceeds-calculator" +twitter: homelightapp diff --git a/data/sponsors/kaltura.yml b/data/sponsors/kaltura.yml new file mode 100644 index 00000000000..c5c5987c93d --- /dev/null +++ b/data/sponsors/kaltura.yml @@ -0,0 +1,3 @@ +name: "Kaltura" +url: "https://kaltura.com/" +twitter: "kaltura" diff --git a/data/sponsors/launch-darkly-before-20210928.yml b/data/sponsors/launch-darkly-before-20210928.yml new file mode 100644 index 00000000000..a01bdbe957c --- /dev/null +++ b/data/sponsors/launch-darkly-before-20210928.yml @@ -0,0 +1,2 @@ +name: "LaunchDarkly" +url: "http://www.launchdarkly.com/" diff --git a/data/sponsors/merixstudio.yml b/data/sponsors/merixstudio.yml new file mode 100644 index 00000000000..1fe8d78ad7e --- /dev/null +++ b/data/sponsors/merixstudio.yml @@ -0,0 +1,2 @@ +name: "Merixstudio" +url: "https://www.merixstudio.com/" diff --git a/data/sponsors/merkely.yml b/data/sponsors/merkely.yml new file mode 100644 index 00000000000..481dd721090 --- /dev/null +++ b/data/sponsors/merkely.yml @@ -0,0 +1,3 @@ +name: Merkely +url: https://www.merkely.com/ +twitter: "@merkely" diff --git a/data/sponsors/neuralegion.yml b/data/sponsors/neuralegion.yml new file mode 100644 index 00000000000..e60ab2b4f15 --- /dev/null +++ b/data/sponsors/neuralegion.yml @@ -0,0 +1,2 @@ +name: "NeuraLegion" +url: "https://www.neuralegion.com/" diff --git a/data/sponsors/next-insurance.yml b/data/sponsors/next-insurance.yml new file mode 100644 index 00000000000..e4123fa90b5 --- /dev/null +++ b/data/sponsors/next-insurance.yml @@ -0,0 +1,2 @@ +name: "Next Insurance" +url: "https://www.nextinsurance.com/" diff --git a/data/sponsors/nextstep.yml b/data/sponsors/nextstep.yml new file mode 100644 index 00000000000..ea1c6e13971 --- /dev/null +++ b/data/sponsors/nextstep.yml @@ -0,0 +1,2 @@ +name: "Next Step" +url: "http://icnextstep.com/" \ No newline at end of file diff --git a/data/sponsors/observiq.yml b/data/sponsors/observiq.yml new file mode 100644 index 00000000000..0b810782e1e --- /dev/null +++ b/data/sponsors/observiq.yml @@ -0,0 +1,2 @@ +name: "observiq" +url: "https://observiq.com/" diff --git a/data/sponsors/profisea.yml b/data/sponsors/profisea.yml new file mode 100644 index 00000000000..ac282cb2fa5 --- /dev/null +++ b/data/sponsors/profisea.yml @@ -0,0 +1,2 @@ +name: "PROFISEA" +url: "https://profisea.com/" diff --git a/data/sponsors/riskmethods.yml b/data/sponsors/riskmethods.yml new file mode 100644 index 00000000000..fb2cda2fbe4 --- /dev/null +++ b/data/sponsors/riskmethods.yml @@ -0,0 +1,2 @@ +name: "Riskmethods" +url: "https://www.riskmethods.net/" diff --git a/data/sponsors/snappy.yml b/data/sponsors/snappy.yml new file mode 100644 index 00000000000..3c07d2238be --- /dev/null +++ b/data/sponsors/snappy.yml @@ -0,0 +1,2 @@ +name: "snappy" +url: "https://snappy.com/" diff --git a/data/sponsors/socraft.yml b/data/sponsors/socraft.yml new file mode 100644 index 00000000000..f55ec216edf --- /dev/null +++ b/data/sponsors/socraft.yml @@ -0,0 +1,2 @@ +name: "socraft" +url: "https://socraft.ch/" diff --git a/data/sponsors/sokube.yml b/data/sponsors/sokube.yml new file mode 100644 index 00000000000..c16a165eba5 --- /dev/null +++ b/data/sponsors/sokube.yml @@ -0,0 +1,2 @@ +name: "SoKube" +url: "https://www.sokube.ch/" diff --git a/data/sponsors/techfirm-before-20211001.yml b/data/sponsors/techfirm-before-20211001.yml new file mode 100644 index 00000000000..d660d8d71f9 --- /dev/null +++ b/data/sponsors/techfirm-before-20211001.yml @@ -0,0 +1,2 @@ +name: "TechFirm" +url: "https://techfirm.ch" diff --git a/data/sponsors/valueitswiss.yml b/data/sponsors/valueitswiss.yml new file mode 100644 index 00000000000..ee68bd4c281 --- /dev/null +++ b/data/sponsors/valueitswiss.yml @@ -0,0 +1,2 @@ +name: "Value IT Swiss" +url: "https://valueit.ch" diff --git a/data/sponsors/velocitytech.yml b/data/sponsors/velocitytech.yml new file mode 100644 index 00000000000..14f657d1c38 --- /dev/null +++ b/data/sponsors/velocitytech.yml @@ -0,0 +1,2 @@ +name: "velocitytech" +url: "https://velocity.tech/" diff --git a/data/sponsors/willbank.yaml b/data/sponsors/willbank.yaml new file mode 100644 index 00000000000..499a46023b7 --- /dev/null +++ b/data/sponsors/willbank.yaml @@ -0,0 +1,4 @@ +name: "willbank" +url: "https://www.willbank.com.br/" +twitter: eusouwillbank + diff --git a/hugoserver.ps1 b/hugoserver.ps1 index 9ee0c53ec2e..3d24696397b 100644 --- a/hugoserver.ps1 +++ b/hugoserver.ps1 @@ -5,4 +5,4 @@ $MyPath = $PSScriptRoot docker stop hugo-server docker rm hugo-server -docker run -tip 1313:1313 -v $(pwd):/home/circleci/project:cached -e HUGO_THEME=devopsdays-theme -e HUGO_BASEURL="http://localhost:1313" --name hugo-server --entrypoint "" cibuilds/hugo:0.81.0 hugo server --watch --bind "" +docker run -tip 1313:1313 -v $(pwd):/home/circleci/project:cached -e HUGO_THEME=devopsdays-theme -e HUGO_BASEURL="http://localhost:1313" --name hugo-server --entrypoint "" cibuilds/hugo:0.88.1 hugo server --watch --bind "" diff --git a/hugoserver.sh b/hugoserver.sh index ea5ae633296..96d31946250 100755 --- a/hugoserver.sh +++ b/hugoserver.sh @@ -16,4 +16,4 @@ fi docker stop hugo-server docker rm hugo-server -docker run -tip 1313:1313 -v $(pwd):/home/circleci/project:$MOUNT_OPTION -e HUGO_THEME=devopsdays-theme -e HUGO_BASEURL="http://localhost:1313" --name hugo-server --entrypoint "" cibuilds/hugo:0.81.0 hugo server --watch --bind "" +docker run -tip 1313:1313 -v $(pwd):/home/circleci/project:$MOUNT_OPTION -e HUGO_THEME=devopsdays-theme -e HUGO_BASEURL="http://localhost:1313" --name hugo-server --entrypoint "" cibuilds/hugo:0.88.1 hugo server --watch --bind "" diff --git a/netlify.toml b/netlify.toml index ee2d4a6b4e8..a36b8a2f986 100644 --- a/netlify.toml +++ b/netlify.toml @@ -15,10 +15,10 @@ skip_processing = true [context.production.environment] - HUGO_VERSION = "0.81.0" + HUGO_VERSION = "0.88.1" [context.deploy-preview.environment] - HUGO_VERSION = "0.81.0" + HUGO_VERSION = "0.88.1" [context.branch-deploy.environment] - HUGO_VERSION = "0.81.0" + HUGO_VERSION = "0.88.1" diff --git a/static/_redirects b/static/_redirects index 6799d390178..c1a99e7fd65 100644 --- a/static/_redirects +++ b/static/_redirects @@ -12,6 +12,7 @@ /berlin/* /events/2020-berlin/:splat 302 /birmingham-al/* /events/2022-birmingham-al/:splat 302 /birmingham/* /events/2021-birmingham/:splat 302 +/birmingham-uk/* /events/2022-birmingham-uk/:splat 302 /bogota/* /events/2021-bogota/:splat 302 /boise/* /events/2021-boise/:splat 302 /boston/* /events/2021-boston/:splat 302 @@ -74,13 +75,13 @@ /new-york-city/* /events/2021-new-york-city/:splat 302 /new-zealand/* /events/2019-auckland/:splat 302 /newcastle/* /events/2018-newcastle/:splat 302 -/oslo/* /events/2020-oslo/:splat 302 +/oslo/* /events/2021-oslo/:splat 302 /paris/* /events/2021-paris/:splat 302 /philadelphia/* /events/2020-philadelphia/:splat 302 /phoenix/* /events/2018-phoenix/:splat 302 /pittsburgh/* /events/2015-pittsburgh/:splat 302 /portland-me/* /events/2020-portland-me/:splat 302 -/portland-or/* /events/2021-portland-or/:splat 302 +/portland-or/* /events/2022-portland-or/:splat 302 /events/2021-portland/* /events/2021-portland-or/:splat 302 /porto-alegre/* /events/2021-porto-alegre/:splat 302 /portugal/* /events/2020-portugal/:splat 302 @@ -115,7 +116,7 @@ /warsaw/* /events/2019-warsaw/:splat 302 /washington-dc/* /events/2020-washington-dc/:splat 302 /zaragoza/* /events/2020-zaragoza/:splat 302 -/zurich/* /events/2020-zurich/:splat 302 +/zurich/* /events/2022-zurich/:splat 302 /events/2009-ghent/* http://legacy.devopsdays.org/events/2009-ghent/:splat 301! /events/2010* http://legacy.devopsdays.org/events/2010:splat 301! /blog/wp-content/* http://legacy.devopsdays.org/blog/wp-content/:splat 301! @@ -160,3 +161,4 @@ /lima/* /events/2020-lima/:splat 302 /rosario/* /events/2020-rosario/:splat 302 /geneva/* /events/2021-geneva/:splat 302 +/aarhus/* /events/2022-aarhus/:splat 302 diff --git a/static/events/2016-telaviv/conduct/index.html b/static/events/2016-telaviv/conduct/index.html index f701ce48de9..b3a8c2614c9 100644 --- a/static/events/2016-telaviv/conduct/index.html +++ b/static/events/2016-telaviv/conduct/index.html @@ -1,6 +1,6 @@ devopsdays Tel Aviv 2016 - code of conduct

devopsdays Tel Aviv - conduct

ANTI-HARASSMENT POLICY

DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.

Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.

Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.

If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.

Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.

We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.

CODE OF CONDUCT

I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.

II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.

III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.

IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.

V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.

VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.