diff --git a/assets/events/2026-medellin/logo.png b/assets/events/2026-medellin/logo.png new file mode 100644 index 00000000000..310e2aae8a9 Binary files /dev/null and b/assets/events/2026-medellin/logo.png differ diff --git a/assets/events/2026-medellin/organizers/alejandra.png b/assets/events/2026-medellin/organizers/alejandra.png new file mode 100644 index 00000000000..76f97568df3 Binary files /dev/null and b/assets/events/2026-medellin/organizers/alejandra.png differ diff --git a/assets/events/2026-medellin/organizers/camila.png b/assets/events/2026-medellin/organizers/camila.png new file mode 100644 index 00000000000..bd053603104 Binary files /dev/null and b/assets/events/2026-medellin/organizers/camila.png differ diff --git a/assets/events/2026-medellin/organizers/miguelangel.png b/assets/events/2026-medellin/organizers/miguelangel.png new file mode 100644 index 00000000000..122796f4c43 Binary files /dev/null and b/assets/events/2026-medellin/organizers/miguelangel.png differ diff --git a/assets/events/2026-medellin/organizers/zapata.png b/assets/events/2026-medellin/organizers/zapata.png new file mode 100644 index 00000000000..88106a67f70 Binary files /dev/null and b/assets/events/2026-medellin/organizers/zapata.png differ diff --git a/content/events/2026-medellin/conduct.md b/content/events/2026-medellin/conduct.md new file mode 100644 index 00000000000..907d7504a6a --- /dev/null +++ b/content/events/2026-medellin/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Medellín 2025" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Medellín 2024 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 Medellín 2024 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-medellin/contact.md b/content/events/2026-medellin/contact.md new file mode 100644 index 00000000000..c0d8bb4f40f --- /dev/null +++ b/content/events/2026-medellin/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Medellín 2025." ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2026-medellin/propose.md b/content/events/2026-medellin/propose.md new file mode 100644 index 00000000000..b8d907d8719 --- /dev/null +++ b/content/events/2026-medellin/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Medellín 2024" ++++ + {{< 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-medellin/registration.md b/content/events/2026-medellin/registration.md new file mode 100644 index 00000000000..bcb782f2644 --- /dev/null +++ b/content/events/2026-medellin/registration.md @@ -0,0 +1,7 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Medellín 2025" ++++ + + diff --git a/content/events/2026-medellin/speakers.md b/content/events/2026-medellin/speakers.md new file mode 100644 index 00000000000..7b7e015ca9a --- /dev/null +++ b/content/events/2026-medellin/speakers.md @@ -0,0 +1,5 @@ ++++ +Title = "Speakers" +Type = "speakers" +Description = "Speakers for devopsdays Medellin 2025" ++++ diff --git a/content/events/2026-medellin/sponsor.md b/content/events/2026-medellin/sponsor.md new file mode 100644 index 00000000000..e10bcf810a7 --- /dev/null +++ b/content/events/2026-medellin/sponsor.md @@ -0,0 +1,183 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Medellin 2025" ++++ +
+
+
+
+
+

We greatly value sponsors for this community event! If you are interested in sponsoring, request a PDF of our prospectus for more details by dropping us an email at {{< email_organizers >}}.

+
+
+

Sponsorship Packages

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + placement + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
GOLDPLATINUMDIAMONDCOMMUNITYEVENT EXPERIENCELUNCHBREAKS
Price$3,600$6,000$10,000Partnership$1,000$2,800$1,500
Social media shout-out
Logo on DevOpsDays MDE website
Logo on marketing materials (incl. emails)
Logo on dedicated slide during breaks +
Logo on shared slides during breaks
Logo on participant badge
Dedicated table in sponsor area (w/ 2 chairs)
prominent
+
high-profile
+
Shout-out from MCs at kickoff and breaks





One, 1-minute pitch during Program
One, 3-minute pitch during Program
# Tickets included51016Contact UsContact UsContact UsContact Us
# Available864Unlimited533
Special Notes:Contact us for combo package options

