diff --git a/assets/events/2026-dallas/logo.png b/assets/events/2026-dallas/logo.png new file mode 100644 index 00000000000..b897f63b1bb Binary files /dev/null and b/assets/events/2026-dallas/logo.png differ diff --git a/assets/events/2026-dallas/organizers/gokul.jpg b/assets/events/2026-dallas/organizers/gokul.jpg new file mode 100644 index 00000000000..6068c688d18 Binary files /dev/null and b/assets/events/2026-dallas/organizers/gokul.jpg differ diff --git a/assets/events/2026-dallas/organizers/herold.jpg b/assets/events/2026-dallas/organizers/herold.jpg new file mode 100644 index 00000000000..579ed2092c5 Binary files /dev/null and b/assets/events/2026-dallas/organizers/herold.jpg differ diff --git a/assets/events/2026-dallas/organizers/jack.jpg b/assets/events/2026-dallas/organizers/jack.jpg new file mode 100644 index 00000000000..b2d9a52cceb Binary files /dev/null and b/assets/events/2026-dallas/organizers/jack.jpg differ diff --git a/assets/events/2026-dallas/organizers/jessica-clark.jpg b/assets/events/2026-dallas/organizers/jessica-clark.jpg new file mode 100644 index 00000000000..91ecd4c0cff Binary files /dev/null and b/assets/events/2026-dallas/organizers/jessica-clark.jpg differ diff --git a/assets/events/2026-dallas/organizers/jessica-sabugo.jpg b/assets/events/2026-dallas/organizers/jessica-sabugo.jpg new file mode 100644 index 00000000000..d29617496a2 Binary files /dev/null and b/assets/events/2026-dallas/organizers/jessica-sabugo.jpg differ diff --git a/assets/events/2026-dallas/organizers/jim.jpg b/assets/events/2026-dallas/organizers/jim.jpg new file mode 100644 index 00000000000..2471a5b5b2c Binary files /dev/null and b/assets/events/2026-dallas/organizers/jim.jpg differ diff --git a/assets/events/2026-dallas/organizers/lee.jpg b/assets/events/2026-dallas/organizers/lee.jpg new file mode 100644 index 00000000000..0cfc1f19e17 Binary files /dev/null and b/assets/events/2026-dallas/organizers/lee.jpg differ diff --git a/assets/events/2026-dallas/organizers/mark-andersen.jpg b/assets/events/2026-dallas/organizers/mark-andersen.jpg new file mode 100644 index 00000000000..87504cd5094 Binary files /dev/null and b/assets/events/2026-dallas/organizers/mark-andersen.jpg differ diff --git a/assets/events/2026-dallas/organizers/paula.jpg b/assets/events/2026-dallas/organizers/paula.jpg new file mode 100644 index 00000000000..c4fa8665fee Binary files /dev/null and b/assets/events/2026-dallas/organizers/paula.jpg differ diff --git a/assets/events/2026-dallas/organizers/roger.jpg b/assets/events/2026-dallas/organizers/roger.jpg new file mode 100644 index 00000000000..485b7023450 Binary files /dev/null and b/assets/events/2026-dallas/organizers/roger.jpg differ diff --git a/assets/events/2026-dallas/organizers/russell.jpg b/assets/events/2026-dallas/organizers/russell.jpg new file mode 100644 index 00000000000..2fbfa7c4a28 Binary files /dev/null and b/assets/events/2026-dallas/organizers/russell.jpg differ diff --git a/assets/events/2026-dallas/organizers/scott.jpg b/assets/events/2026-dallas/organizers/scott.jpg new file mode 100644 index 00000000000..11902331c41 Binary files /dev/null and b/assets/events/2026-dallas/organizers/scott.jpg differ diff --git a/content/events/2026-dallas/conduct-fr.md b/content/events/2026-dallas/conduct-fr.md new file mode 100644 index 00000000000..41e4edf48c0 --- /dev/null +++ b/content/events/2026-dallas/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays dallas 2026" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays dallas 2026 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 dallas 2026 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2026-dallas/conduct-pt-br.md b/content/events/2026-dallas/conduct-pt-br.md new file mode 100755 index 00000000000..8848f826f95 --- /dev/null +++ b/content/events/2026-dallas/conduct-pt-br.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do devopsdays dallas 2026" ++++ + + +Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays dallas 2026 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 dallas 2026 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._ diff --git a/content/events/2026-dallas/conduct.md b/content/events/2026-dallas/conduct.md new file mode 100644 index 00000000000..c350ca292cf --- /dev/null +++ b/content/events/2026-dallas/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays dallas 2026" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays dallas 2026 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 dallas 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-dallas/contact.md b/content/events/2026-dallas/contact.md new file mode 100644 index 00000000000..1e10ec4ac89 --- /dev/null +++ b/content/events/2026-dallas/contact.md @@ -0,0 +1,16 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays dallas 2026" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + +Local Emeritus Organizers
+Ben Johnson, Annie Hedgpeth, Michael Hedgepeth, Carlos Nuñez. Mark Saum, Megan Bohl, Mike Rosado, Najwan Abdul Wahab, Travis Mims + +{{< list_core >}} diff --git a/content/events/2026-dallas/location.md b/content/events/2026-dallas/location.md new file mode 100644 index 00000000000..4f807964f8e --- /dev/null +++ b/content/events/2026-dallas/location.md @@ -0,0 +1,30 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays dallas 2026" ++++ + +Here we will provide you with information about the venue including address, map/direction, parking/transit, and any hotel details in this vicinity. +
+ DevOpsDays Dallas 2025 +


+

+ +### Conference location: +### Plano Event Center
+[2000 East Spring Creek Parkway, Plano, TX 75074](https://goo.gl/maps/Gn5gqVSKC1u) + + + + + + +
+If you are traveling to attend this event, the Plano Event Center is approximately a 45-minute drive from the DFW Airport via President George Bush Turnpike (East). Here is a list of hotels and their distance from the hotel to the vicinity of the Plano Event Center for your convenience: More information about hotels in this area, click here. +
+
+ +
+ + +{{< event_twitter >}} diff --git a/content/events/2026-dallas/propose.md b/content/events/2026-dallas/propose.md new file mode 100644 index 00000000000..8b509fe9f45 --- /dev/null +++ b/content/events/2026-dallas/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays dallas 2026" ++++ + {{< 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/2026-dallas/registration.md b/content/events/2026-dallas/registration.md new file mode 100644 index 00000000000..efdb189e6cf --- /dev/null +++ b/content/events/2026-dallas/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays dallas 2026" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2026-dallas/sponsor.md b/content/events/2026-dallas/sponsor.md new file mode 100644 index 00000000000..3af8228c2c8 --- /dev/null +++ b/content/events/2026-dallas/sponsor.md @@ -0,0 +1,26 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Interested in sponsoring DevOpsDays Dallas 2026? We greatly value sponsors for this open event." ++++ + +
+ DevOpsDays Dallas 2025 +
+
+

+ + + +DevOpsDays is a self-organizing conference for DevOps practitioners that depends on your sponsorships. We do not have a traditional trade show conference floor, 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 participate and engage with the attendees as peers. +

+Any attendee also has the opportunity to demonstrate products or projects as part of any of the Open Space sessions. Platinum sponsors will also have access to a dedicated demo room to provide hands-on demos to individuals or small groups. Be sure to send technical practitioners to interact with customers and peers at DevOpsDays on their own terms. +

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

+Please email the organizers at dallas@devopsdays.org with any questions you may have about sponsoring the event. diff --git a/content/events/2026-dallas/welcome.md b/content/events/2026-dallas/welcome.md new file mode 100644 index 00000000000..a09f6fcfa51 --- /dev/null +++ b/content/events/2026-dallas/welcome.md @@ -0,0 +1,89 @@ ++++ +Title = "devopsdays dallas 2026" +Type = "welcome" +aliases = ["/events/2026-dallas/"] +Description = "devopsdays dallas 2026" ++++ + + + + + +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ +
+
+ Location +
+
+ {{< event_location >}} +
+
+ + + + + + + + + +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ + + diff --git a/data/events/2026/dallas/main.yml b/data/events/2026/dallas/main.yml new file mode 100644 index 00000000000..758359b82ce --- /dev/null +++ b/data/events/2026/dallas/main.yml @@ -0,0 +1,206 @@ +name: "2026-dallas" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2026" # The year of the event. Make sure it is in quotes. +city: "dallas" # The displayed city name of the event. Capitalize it. +event_twitter: "devopsdaysdfw" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Devopsdays is coming to dallas!" # 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 2026-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 2026-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: 2026-09-29T00:00:00-05:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2026-09-30T00:00:00-05: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. + +masthead_background: "planoeventcenter.jpg" + +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: "" # No longer used + +location: "Plano Event Center" # Defaults to city, but you can make it the venue name. +location_address: "2000 East Spring Creek Parkway, Plano, TX 75074" #Optional - use the street address of your venue. This will show up on the welcome page if set. Also used by the event_map shortcode! + +# Optional - Social badges +# These can be used in the body of any page via matching shortcodes. See sample: https://devopsdays.org/events/2025-denver/welcome/ +event_social_linkedin: "https://linkedin.com/company/devopsdays" # Change this to the url to your Linkedin group, company, or page. +event_social_slack: "https://join.slack.com/t/devopsdays/custom_shared_invite_url" # Change this to your slack invite link. +event_social_listserv: "https://lists.devopsdays.org/subscription?custom_listserv_invite_url" # Change this to your mailing list subscription form url. +event_social_twitter: "devopsdaysdfw" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +event_social_mastodon: "https://mastodon.social/@devopsdays" # Change this to url to your mastodon page +event_social_bsky: "https://bsky.app/profile/devopsdays.bsky.social" # Change this to url to your bluesky page +event_social_youtube: "DevOpsDaysDFW" # Change this to the youtube channel handle for your event such as devopsdaysrox + + +# Social Share Buttons +# Optional: Specify which social share buttons to display on event pages. +# If not specified, defaults to all: ["email", "twitter", "facebook", "linkedin"] +# Valid values: "email", "twitter", "facebook", "linkedin" +# Example: social_shares: ["email", "linkedin"] # Only show email and LinkedIn share buttons +social_shares: # ["email", "twitter", "facebook", "linkedin"] + +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: "Gokul Sridharan" + employer: "Katalon" + bio: "Gokul Sridharan is a Master’s Degree holder in IT, an entrepreneur by nature and a successful presales management professional at CA Technologies. He has worked there for the past 3 years and successfully managing a business of $10m+ from a technical sales standpoint. Prior to joining CA and pursuing his master’s degree, Gokul started off his career at Accenture as a software developer.

During that time frame, he also started his own restaurant venture called ‘The Snack Shack’ in India. He loves DevOps concepts and likes to be a part of local meetups. He is also part of the organizing committee in DevOpsDays Dallas, and on in his spare time likes to work on new and innovative ideas." + role: "SWAG, Registration" + twitter: "ConsultGokul_CA" + linkedin: "https://www.linkedin.com/in/gokul-sridharan-98a12323/" + image: "gokul.jpg" + + - name: "Jack Teoh" + employer: "Vizient, Inc." + bio: "Jack Teoh started his DevOps journey by actively volunteering for DevOpsDays Austin since 2015 and participates in multiple user group in the DevOps space. He also started volunteering for DevOpsDays Dallas when it was just starting in 2016, then become one of the core local organizer. He enjoys helping out both at DevOpsDays Austin and DevOpsDays Dallas, because he gets to meet and interact with people who are liked minded sharing a common interest which is DevOps." + role: "Eventbrite - Ticket Sales, SWAG, Registration" + twitter: "jaxteoh" + linkedin: "https://www.linkedin.com/in/jackteoh/" + github: "https://github.com/jaxteoh" + image: "jack.jpg" + + - name: "Jessica Clark" + employer: "Capital One" + bio: "Jessica is a Technology Leader at Capital One where she is passionate about mentoring and coaching others to achieve their career goals. She currently serves at the Chief of Staff for Card Tech Foundations which drives the horizontal capabilities for the entire Card Tech organization. Prior to her current role, she led a Product Execution team focused on improving the internal developer experience through automation and standardization. She has also held roles in Cloud Governance, Tech Strategy, Process Improvement, and Software Development. Throughout her career, she has been actively been involved in various Women in Tech organizations and currently is a leader within the Allies community. Outside of work, Jessica enjoys spending time with her daughter, catching up on (bad) reality TV, or giving out high-fives on Peloton. Jessica has been a conference organizer since 2018." + role: "Call For Papers" + linkedin: "https://www.linkedin.com/in/jessica-clark-7248526/" + image: "jessica-clark.jpg" + + - name: "Jessica Sabugo" + employer: "" + bio: "Jessica is a passionate DevOps Engineer with a background in test automation and a strong commitment to the DevOps culture. Since 2019, she has been an active organizer of DevOpsDays Dallas, where she leverages her enthusiasm for community engagement and collaboration. Jessica thrives on continuous learning and enjoys exploring new technologies. She is an avid traveler and finds great joy in the DevOpsDays community, believing in the power of connection and teamwork to drive impactful change in the tech industry." + role: "Social Media, Run of Show" + twitter: "jessica_sabugo" + linkedin: "https://www.linkedin.com/in/jessica-sabugo-581ab658/" + image: "jessica-sabugo.jpg" + + - name: "Jim Baldwin" + employer: "Slalom Consulting" + bio: "Jim Baldwin has over 20 years in the IT field holding various positions from Systems Administration and Infrastructure Engineering to DevOps and Cloud Computing. After attending DevOpsDays in Austin in 2015 and becoming DevOps awakened, Jim has spent his time honing his DevOps and Agile skills.

Jim is currently a Senior Consultant at Slalom Consulting." + role: "Website, Sponsorship Outreach" + twitter: "BaldwinJim" + linkedin: "https://www.linkedin.com/in/jimbaldwin469/" + image: "jim.jpg" + + - name: "John-Paul Herold" + employer: "Southwest Airlines" + bio: 'John-Paul Herold is an Engineering Leader focused on continuous learning and building great teams that harness data to deliver high-value solutions to customers. Currently his Cloud Security org is focused on reducing risk in SWA''s AWS cloud environments, while supporting accelerated delivery, and all with a measurably excellent developer experience. John-Paul started as a Java developer, transitioned to "DevOps" Engineer when he found he could manage servers like cattle, then Cloud Engineer which brought him to Southwest Airlines where he later moved into leadership.

His path with DevOpsDays started in 2015 when he attended both Dallas and Austin, and has continued every year since. He volunteered for DevOpsDays DFW the first time in 2019, was an organizer for DevOpsDays Texas 2021, and has been an oragnizer for DevOpsDays Dallas since 2022.

John-Paul is based in Dallas and has a CSE degree from Southern Methodist University. In his off time he enjoys playing soccer, listening to music, running a homelab, reading tech books, and working on projects in his garage.' + role: "Open Spaces" + twitter: "thedailyherold" + linkedin: "https://www.linkedin.com/in/johnpaulherold/" + image: "herold.jpg" + + - name: "Lee Herrin" + employer: "Dell EMC" + bio: "Lee is an experienced technologist with a passion for solving problems. Whether technical, logistical, organizational - in every endeavor, Lee brings with him a high-level of integrity and an effective leadership style. His experience spans multiple disciplines including Employee Engagement, Distribution, IT Solutions Architecture, Virtual and Physical IT Infrastructure, and Cyber-security.

Lee is a volunteer for DevOpsDays DFW as a result of his passionate interest in DevOps (and DevSecOps) and the associated community of talented professionals.

Lee works with Ancilla LLC - As a Consultant and Project Director. Ancilla LLC provides consulting services for Cloud, CyberSecurity, Application Security and Organizational Excellence. Providing Organizations with Proven, Documented & Published Outcomes.

Lee also volunteers his time acting as Prayer Team Chair for the DFW Technology Prayer Breakfast - a local faith-based nonprofit." + role: "Social Media, Banners, Signage" + twitter: "TechnologicaLee" + linkedin: "https://www.linkedin.com/in/wtleeherrin/" + image: "lee.jpg" + + - name: "Mark Andersen" + employer: "Capital One" + bio: "Mark loves DevOps and the cloud and has spent the last 2 years with Capital One going all in on DevOps and the Cloud. Mark leads DevOps for Capital One Auto Finance and is the Cloud Lead for public cloud accounts in Plano. Previously Mark has spent 14 years at Southwest Airlines in various software development and leadership roles." + role: "Call For Papers" + twitter: "mandersen94" + linkedin: "https://www.linkedin.com/in/markandersen94/" + website: "https://www.capitalone.com/" + github: "https://github.com/mandersen94/" + image: "mark-andersen.jpg" + + - name: "Paula Lipnick" + employer: "JP Morgan Chase" + bio: "Paula has had the opportunity to be a part of innovative organizations for over 10 years, and she enjoys continuously improving processes to increase long-term business value. Currently, Paula is a Product Agility Lead at JP Morgan Chase.\n\nAlso, Paula is a huge fan of the benefits and measurable impacts that are created using DevOps, Agile, and Lean practices. She volunteered at DevOpsDays DFW in 2022, and she is overjoyed to join the Organizer Team for DevOpsDays DFW in 2023. \n\nAlso, Paula holds a Professional Scrum Master Certification, Project Management Professional Certification, MBA with a concentration in Business Intelligence and Accounting, and a Bachelor of Science in Finance. In addition, Paula loves volunteering in the community, hiking, and surfing anytime she is close to the ocean." + role: "Community Outreach, Non-Profit Outreach" + linkedin: "https://www.linkedin.com/in/paula-lipnick-mba-pmp-psm/" + image: "paula.jpg" + + - name: "Roger Servey" + employer: "Innovar Solutions" + bio: "Roger is a 20+ year International IT Leader experienced with Software delivery for systems delivering multi billion dollar impacts to their Enterprises. Roger currently leads Verizon's Engineering Practice Transformation Centers - DOJOs - Across the United States, where teams enter to learn new Agile Practices, DevOps Automantions and Cloud Technologies which speed time to value realization, drive efficiency and improve quality.

Focus Areas for Roger include: DevOps, Agile Development, Continuous Delivery, Lean Development, Software architecture and design, Pricing theory, Product Lifecycle Management, Onshore, Near Shore and Offshore project development (US, LATAM, EMEA, APAC) and Pricing Analytics.

Roger holds his Bachelors Degree from Southern Methodist University and is a continuous learner. A Practitioner of constraint management and evangelist for DevOps measurement, speaking at OS Con 2018 and GLUCON 2018 on DevOps Measurement and Enter-Sourcing with Hygieia. That which is measured, improves!. " + role: "Organizer Wrangler, Keynote Speakers" + image: "roger.jpg" + + - name: "Russell W. Black" + employer: "Elevate" + bio: "Russell currently serves as Manager of DevOps Engineering where his team encourages Dev Team autonomy for code and infrastructure pipelines. He has over 30 years of IT experience in a variety of technologies and industries. Starting as a Web Application Developer, then moving into IT Leadership Russell was introduced to DevOps in 2015 while managing platform and systems that supported the Verizon Global Website (www.verizon.com). He quickly adopted an agile / cloud-first methodology to improve feature speed and quality to the business.

Since 2008 Russell has led inclusive and empowered multi-cultural teams responsible for software development and delivery, production support, Operations, and DevOps." + role: "Volunteers" + linkedin: "https://www.linkedin.com/in/russellblack/" + image: "russell.jpg" + + - name: "Scott Purgerson" + employer: "Tech Mahindra" + bio: "Scott Purgerson, was previously a Sr. Sales Executive with Automation Anywhere located in Dallas, Texas. Although born in San Jose, CA, he takes great pride in claiming he’s a Texan, as he’s resided there 97% of his life. Scott has over 16 years of professional experience, comprised of sales and management. He’s very passionate about helping and partnering with others in their digital transformation journey. Scott joined as an organizer for Dallas DevOps Days in 2019. In his downtime, Scott enjoys spending time with his wife, Michelle, and their corgi, Winnie, as well being in the woods, hunting." + role: "Venue Logistics, Food, Entertainment" + twitter: "PurgersonScott" + linkedin: "https://www.linkedin.com/in/scott-purgerson-5858224" + image: "scott.jpg" + +organizer_email: "dallas@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 : "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: platinum + label: Platinum + max: 10 + - id: gold + label: Gold +# max: 10 + - id: silver + label: Silver + max: 10 # This is the same as omitting the max limit. + - id: happyhour + label: Happy Hour + max: 2 + - id: coffee + label: Coffee Bar + max: 1 + - id: media + label: Media + max: 5 + - id: npo + label: Non-Profit + max: 10 + - id: community + label: Community diff --git a/static/_redirects b/static/_redirects index 37854b27006..aa7183c585e 100644 --- a/static/_redirects +++ b/static/_redirects @@ -32,7 +32,7 @@ /copenhagen/* /events/2026-copenhagen/:splat 302 /denmark/* /events/2026-copenhagen/:splat 302 /cuba/* /events/2019-cuba/:splat 302 -/dallas/* /events/2025-dallas/:splat 302 +/dallas/* /events/2026-dallas/:splat 302 /denver/* /events/2025-denver/:splat 302 /des-moines/* /events/2025-des-moines/:splat 302 /detroit/* /events/2025-detroit/:splat 302 diff --git a/static/events/2026-dallas/available-now.png b/static/events/2026-dallas/available-now.png new file mode 100644 index 00000000000..81c7d6abc40 Binary files /dev/null and b/static/events/2026-dallas/available-now.png differ diff --git a/static/events/2026-dallas/boot.png b/static/events/2026-dallas/boot.png new file mode 100644 index 00000000000..63650fc89a7 Binary files /dev/null and b/static/events/2026-dallas/boot.png differ diff --git a/static/events/2026-dallas/fa-backpack.png b/static/events/2026-dallas/fa-backpack.png new file mode 100644 index 00000000000..5e2c35fa088 Binary files /dev/null and b/static/events/2026-dallas/fa-backpack.png differ diff --git a/static/events/2026-dallas/fa-landyard.png b/static/events/2026-dallas/fa-landyard.png new file mode 100644 index 00000000000..25e4b0aea6d Binary files /dev/null and b/static/events/2026-dallas/fa-landyard.png differ diff --git a/static/events/2026-dallas/half-boot.png b/static/events/2026-dallas/half-boot.png new file mode 100644 index 00000000000..6fa1f14d3bb Binary files /dev/null and b/static/events/2026-dallas/half-boot.png differ diff --git a/static/events/2026-dallas/not_available.png b/static/events/2026-dallas/not_available.png new file mode 100644 index 00000000000..6a044ddcd99 Binary files /dev/null and b/static/events/2026-dallas/not_available.png differ diff --git a/static/events/2026-dallas/planoeventcenter.jpg b/static/events/2026-dallas/planoeventcenter.jpg new file mode 100644 index 00000000000..80bb89211ad Binary files /dev/null and b/static/events/2026-dallas/planoeventcenter.jpg differ diff --git a/static/events/2026-dallas/slack.png b/static/events/2026-dallas/slack.png new file mode 100644 index 00000000000..b498e3686b3 Binary files /dev/null and b/static/events/2026-dallas/slack.png differ diff --git a/static/events/2026-dallas/sold-out.png b/static/events/2026-dallas/sold-out.png new file mode 100644 index 00000000000..27dfe5309ac Binary files /dev/null and b/static/events/2026-dallas/sold-out.png differ diff --git a/static/events/2026-dallas/sponsorship.png b/static/events/2026-dallas/sponsorship.png new file mode 100644 index 00000000000..4bf4c967322 Binary files /dev/null and b/static/events/2026-dallas/sponsorship.png differ diff --git a/static/events/2026-dallas/wip.png b/static/events/2026-dallas/wip.png new file mode 100644 index 00000000000..fe76f3e1c6f Binary files /dev/null and b/static/events/2026-dallas/wip.png differ diff --git a/static/events/2026-dallas/youtube.jpg b/static/events/2026-dallas/youtube.jpg new file mode 100644 index 00000000000..5699d91d329 Binary files /dev/null and b/static/events/2026-dallas/youtube.jpg differ