* Prices in USD may vary due to exchange rate

+

* If the conference is cancelled due to events beyond our control (e.g. venue closure or government edict) we will do our best to reimburse everyone we can; this is dependent on obtaining a refund from our venue based on force majeure and we cannot absolutely guarantee this will happen. Please let us know if your sponsorship is dependent on the hybrid event taking place before you make your sponsorship payment.

+ +
+
+
+
+
+
+

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/2026-medellin/welcome.md b/content/events/2026-medellin/welcome.md new file mode 100644 index 00000000000..340f28d32b5 --- /dev/null +++ b/content/events/2026-medellin/welcome.md @@ -0,0 +1,128 @@ ++++ +Title = "DevOpsDays Medellín 2025" +Type = "welcome" +aliases = ["/events/2025-medellin/"] +Description = "Welcome to DevOpsDays Medellín 2025" ++++ +
+
+ DevOpsDays Medellin 2025 +
+
+

Nuestra conferencia DevOpsDays Medellín 2025 vuelve el 22 y 23 de mayo de manera presencial desde la Universidad Luis Amigó

+

+ The DevOpsDays conference arrives to Medellín once again, Be part on May 2025! +

+

Event Information

+

+

    +
  • +

    Dates

    +
    • +
  • +
    {{< event_start >}} - {{< event_end >}}
    +
    • +
+

+

Conference format

+

+

    +
  • + Two days of conferences and activities. +
    • +
  • + Starting Welcome from the organizers and day overview. +
    • +
  • + Talks that follows the traditional format of a speaker or panel. +
    • +
  • + 30 minutes. +
    • +
  • + Set of several ignite talks. +
    • +
  • + Openspaces in the afternoon. +
    • +
+

+
+
+
+
+ +    Buy your Tickets Now! - ¡Compra tu entrada ahora! + + + + +
+ +    Contact the Organizers + +
+
+
+
+
+
+ + +
+
+
+
+ +    Follow @DevOpsDaysMed +
+ +
+
+
diff --git a/data/events/2026/medellin/main.yml b/data/events/2026/medellin/main.yml new file mode 100644 index 00000000000..6d6effc62cb --- /dev/null +++ b/data/events/2026/medellin/main.yml @@ -0,0 +1,86 @@ +name: "2026-medellin" # 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: "Medellín" # The displayed city name of the event. Capitalize it. +event_twitter: "DevopsdaysMed" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "DevOpsDays is returning to Medellín. More updates will be available soon." # 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: 2026-05-27T08:00:00-06:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2026-05-28T08: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: 2026-01-24T08:00:00-06:00 # start accepting talk proposals. +cfp_date_end: 2026-04-18T08:00:00-06:00 # close your call for proposals. +cfp_date_announce: 2026-04-18T08:00:00-06:00 # inform proposers of status + +cfp_link: "" + +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: # "https://www.ticketopolis.com/medellindevopsdays2020/tickets.aspx" # 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: "6.2339363,-75.5887074" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html +location: "¡Conferencia Virtual!" # Defaults to city, but you can make it the venue name. +# +# location_address: "Carrera 43A (Av. El Poblado) con Calle 30, Medellín, Antioquia, Colombia" #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: Spanish + url: "https://devopsdays.io/" + - name: contact + - name: conduct + +# 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: "Carlos Zapata" + employer: "Rockwell Automation" + linkedin: "https://www.linkedin.com/in/carlos-zapata-96479275/" + image: "zapata.png" + + - name: "Miguelangel Pineda" + employer: "Banco BICE Chile" + image: "miguelangel.png" + linkedin: "https://www.linkedin.com/in/miguelangel-pineda-garcia/" + + - name: "Camila Gallego" + employer: "Agile & Consulting Group Co" + image: "camila.png" + + - name: "Alejandra Pérez" + employer: "Devops Colombia" + image: "alejandra.png" + + + +organizer_email: "medellin@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 + +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: diamond + label: Diamond + - id: platinum + label: Platinum + - id: gold + label: Gold + - id: socialmedia + label: Social Media